agent-teamslisted

# Agent Teams > **Experimental**: Agent teams require the `--enable-teams` flag and may change between Claude Code versions. ## When to Use This Skill | Use agent teams when... | Use subagents instead when... | |------------------------|------------------------------| | Multiple agents need to work in parallel | Tasks are sequential and interdependent | | Ongoing communication between agents is needed | One focused task produces one result | | Background tasks need progress reporting | Agent output feeds directly into next step | | Complex workflows benefit from task coordination | Simple, bounded, isolated execution | | Independent changes to the same codebase (with worktrees) | Context sharing is fine and efficient | ## Sub-Agent Caveat: Spawn Teams from the Main Thread `TeamCreate`, `Agent`, and the related parallel-spawn tools may not be present in a **sub-agent's** tool surface, even if the parent conversation has them. A sub-agent designed to orchestrate its own team can silently degrade to sequential single-thread execution — same content, much longer wall-clock — without surfacing the failure until its post-completion summary. **Authoring guidance:** | Situation | Recommended pattern | |-----------|---------------------| | Fan-out from the main conversation | Spawn the team / parallel `Agent` calls directly — full tool surface available | | Sub-agent orchestrating its own team | Avoid by design when possible: split the work so the main thread does the fan-out |