What probably matters to youSection of the release
What
A new internal function enumerates every entry in the task registry (the internal bookkeeping list of running agents) and classifies each one as either a local_agent (with its id, type, and parent agent id) or an in_process_teammate (with its id and name). The resulting list also includes each entry's status, which agent spawned it, and a resolved display name. This appears to be the implementation behind an agent.list-style listing.
Why
This gives a more complete and structured view of what agents and teammates are currently active, which matters for anything that needs to inspect or manage multiple running agents at once.
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 sinceAnthropic's documentation has since written up agent.list, on Claude Code changelog.* Added `agent.spawn` for teammates, one agent id across plugin hook events, and idle and waiting states in `$.agent.list()`changelogsee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up agent.list, on Claude Code changelog.
