Skip to content
Agent Fleet

v0.23.2

Each terminal session gets its own scratch folder, removed along with the session, and Settings › Machine can empty the caches go, npm, uv and pip leave in your home. Around them, a child you asked not to be notified about no longer leaves a red dot behind, the working-copy delete shows which sessions run in each copy, and the Files pane no longer shows Agent Fleet’s own data folder.

New

Section titled “New”
  • Each Terminal (CLI) session has its own scratch folder, $AF_WORK_DIR. It is ~/.af-work/<session>/, created when the session starts and deleted with the session, so an agent’s probes, review checkouts and screenshots no longer pile up loose in your home. Managed sessions do not get it yet.
  • Settings › Machine › Tool caches lists the caches go, npm, uv and pip keep in your home. They grow without limit and nothing empties them. Measure counts them only when you press it; Empty deletes one after a confirmation. A cache that a running build or install is using shows In use and cannot be emptied until it finishes.

Improved

Section titled “Improved”
  • The working-copy delete shows the sessions in each copy — kind icon and display name, with a state chip on running ones — so a random folder name no longer hides what the copy was for.
  • The user guide’s top page puts the release history in its own paragraph right after the reference.

Fixed

Section titled “Fixed”
  • With “Notify when a child session is waiting for input” off, the child’s row, its pane tab and the notification center still showed it as unread. It is now marked read as it arrives. Questions and approvals from a child, and other sessions waiting for input, stay unread as before.
  • The Files pane could open ~/.local/share/agent-fleet, which holds terminal scrollback, the cleanup archive of deleted sessions’ transcripts and the usage ledger. It is now blocked like the other Agent Fleet folders.
  • ecs-ec2: pause.sh left engine GPU instances running, billed until someone terminated them, because it stopped the CP — the only thing that terminates them — without looking at them. It now waits for engines to go idle (or terminates them with --fast), sweeps any left after the CP stops, and also stops the database (--keep-db keeps it). --up starts the database before the CP, and --status warns about GPU instances with no CP and a database running under a paused CP.

Upgrade notes

Section titled “Upgrade notes”

Nothing to do. On ecs-ec2, pause.sh now stops the RDS database too; pass --keep-db to keep it running.

Agent CLI pins: Claude Code 2.1.282, Antigravity 1.2.10 and Kiro 2.24.0. Codex, Copilot, OpenCode, Cursor and Muse Code are unchanged from 0.23.1.