Skip to content

v0.25.0

Branch names for a session started from a work item now follow the repository’s own rules — its git-flow settings, a .agent-fleet/branches file or Bitbucket’s branching model. Open pull requests in Work items show their CI status and conflicts. af-aws-exec runs your assume-role and credential_process profiles, and Settings › AWS profiles/SSM logs in from the profile’s row. A Managed session that fails to start now shows what its CLI printed.

  • Branch names follow the repository’s rules. Starting a session from a work item fills in the branch name and its base from the repository’s .agent-fleet/branches, its git-flow settings (.gitflow or the clone’s gitflow.*) or Bitbucket’s branching model, says which rule chose the base, and notes a name that does not match. It never refuses a name. The rename dialog offers the repository’s branch kinds, and the branch template gains {ref}, {num}, {project}, {type} and {prefix}. Initializing git-flow from the Console is still to come (#1126). (#1120, #1124, #1125)
  • Open pull requests in Work items show their CI status and merge conflicts — failing, running or passing, and a mark when the PR conflicts with its base. Nothing is drawn when GitHub has no answer yet. (#1113)
  • The work item’s “already started” list shows session names, and a session that has since been archived can be restored from there. (#1108)
  • af-aws-exec runs your own assume-role (role_arn + source_profile) and credential_process profiles when you name the account with --account. It checks the whole chain first and passes only short-lived credentials. Assuming a role from a Settings SSO profile is still to come (#1109). (#1107)
  • Settings › AWS profiles/SSM (was “AWS SSM”) has Log in and a login-state badge on each profile row, so you can sign in before a command asks.
  • A Managed session that fails to start shows the last lines its CLI printed, with secrets removed, instead of only “did not start in time”. (#1076)
  • create_session can set the child’s reasoning effort (it needs model too). (#1068)
  • The image studio on a phone: the draft bar stays in view while you type, the composer sits on the pane’s bottom edge, toasts no longer cover the composer, and a tap outside dismisses them. “N pictures are ready” stays until you look, and a studio started in a new worktree takes that worktree’s name. (#1089, #1090)
  • AI-suggested titles for a session started from a work item keep the item’s key (#1146, PROJ-123).
  • The Work items filter has the same box and × as the other filters, and Escape clears it.
  • A translated question card asks again for the fields the first translation dropped. (#1114)
  • The engine catalogue sizes the memory of gemma-4, LFM2.5 and GPT-OSS models correctly, so they can be enabled without declaring their memory by hand. (#975)
  • llama.cpp sessions with long conversations read faster in the mirror.
  • codex sessions on Terminal (CLI) ran in the home directory instead of their working copy, could not be resumed, and Agent Fleet’s own tools could not tell which session called them. Switching a Managed codex session to Terminal no longer stops at “This conversation is open in another app”. (#1131)
  • On AWS deployments, an AI suggestion (title, branch name, reply) could fail when the model took close to a minute to answer.

Nothing to do. The default branch name for a work item changes from feature/issue-1113 to feature/1113-<title words>, with fix/ for a bug; a branch template you set yourself is kept. On ECS, update.sh now also moves the image engine’s ComfyUI tag when it is still on an earlier release’s default (copying the image into ECR first); a tag you chose yourself is left alone. (#965)

Agent CLI pins: Claude Code 2.1.284, Codex 0.158.0, OpenCode 1.18.33, Copilot 1.0.89, Antigravity 1.2.12, Cursor 2026.09.28-64d2043 and Muse Code 1.4.0-R4302.1. Kiro is unchanged from 0.24.0.