Skip to content
Agent Fleet

v0.13.0

Issues, pull requests and tickets from GitHub, Jira and Bitbucket appear in the left rail, and a session starts from the one you picked. On ecs-ec2, a workspace now has a memory limit of its own, so a heavy one can no longer take its machine down with it.

New

Section titled “New”
  • Work items — GitHub issues and pull requests, Jira tickets, Bitbucket pull requests — are listed in the left rail, and you start work from one. Opening a row shows the item, and starting from there picks the repository and whether to use a new or existing worktree, then fills in the prompt, session name and branch. The list is there while the workspace is stopped too, which is where it matters most: starting a stopped workspace from a ticket is the point.
  • Connections are per tenant: GitHub, Jira and Bitbucket. Jira connects with an API token or with OAuth, and issue tracking has its own tab in settings. What you see is whatever your saved queries return — there is one query to edit, not a filter UI.
  • A report can be written back to the ticket. Agent Fleet drafts the facts — the branch and the files that changed — and you write the words and press post. Nothing is posted automatically, agents cannot reach this path, and no summary is generated for you.
  • A workspace on ecs-ec2 has its own memory limit, so one workspace using everything can no longer starve the machine’s own services — which took a slot down for hours. The size shown is the memory you can actually use, with the machine’s size in brackets. An optional alarm mails you when the pool’s disks are saturated.

Fixed

Section titled “Fixed”
  • A workspace could become impossible to start, answering 504 every time, while the machine looked healthy from outside: the machine was up but its operating system was gone. Such a machine is now dropped rather than waited for, and the workspace is placed on another one.
  • A running turn was reported as waiting for input on a narrow screen — a phone, in practice.
  • A message from another session looked like something you had written: it arrived without the badge that says where it came from.
  • A session that failed to start on a retired model buried the reason under a list of every available model. It now names the closest matches and says the model was retired.
  • Setting CI in the workspace environment left Cursor sessions with a dead screen — a banner and nothing else, ignoring every keystroke. Cursor drops its interactive UI when it sees that variable, so it is no longer passed on.

Upgrade notes

Section titled “Upgrade notes”

On ecs-ec2, workspaces now run with a memory limit: the machine keeps a reserve for its own services (a fifth of the nominal size, between 1 and 2 GiB), and the rest is yours. Ec2HostReserveMb (AF_ECS_EC2_HOST_RESERVE_MB) changes or switches that off, and PoolAlarmEmail turns on the disk-saturation alarm, which is off by default. Because the number you can use is no longer the machine’s size, both are shown.

Agent CLI pins: Claude Code 2.1.247, Codex 0.150.1, Copilot 1.0.81, Antigravity 1.1.22, Cursor 2026.08.25, Kiro 2.20.1. The others are unchanged from 0.12.4.