What
The Fleet view (the screen listing background jobs/agents) now accepts a typedAgent value, which flows through to the helper that relaunches the Fleet UI after an app update. When relaunching, this is passed via a new --agent argument, alongside the existing cwdFilter and dispatchDefaults (with an inherited default permission mode stripped out).
Why
This lets a background agent relaunched after an update keep running as the specific agent type it was dispatched with, rather than losing that setting across the relaunch.
Names in the bundle--agent
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on CLI reference touched a line naming --agent after this was published.
| `--bg`, `--background` | Start the session as a [background agent](/docs/en/agent-view) and return immediately. Prints the session ID and management commands. Combine with `--exec` to run a shell command as a background job instead of a …cli-reference see the edit
Confirmed since
Anthropic's documentation has since written up --agent, on multiagent-orchestration.
--agent "$coordinator_id" \managed-agents/multiagent-orchestration see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --agent, on multiagent-orchestration.
Anthropic's release notes agree
Fixed claude agents losing --model, --effort, --permission-mode, --allow-dangerously-skip-permissions and --agent after an auto-update…