Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

Fleet view background-agent relaunch can now target a specific agent type

Fleet view can now relaunch a background agent as a specific agent type after an update

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaBackground Taskswhat it touches
KindNew Featuresin v2.1.274,
Use it now Notable

Fleet view can now relaunch a background agent as a specific agent type after an update

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.

Read from
Names in the bundle--agent
Since it was published

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.

Confirmed since Anthropic's documentation has since written up --agent, on multiagent-orchestration. --agent "$coordinator_id" \ managed-agents/multiagent-orchestration see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --agent, on multiagent-orchestration.
Anthropic's release notes agreeFixed claude agents losing --model, --effort, --permission-mode, --allow-dangerously-skip-permissions and --agent after an auto-update…

See this entry in the whole of v2.1.274 →