agent teams
An experimental (research preview) agentic pattern where multiple agents communicate through a shared task list, enabling peer-to-peer coordination and direct messaging between agents
As defined in Every Claude Code Workflow Explained (& When to Use Each)
Where it comes up · 1
Most important claims · 5 of 5Search all claims for “agent teams” →
- Agent teams are a new experimental feature (shipped with Opus 4.6 as research preview) that allow multiple agents to share information through a shared task list rather than a central hub, enabling cross-agent communication, challenge, and adaptation.Every Claude Code Workflow Explained (& When to Use Each)
- Agent teams should only be used for genuinely complex projects requiring cross-collaboration between agents; most work should be solved with sub-agents or single-session approaches due to the 4-7x token multiplication and community concern that agent teams produce large quantities of work without ensuring the work is the right work.Every Claude Code Workflow Explained (& When to Use Each)
- A practical example of when agent teams are appropriate is building a complex SaaS application with a frontend developer, backend developer, and testing developer that need to communicate and coordinate as they build.Every Claude Code Workflow Explained (& When to Use Each)
- Agent teams require enabling a flag (claude_code_experimental_agent_teams=1) in settings.json as an environment variable, and must be explicitly specified in prompts by the user—unlike sub-agents, they do not activate automatically.Every Claude Code Workflow Explained (& When to Use Each)
- Agent teams can be navigated in the terminal using Shift+Up and Shift+Down to switch between teammates, and users can message any teammate directly or communicate through the team lead.Every Claude Code Workflow Explained (& When to Use Each)