Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Background TasksArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release
Runs only under the remote-driven fleet-view enablement check.
What
Starting the fleet view with claude agents now also marks the session as restricted as part of its setup. It sits behind the same fleet-view enablement check as the rest of that command, which is driven by remote configuration rather than anything in this build, so whether it runs is decided server-side.
Evidence
setRestrictedSession
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Names in the bundleclaude agents
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.
Added sinceA small documentation edit on What's new touched a line naming claude agents after this was published.Also this week: **fork mode** is on by default in interactive sessions, so Claude can delegate a side task to a subagent that inherits the full conversation; **GitLab** merge request URLs work with `--worktree` and the `claude agents` view…whats-new/indexsee the edit
Confirmed sinceAnthropic's documentation has since written up claude agents, on Claude Code changelog.* Fixed `claude agents`: pressing ← again at a natural pace to go back to the agent list no longer gets ignored until you pause for over a secondchangelogsee 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 claude agents, on Claude Code changelog.
Anthropic's release notes agreeWindows: Fixed the claude agents list not responding to the keyboard after detaching from a session, or when launched in a terminal tab left…
