Agent Teams

Agent Teams operate one level above subagents. The unit is not a child agent inside a session — it is a full Claude Code session, and several of them work together.

The distinguishing capability: they can talk to each other

Cross-session messaging means one session can send a message to another by name. That is qualitatively different from delegation: a subagent reports upward and ends, while sessions in a team persist and coordinate.

Agent view is the screen for watching several of them at once.

When this is the right shape

• Work that splits cleanly across separate working directories — which is why worktrees are documented alongside it.
• Long-running efforts where each strand needs its own persistent context.
• Cases where you want to interject with one strand without disturbing the others.

What it does not do

• It does not remove merge conflicts. Two sessions editing the same files still conflict. Worktrees exist to keep them apart.
• It is not cheaper. Several sessions consume several sessions’ worth of usage.
• It is not the right tool for a fan-out search. That is a subagent. Comparison.

Availability

Documented as a Claude Code capability, and gated the way Claude Code is — Pro and above. Whether agent-team orchestration is reachable through the API is not stated in the sources checked, so that column is left as not documented.