v1.0.0

The first tagged release. The list below is everything Aixle Flow does as of
1.0.0, by product area; later releases list only what changed.

Added

• Companies & projects: companies as separate workspaces; one person can
  belong to several and switch between them from the sidebar.
• Companies & projects: projects page with search, per-person favorites,
  project creation and transfer of project ownership.
• Companies & projects: light and dark theme.
• Sign-in & onboarding: sign-in with password, Google, Microsoft (Entra
  ID), single-use email links or passkeys; the email domain finds the
  workspace.
• Sign-in & onboarding: authenticator-app codes, and step-up confirmation
  when a session enters a workspace whose sign-in rules it does not yet meet.
• Sign-in & onboarding: email invitations that can be accepted, declined
  or used to create an account, with reminders.
• Sign-in & onboarding: two-step onboarding — role and agent output
  language, then connecting an agent runtime; viewers get a short tour.
• Sign-in & onboarding: hosted only — self-service workspace signup
  confirmed by email, and a How it works page with pricing and an ROI
  calculator.
• Sign-in & onboarding: public landing page, privacy policy and terms of
  service.
• Profile: agent runtimes Claude Code, Cursor CLI, Codex, Gemini CLI,
  Antigravity CLI, Grok and Kiro CLI, each connected per company through its
  own login in an in-page terminal.
• Profile: Claude Code on your own Amazon Bedrock account, connected
  through AWS IAM Identity Center, with a health check.
• Profile: agent logins stored encrypted, refreshed by the server and
  saved back when a CLI rotates them; a failed refresh sends an email.
• Profile: default agent and model; sharing your sessions with project
  members; signing out every other browser.
• Profile: companies you belong to, pending invitations, and leaving a
  company with a handover of the projects you own.
• Profile: Usage tab — your sessions, tokens and spend, and each vendor's
  quota windows with the time until they reset.
• Profile: Security tab — link or remove Google and Microsoft sign-in,
  manage passkeys and authenticator codes, end signed-in devices.
• Profile: MCP tab — a personal token that makes Flow an MCP server for
  your own agents (Claude Code, Codex, Cursor), acting with your permissions.
• Profile: the personal MCP server's tools cover projects, boards,
  workflows, runs, resources and catalogs, with guide prompts; you choose
  which tools it serves.
• Overview: project home with KPI cards and period deltas (tasks,
  sessions, runs, spend, cost per session), run outcomes, tasks per column and
  recent activity.
• Tasks: one Kanban board per project; each column has a purpose the agent
  receives; columns can be added, renamed, reordered, removed and collapsed.
• Tasks: board templates on an empty board: Simple Kanban, Dev Team and
  Full SDLC.
• Tasks: cards with a Markdown description, type, priority, assignee,
  tags, parent epic, subtasks, comments, attachments and a stable #id.
• Tasks: card drawer with details, latest run, run history, comments
  filterable by people or agents, and the card's time, tokens and spend.
• Tasks: search by title or #id (/), filters by type, assignee and
  tag, archived cards, and saved view presets, personal or shared.
• Tasks: n creates a card; multi-select moves, archives, deletes or sets
  priority, assignee or tags on many cards at once.
• Tasks: board activity feed, per-card movement history, and live updates
  for everyone on the board.
• Tasks: a column bound to a workflow starts a run when a card enters it,
  or offers Run workflow on the card; cooldown and Retry run.
• Workflows: workflows as graphs of sessions (steps); sessions that do not
  depend on each other run in parallel, each in its own container.
• Workflows: per session — instructions, persona, required runtime,
  preferred model, resources, inputs, outputs, dependencies and an optional
  BMAD Method install.
• Workflows: on failure fail, retry (with a limit) or skip; skip never, if
  outputs exist, or manually; human approval; sub-steps the agent checks off.
• Workflows: workflow-wide tools, skills, connectors, assets and
  repositories, optionally inheriting every project resource.
• Workflows: declared input and output files (globs allowed); a session
  receives the outputs of every session it runs after.
• Workflows: @ references in instructions to assets, outputs, sessions,
  connectors, tools, skills and config items, checked as you type; a run
  certain to fail does not start.
• Workflows: edits kept until Save; each Save is a numbered version with
  history, diff and revert; a Save over a newer version is refused.
• Workflows: archive and restore, duplicate, publish to the Workflow
  Catalog, and run by hand with chosen input files.
• Triggers & gates: Triggers page with every trigger in the project,
  filterable by source and workflow; add, edit, switch off, delete.
• Triggers & gates: triggers on a task entering a column, a schedule (cron
  with time zone), a Slack or Teams message, an incoming webhook, or a task
  tracker event.
• Triggers & gates: off-board triggers choose whether a run gets a card
  (none, existing, create, find or create) and run as the trigger's creator.
• Triggers & gates: event filters, a cooldown, and de-duplication so a
  re-delivered event never starts a second run.
• Triggers & gates: per-project incoming webhooks verified by HMAC
  SHA-256, a shared token, a Slack signature, or nothing.
• Triggers & gates: CI gates hold a card on GitHub checks or Actions,
  GitLab pipelines, or Azure DevOps builds and PR policies; a step can also
  wait for a person.
• Triggers & gates: gates re-check the provider when a webhook is missed
  and go stale after a time limit.
• Triggers & gates: runs report back to their source — a status card in
  the chat thread, or a comment on the tracker issue when a run fails.
• Sessions & Runs: one list of workflow runs and standalone sessions, with
  filters and search.
• Sessions & Runs: standalone sessions with a runtime, model, persona,
  prompt, resources and interactive or automatic mode; restart from a
  finished session.
• Sessions & Runs: live terminal in the browser, an embedded VS Code
  editor for the session's owner, and log replay of finished sessions.
• Sessions & Runs: run page with steps in order, parallel steps side by
  side, approve and continue, retry, skip with a reason, and cancel.
• Sessions & Runs: per-session tokens and cost, secrets redacted from
  logs, failed repository clones named, and the workflow version each session
  used.
• Sessions & Runs: session queues — sessions wait in order for a free
  worker and say whether they wait for a slot, for capacity, or are starting.
• Sessions & Runs: run outputs can be downloaded, promoted to project
  assets, or reviewed in bulk to keep or dismiss.
• Assets: project files in nested folders — upload, rename, move,
  drag-and-drop, delete, search, and a flat All files view.
• Assets: multi-select move and delete, version history per file, and
  files from Slack and Teams messages saved into folders.
• Assets: public share links that open a file in a sandboxed viewer and
  can be revoked; agents can create them too.
• Agents: personas (title, persona, communication style, principles) that
  run on any runtime; version history, diff, revert and archive.
• Wrappers: custom tools run in a container image you choose, with files
  edited in the app; attached to workflows or sessions; versioned and
  archivable.
• Skills: catalog mirrored from skills.sh with install counts and security
  audit ratings; a high or critical rating asks for confirmation.
• Skills: hand-written skills from a SKILL.md form; installs keep a copy of
  the files; version history, diff, revert and archive.
• Connectors: MCP servers over HTTP, SSE or stdio, from a catalog mirrored
  from the official MCP registry or added by hand.
• Connectors: header and env values can reference secrets; values are never
  shown, and are cleared when the server's address changes.
• Connectors: OAuth 2.1 servers with discovery, automatic or manual client
  registration, shared or per-user credentials, and an email when refresh
  fails.
• Connectors: a changed tool list must be accepted before use; catalog
  connectors update in place; packages are pinned to exact versions.
• Connectors: version history, diff and revert that never store secrets;
  archive and restore.
• Connectors: a built-in aixle-tools server in every session — board,
  gates, sub-steps, assets, secrets, other sessions' status, finish or fail.
• Repositories: GitHub, GitLab and Azure DevOps repositories with a source
  branch, and public GitHub and GitLab repositories with no integration.
• Repositories: clones carry every branch and full history; git and gh
  get a short-lived token for one repository on each call.
• Trackers: GitHub Projects, Azure Boards, Jira, Linear and YouTrack as the
  project's trackers — primary or read-only, detach, and a board column per
  tracker state.
• Trackers: agent tools to search, read, create, update, move, assign and
  comment on issues, and link them to board tasks.
• Integrations: GitHub through the GitHub App or a personal access token,
  with CI gate webhooks and Test connection.
• Integrations: GitLab, self-managed included, through a personal access
  token, with pipeline hooks for CI gates.
• Integrations: Azure DevOps through Sign in with Microsoft or an admin
  token — repositories, pull request and build tools, Azure Boards, Service
  Hooks set up automatically.
• Integrations: Jira Cloud (Atlassian app or service account), Linear
  (Linear app or API key) and YouTrack Cloud or self-hosted (the Aixle Flow
  YouTrack app).
• Integrations: Slack — one or more workspaces, @mention triggers, the Run
  workflow message action, /aixle run and /aixle status, account linking,
  incoming files.
• Integrations: Microsoft Teams — approval link for a Microsoft 365 admin,
  channel and chat triggers, /run and /status, files both ways.
• Integrations: chat tools to post (Markdown, Slack blocks, files), read
  threads, and edit or delete messages in Slack and Teams.
• Integrations: Coder — agents take remote workspaces from a pool, clone a
  repository onto one, run commands over SSH and release it.
• Secrets & Variables: project secrets and variables, encrypted at rest and
  attached to sessions by name; values stay masked and each delivery is
  logged.
• Members: project members picked from the company, with an owner badge
  and removal after confirmation.
• Analytics: project analytics by period, scope and person — cost and
  tokens, per-runtime activity, per-workflow cost, sources, durations and an
  activity heatmap.
• Settings: project name, description, artifacts language (11 languages),
  reserved workers, archive and delete.
• Aixle Builder: describe a process in plain language; an agent acting as
  you creates workflows, steps, triggers, board columns, agents, skills and
  connectors.
• Aixle Builder: live terminal and activity feed, workflow checks and test
  runs, Workflows and Board tabs, and past sessions that can be resumed.
• Templates: public template catalog (projects, workflows, boards, agents,
  skills, connectors) from maintainer-approved publishers.
• Templates: install shows what is created, reused or in conflict, asks
  for settings, and ends on a setup checklist; triggers start switched off.
• Templates: publishing as a pull request to AixleHQ/flow-templates through
  the personal MCP server's publish_template prompt.
• Workflow Catalog: company catalog of published workflows with their
  publisher, search, and Copy & Configure into a project.
• Company analytics: admin view across projects — summary, cost and
  tokens, per-runtime activity, per-project breakdown and session sources.
• Company sessions: admin list of every session and run in the company,
  with artifact review.
• Company assets: company files and folders for admins, shown read-only
  inside each project's Assets.
• Company members: member list with search, invitations with a role
  (Admin, Employee, Viewer), resend, role changes and removal, with emails for
  each.
• Company members: member profile with a colleague's usage and the
  sessions they share.
• Company settings: name, branding (logo and colors) and the number of
  workers (concurrent sessions).
• Company settings: Access — the sign-in methods the workspace accepts,
  refusing changes that would lock a member out; per-company OpenID Connect
  connections (Okta, Entra, Ping and others), enabled after a test sign-in.
• Company settings: domain verification by DNS TXT record, so people from
  the domain can join automatically; SCIM 2.0 directory sync.
• Company settings: hosted billing through Stripe — free worker-hours, a
  balance banner, card checkout, cancel and resume, paying a failed invoice.
• Docs: documentation portal at /docs with search, user guide,
  integration setup and operator reference.
• Deployment modes: self-hosted (nothing metered), hosted (Stripe billing) and
  AWS Marketplace (hourly worker metering, split per company).
• Docker Compose stack (web, worker, PostgreSQL, Redis, Temporal, Traefik,
  OTLP ingest); make setup and make up start it.
• Agent sessions as Docker containers or Kubernetes pods in per-project
  namespaces; terminals and editors proxied through Traefik.
• Durable runs on Temporal that survive restarts; board-triggered runs are
  delivered at least once and never start twice.
• Company session capacity, project reservations and a queue health page in
  the admin panel.
• Platform admin panel: impersonation, restore, sign out everywhere and
  permanent delete of users; company capacity; a record browser; catalog
  syncs.
• OpenAPI explorer at /api-docs behind HTTP Basic auth.
• Sentry for web, frontend and worker; agent token and cost telemetry through
  OTLP ingest; S3-compatible storage; SMTP mail.
• Versioned releases: a vX.Y.Z tag publishes every image to
  ghcr.io/aixlehq as X.Y.Z (and X.Y, X, latest for a stable
  release), and web X.Y.Z launches agent images X.Y.Z.
• Agent runtimes and their CLI pins declared once, in
  config/agent_runtimes.json, with a weekly canary that reports pins behind
  the vendors' newest releases.
• Apache License 2.0, NOTICE attribution file, trademark policy
  (TRADEMARK.md) and third-party license inventory
  (THIRD-PARTY-LICENSES.md, NOTICES.md).
• Contributor model: individual and corporate Contributor License Agreements
  (CLA.md, CLA-CORPORATE.md) and Developer Certificate of Origin (DCO)
  sign-off, documented in CONTRIBUTING.md.
• Open-source documentation: README, ROADMAP, quickstart, user guide and
  reference.
• Community health files: Code of Conduct, Security Policy, Governance, issue
  and pull-request templates, CODEOWNERS, and this changelog.

Changed

For deployments that ran a build from before this release:

• A release's web image launches the agent images of its own version
  (AGENT_IMAGE_TAG defaults to it) instead of latest; setting
  AGENT_IMAGE_TAG still overrides it. Images are no longer published from
  the main-images branch.
• Agent runtime images are derived from AGENT_IMAGE_PREFIX +
  AGENT_IMAGE_TAG; the per-runtime AGENT_IMAGE_* variables remain as
  overrides.
• Agent Dockerfiles take their CLI pin as a required CLI_VERSION build arg;
  make build-agents passes it from config/agent_runtimes.json.
• Every deployment input is declared in config/settings.yml and documented
  in docs/reference/configuration.md.
• The Active Record pool follows Puma's RAILS_MAX_THREADS default (10)
  instead of 8 connections.

Removed

For deployments that ran a build from before this release:

• Configuration nothing read: AUTHOR_NAME, AUTHOR_EMAIL, RAILS_PORT,
  TEMPORAL_UI_URL, REDIS_UI_URL, TRAEFIK_DASHBOARD_URL,
  TRAEFIK_CORS_ORIGINS, OTEL_EXPORTER_OTLP_METRICS_ENDPOINT,
  OTEL_EXPORTER_OTLP_LOGS_ENDPOINT, CODER_DEFAULT_TEMPLATE,
  CODER_MACHINE_PREFIX, MAX_FILE_SIZE, ENVIRONMENT. Setting them now has
  no effect; they can be dropped from ConfigMaps, compose files and CI build
  args.

Images

Published as ghcr.io/aixlehq/flow-<name>:1.0.0: flow-web, flow-otlp-ingest, flow-agent-base-core, flow-claude-code, flow-cursor-cli, flow-codex, flow-gemini-cli, flow-antigravity-cli, flow-grok, flow-kiro-cli. Web 1.0.0 launches the agent images of the same version.