v0.32.0

A session can move to another agent, carrying its conversation and working state, and offers the move when it hits a usage limit. Apps that sign in with Google can sign in on a preview host through a development sign-in, the workspace bundles a Jira CLI, and opencode is now opencode 2. Agent memory gets an experimental review that suggests memories from finished sessions, and can be used from agents outside Agent Fleet.

New

• Move a session to another agent. Move to another agent… in the session menu starts a new session of another kind in the same working copy, with a handover file describing the conversation, uncommitted changes and pending work. When a session hits its usage limit, a band in the conversation offers the move, listing the agents with quota left first. (#2182, #2254)
• Export a conversation as Markdown from the session menu: conversation only, with tool names, or with tool output. Secrets are masked. (#2183, #2202)
• Development sign-in for apps on a preview host. An app that signs in with Google can sign in with your Agent Fleet account by changing only its issuer, client id and secret, which every workspace receives as AF_DEV_IDP_*. Settings › Preview subdomains shows the issuer and client id (the secret stays in AF_DEV_IDP_CLIENT_SECRET inside the workspace) with copy-ready configuration for Spring Boot, Auth.js, Go and Better Auth, and lets you define test personas to sign in as. It needs preview subdomains; see the upgrade notes. (#2218, #2222, #2223, #2228, #2304)
• The Jira CLI jira is in the workspace image and signs in through your Jira connection, API token or OAuth, for every agent. (#2178)
• Memory suggestions from finished sessions (experimental). With Have finished sessions suggest memories on (Settings › Agent memory › Settings, off by default), a session that has paused for a while is read by a helper agent with no tools, which proposes memories worth keeping (Suggest memories now in the session menu runs it on demand). Nothing is saved until you approve it under Agent memory › Changes › Proposed; the excerpt goes to the provider chosen in AI assistance and spends tokens. This is an early version, and what it proposes may change. (#1559, #2320, #2321)
• Use Agent Fleet memory from outside Agent Fleet. Your own Claude Code or Claude Desktop can read, and if you allow it write, your workspace’s Agent Fleet memory through the /mcp endpoint with a personal access token. Off by default; turn it on in Settings › Agent memory. (#1988, #2329)

Improved

• opencode is now opencode 2. The image pins opencode 2.0.32 instead of 1.19.0. Managed and Terminal (CLI) sessions use it, and the member guide describes it as the way opencode works. Note that opencode 2 reads only AGENTS.md (no CLAUDE.md fallback) and has no ToDo list. A workspace that tried the opt-in (opencode-major 2) simply uses the pinned version; install-opencode2 and opencode-major explain this and change nothing. (#2105, #2134, #2133)
• Settings › Agent memory is reorganised. Agent memory and Memory snapshots are separate entries, memories open in a list-and-detail view, imports and exports start from one Import & export page, and snapshot history hides Agent Fleet memory writes by default. (#2324)
• Review a revised plan again in the same reviewer session, and a stopped claude session’s carried plan can be reviewed in another session too. (#2219, #2211)
• An expired Claude login in the assistant chat shows Re-authenticate and Retry instead of a raw error, and Re-authenticate opens Settings at that agent’s card. (#2180, #2177)
• claude resumes sooner after it gives up refreshing its login because another claude process held the lock. (#2231)
• Idle workspaces stop more reliably. Background work started by an idle session, such as a dev server, holds the workspace for at most 2 hours (tenant limit background_hold_max), and a Managed cursor, kiro, codex or opencode turn with no sign of life for an hour stops holding it. A running tool, or a turn the Agent cannot observe, still holds. (#2338, #1942)
• kiro Terminal sessions report approval prompts more reliably, and cursor Terminal sessions record token usage per turn. (#2285, #2286)
• The session menu is grouped into sections. (#2189)
• Helper calls such as title suggestions no longer start your MCP servers when they run on claude. (#2334)

Fixed

• A long or multi-line peer message to a busy claude Terminal session arrived truncated. A message claude only queued, or that cursor rejected, was also reported as delivered; it is now reported as queued. (#2195, #2288, #2299)
• create_session with a misspelled agent kind started a claude session; it is now refused. (#2297)
• Switching to a remote branch went wrong when two remotes had a branch of the same name. (#2268)
• A background shell running af-aws-exec or another workspace-agent command did not keep the workspace awake. (#2351)
• Usage chips showed a window whose reset had already passed as near its cap. (#2184)
• Delete working copy hid “Stop the running sessions first” for copies with unpushed or uncommitted work. (#2201)
• The project list emptied when it failed to load, and the active session row hid its state chip. (#2191, #2192)
• On a phone, the WS bar’s port preview buttons spilled out of the popover. (#2308)
• The user guide did not open on a native install without a rootfs. (#2315)
• Malformed host names under the preview domain reached the Console instead of answering 404. (#2240)
• Memory snapshot history stayed on “Loading…” when there were no snapshots or a request failed, and a failed load read as “No snapshots yet”; it now shows the error with Retry. (#2344, #2347, #2349)
• bkt was missing from Settings › Toolchains. (#2179)
• ECS: the missing-EFS-backup warning stayed after a backup plan was added. (#2063, #2066)

Upgrade notes

• Development sign-in is on by default wherever preview subdomains and PUBLIC_BASE_URL are configured. A super admin can turn it off under Dev sign-in in the Admin modal, and AF_DEV_IDP=0 locks it off. Production apps must never trust its issuer.
• Background work now has a 2-hour hold. If your members rely on long-running background jobs in idle sessions, raise the tenant limit background_hold_max (0 = no limit) or set AF_BACKGROUND_HOLD_MAX.
• Your opencode conversations carry over. The first opencode 2 start on a workspace converts opencode’s database (~/.local/share/opencode/opencode.db) in place and imports the existing sessions once, with the same session ids, so Managed and Terminal (CLI) sessions resume as before.
• The opt-in’s own data is not merged. If you ran opencode-major 2 before, the sessions that exist only in its private database (~/.local/share/agent-fleet/opencode2-data) are not visible to the pinned opencode 2. Nothing is deleted; remove that directory and ~/.local/share/agent-fleet/opencode2 when you no longer need them.
• Going back to opencode 1. Rebuild the image with --build-arg OPENCODE_VERSION=1.19.0 and restart the workspaces. opencode 1 sees every conversation from before the upgrade, but not the ones created, or the turns added, under opencode 2. To undo the upgrade exactly, copy ~/.local/share/opencode/opencode.db* before the first start on this release and put the copies back after the way back.

Agent CLI pins: Claude Code 2.1.302, Codex 0.163.0, Copilot 1.0.98, Antigravity 1.4.2, Cursor 2026.10.16-e3cb207, Kiro 2.32.0, OpenCode 2.0.32 and Muse Code 1.4.10-R6427.1.