Dudu-0223
ff563d07e0
Models coordinate subagents through send_message, interrupt_agent, list_agents,
and Team task owners, but every one of those addressed a member by a
36-character Session id. Each new child now has a name, unique among its
creator's children, recorded as a field of the subagent/catalog entry the
creator already appends (payload version 3).
The Session id stays the only execution identity for routing, authorization,
persistence, task ownership, and navigation. A name is a model-facing
reference: 1-32 lower-case letters, digits, or hyphens starting with a letter,
never `lead`, so a UUID never parses as one. Omission selects the first free
`agent-N`; an explicit duplicate or invalid name fails before startup. The
creator reserves the name synchronously at admission and releases it when the
catalog entry commits or startup fails, so no second write, rollback protocol,
or optional naming service exists.
The root is `lead`, and a descendant's full name is its path from the root
without a `lead/` prefix, such as `reviewer/checker`. Sibling-unique segments
make full names tree-unique without a root registry, and cold resume rebuilds
a member's path from the catalogs along its creation chain. A member below an
unnamed historical creator keeps its Session id as its name. resolveName()
reads only the catalogs along the path and grants no authority.
Tools, runtime-authored text, and the Web client consume names: delegation
takes an optional name and returns { kind, subagentId, name }; send_message and
interrupt_agent take `agent`; list_agents rows carry name, status, and
description; Team task results report the owner's name while storage keeps
ownerId; identity runtime context, message framing, and settlement notices use
full names. Recorded sessions, CLI and Web expectations, the Python runtime
snapshots, bilingual docs, an upgrade guide, and an Agent Note follow.
description, kind
| description | kind |
|---|---|
| The team package group: shared task coordination for subagent trees and its model-facing tools. | package-group |
team/ — shared task coordination
English | 中文
Summary
The Team packages let agents in a subagent tree share task ownership and dependencies. The service saves each root Session’s Team selection and task board. The tool plugin exposes task operations and collaboration guidance to the model. Subagent creation, discovery, messaging, and interruption remain in the subagent package family.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
agent-team/ |
Shared task board and saved Team mode for a subagent tree | ctx.agentTeams |
tool-agent-team/ |
Exposes shared task tools while Team mode is enabled | registers on ctx.tools |
Related documentation
- Agent Teams subsystem — task types, events, and the service API.
- Subagent packages — delegation, discovery, and communication.
Dev Note
None.