When to Use Agent Teams
Use this decision framework:| Situation | Tool | Why |
|---|---|---|
| Fully independent work (migrations, convention enforcement) | /batch | No coordination overhead, cheapest option |
| Tasks that report results back (research, analysis) | Subagents | Parent orchestrates, ~4-7x cost |
| Tasks that need to discuss and coordinate | Agent Teams | Shared task list + messaging, ~15x cost |
Delegate Mode Is Essential
Press Shift+Tab to cycle into delegate mode, which restricts the lead to coordination-only tools. In delegate mode, the lead can only:- Create and manage tasks
- Send messages to teammates
- Review and approve plans
- Synthesize results
A Typical Session
Practical Advice
- Sweet spot: 3-5 teammates. Fewer underutilizes parallelism; more creates coordination overhead exceeding the throughput gain.
- Use plan approval for high-stakes work — teammates submit plans before implementing, the lead reviews.
- Prepare for no session resumption. If you need to
/resume, tell the lead to spawn replacement teammates. - Nudge on task status lag. Teammates sometimes forget to mark tasks complete — check with Ctrl+T.
← Prev: Permutation Frameworks · Next: Permission Modes →