A placeholder registry is called from the /agents view but registers an empty object nobody reads.
What
Opening the background-agents fleet view (/agents) now loads an extra module and calls a registration step before drawing anything. It registers an empty object and no code reads it back, so there is no visible effect either way.
Details
registerToolHosts()stores a literal{}into a per-host singleton; the singleton exposes a runtime value that falls back to a frozen empty object, plus a flag saying whether anything was registered.- Neither of those is read anywhere in the build, and
{}is the only value ever registered. This is a seam wired up ahead of what will eventually fill it.
Evidence
registerToolHosts
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/agents
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 Manage multiple agents with agent view touched a line naming /agents after this was published.
To compare agent view with subagents, agent teams, and worktrees, see [Run agents in parallel](/docs/en/agents). Agent view runs sessions on your machine and you dispatch each one; to have Claude start and track parallel sessions in the cl…agent-view see the edit
Confirmed since
Anthropic's documentation has since written up /agents, on permission-policies.
agent=$(curl -fsSL https://api.anthropic.com/v1/agents \managed-agents/permission-policies see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /agents, on permission-policies.