Toolkit
Capability 05 · reviewed 2026-08-01
On this page2 sections
Multi-Agent Coordination
“Multi-AgentA worker you delegate to: brief it, and it takes steps on its own. A chatbot answers; an agent acts.An LLM that runs tools in a loop toward a goal — it acts, checks the result, decides the next step, and repeats until done.Full definition” is not one architecture. The decisive variable is coordination topology: who can create work, who owns shared state, how results move, and whether workers communicate only through a coordinator or directly with peers.
Three Topologies
- Coordinator and workers — a lead decomposes work, spawns isolated agents, and collects their results.
- Peer team — agents have independent sessions plus direct messaging and shared task state.
- External orchestrator — a workflow engine owns scheduling, retries, state, and evidence while agents perform bounded steps.
Claude Code's documented agent teams use independent teammate sessions, a shared task list, mailboxes, and peer messaging, but Anthropic still labels the feature experimental. Codex documents parallel subagents whose results return through the main coordinator; the reviewed source does not describe a peer mailbox or shared task ledger. Copilot CLI Fleet provides coordinator-led parallel execution and documents sibling-agent messaging.
Those are semantic differences, not naming differences.
When Teams Pay
Use multiple agents for genuinely independent work, competing hypotheses, or separate review perspectives. Avoid them when tasks share files, depend on the previous result, or cannot state a crisp completion contract.
The cost model includes more than tokens: coordination messages, duplicate context, merge conflicts, verification, and recovery from partial failure. Start with the smallest useful fan-out and measure elapsed time, defect rate, and total model usage against a single-agent baseline.
The deeper lenses retain Claude Code team examples. Do not translate a peer-team design directly onto a coordinator-only surface without replacing its communication and shared-state assumptions.
Documented coverage · 2026-08-01
Multi-Agent Coordination by product
These classifications are documentation findings, not empirical runtime tests. Surface names are explicit because product-family claims are too coarse.
Claude Code
Anthropic
Agent teams provide independent teammate sessions, a shared task list, mailboxes, and peer messaging, but Anthropic still labels the feature experimental.
Basis: documentedSources: 1
The reviewed experimental agent-teams reference does not establish equivalent IDE and hosted coordination behavior.
Basis: documentedSources: 1
OpenAI Codex
OpenAI
Codex runs parallel specialized subagents and collects results through the main coordinator. The reviewed docs do not describe a peer mailbox or shared task-ledger topology.
Basis: documentedSources: 2
Hosted parallel subagents are documented as coordinator-managed workflows; the source does not describe a peer team with shared task state.
Basis: documentedSources: 2
GitHub Copilot
GitHub
Copilot CLI Fleet decomposes work across parallel subagents and documents sibling-agent discovery and messaging.
Source register
Multi-Agent Coordination sources
Primary vendor documentation reviewed on the date shown. Links may change after publication.
- Orchestrate teams of Claude Code sessions (opens in a new tab)
Anthropic · official docs · accessed 2026-08-01
- Subagents (opens in a new tab)
OpenAI · official docs · accessed 2026-08-01
- GitHub Copilot CLI command reference (opens in a new tab)
GitHub · official docs · accessed 2026-08-01
- Running tasks in parallel with Copilot CLI (opens in a new tab)
GitHub · official docs · accessed 2026-08-01
Comparative implementation depth