Skip to content
Agent Fleet

v0.27.0

Members can run Google Cloud commands as themselves with af-gcloud-exec, from profiles in Settings with a Console login, as they already could for AWS. The WS bar shows which AWS and Google Cloud profiles are signed in, and a single AWS profile can be logged out. Peer, operator and scheduled messages queued for a Managed session now survive a stop or an Agent restart. On ECS, Recreate, Clean home and Destroy reach the EFS home, and ecs-ec2 slots can be reserved for replacement at their next start. The CP task role on ECS is narrowed further; operators of a custom AMI or a restricted deployer have something to check.

New

Section titled “New”
  • Google Cloud profiles. Settings › Google Cloud holds a member’s profiles (project, quota project, account, service account to impersonate, region and zone from a list), and af-gcloud-exec --profile <name> --project <id> -- <command> runs gcloud, kubectl against GKE or Terraform with a short-lived token of that profile. The login is finished in the Console, no Google credential is stored in Agent Fleet, and the first run installs the Google Cloud SDK into the home. A badge in the WS bar shows which profiles are logged in. (#1495, #1496, #1497, #1498, #1511, #1517)
  • AWS profiles in the WS bar. A chip, tinted by state, shows how many Settings AWS profiles are signed in; its popover lists them with Log in. Log out (there and in Settings) signs out one profile only, the Console warns before a login that cannot renew runs out, and region fields are picked from a list. (#1477, #1502, #1483, #1029, #1506)
  • Session rows show the branch’s pull request and listening ports. The PR’s state and, while open, its checks; each port opens the browser pane on it. (#1062)
  • Schedules choose where their result goes: the assistant, the notification center, Discord or Slack. Stay silent when there is nothing to report delivers nothing when the run answers [SILENT]; failures are always notified. (#1560)
  • The launch modal’s first prompt has searchable templates (your own, the repository’s .agent-fleet/launch-prompts.md, and recent prompts), the skill picker, and attachments of any file type. A provisional branch name is asked for again for up to 45 seconds. (#1469, #1448, #1447, #1440)
  • Session menus reach further: a session whose worktree folder is gone offers Recreate working copy (worktree)…, the menu opens the session’s repository menu in the left rail, and a session link in the mirror or the assistant chat opens the session menu on right-click or long press. (#1445, #1557, #1553)
  • A session can read a peer’s recent output with the new peek_session_output af MCP tool, under the same switch and kinds as peer messages. (#1061)
  • A peer message to a session waiting on its user (a question, plan approval or permission prompt) is queued and delivered after the answer instead of being refused. (#1031)
  • ecs-ec2: reserve slots for replacement. Settings › Admin › Slots (super admin) shows each slot’s launch template version; a reserved slot’s workspace moves to a new slot at its next start, and the home is kept. This is now the way to move slots onto a new launch template. (#1473)
  • Tenant admins can rotate one member’s internal git token from the member’s details. (#1199)

Improved

Section titled “Improved”
  • ECS: Recreate, Clean home and Destroy now reach the EFS home, and a home operation interrupted by a Control Plane restart is finished afterwards. On ecs-ec2, Destroy also removes the member’s EFS directories. (#1260, #1536, #1537, #1544)
  • Removing a member stops their workspace and pauses their schedules; inviting them back resumes the schedules. (#1087)
  • Changed files tells session scratch ($AF_WORK_DIR) and other working copies apart from the session’s own changes, and its source-control button opens the session’s own copy. (#1607)
  • New users and devices start in the Tabbed grid layout. A device that already chose a layout keeps it. (#1481)
  • Phone swipes move through sessions in left-rail order and skip shell and SSM sessions. (#1595)
  • Settings and the tenant/admin dialogs have consistent headings, sections and spacing. (#1480, #1491)

Fixed

Section titled “Fixed”
  • Queued messages to a Managed session were lost on a stop, an execution-method switch or an Agent restart. Peer messages, operator instructions and scheduled prompts now stay queued; one dropped before it ran is reported as not run. A queued peer message could also be typed into the turn the user’s answer had just resumed. (#1255, #1257, #1550)
  • The SSM session’s Force re-login signed the member out of every AWS profile. It now discards only that profile’s login. (#1484)
  • ecs-ec2: a slot could be quarantined after a release and a start raced on the same home mount. (#1592)
  • A codex Managed session never saw the image studio’s trial tool when the switch was turned on after it started; the switch now applies from the next trial for every kind. (#1132)
  • codex: a slow scan of loaded threads never finished, which could hold a Managed → Terminal switch. (#1147)
  • Mirror: a question you cancelled said the agent had declined it; the tap that closed a suggestion chip’s menu reopened it; Translate could stay disabled after a pane remount. (#1604, #1556, #1589)
  • Console: Escape did not close an overview card’s menu or its dialogs; a pinned worktree header slid under a wrapped repository header on touch; the ahead/behind chip was unevenly spaced. (#1449, #1584, #1509)
  • Admin: a member key or tenant slug could name a directory outside the member’s own, or one already used by the Control Plane. Both are now refused. (#1455, #1214)

Upgrade notes

Section titled “Upgrade notes”
  • ECS: the CP task role is narrowed. Its EC2 writes are limited to this deployment’s own slots and engine instances, and it launches them only from Amazon-owned or public images. A slot or engine launch template pointing at an AMI of your own now fails with UnauthorizedOperation. (#1423, #1522)
  • ECS: update.sh now deploys stacks with CAPABILITY_NAMED_IAM and creates managed policies named af-<stack>-cp-…-<region>. A restricted deploying role also needs the IAM policy actions listed in deploy/aws/ecs/cfn/PARAMETERS.md. On ecs-ec2, the slot-pool stack is deployed before 20-platform. (#1576)
  • ecs-ec2: to move slots launched before 0.26.0 onto the new user data, reserve them in Settings › Admin › Slots and have users stop and start, rather than setting Ec2SlotTerminateAfterSec. If you set it only for that move, set it back to 0. (#1473)
  • Upgrading from 0.25.0 or earlier: the operator steps in 0.26.0’s Security section still apply.

Agent CLI pins: Claude Code 2.1.288, Codex 0.160.0, Copilot 1.0.91, Antigravity 1.2.16, Cursor 2026.10.01-e373342, Kiro 2.27.1 and Muse Code 1.4.2-R4684.1. OpenCode is unchanged from 0.26.0. (#1427, #1532)