Claude Code Agent Teams
/install claude-code-teams
Claude Code Agent Teams
Orchestrate multiple Claude Code agents working together on complex tasks. Agents coordinate through a shared task list, message each other directly, and work in parallel on independent scopes.
When to Use
✅ Use for parallel independent work:
- Multi-lens code reviews (security, performance, tests in parallel)
- Debugging with competing hypotheses (test theories simultaneously)
- Full-stack features (frontend/backend/tests by separate specialists)
- Architecture decisions (adversarial debate produces stronger ADRs)
- Cross-domain investigations (bottleneck analysis across systems)
- Data-parallel work (inventory classification, bulk refactoring)
❌ Don't use for:
- Sequential work with tight dependencies
- Same-file edits (conflict risk)
- Simple tasks (coordination overhead > benefit)
- Learning/exploration (single agent with full context is better)
Rule of thumb: Teams multiply token cost 3-4x. Use only when parallelization benefit exceeds coordination overhead.
Quick Start
1. Enable Feature
Environment variable:
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Or settings file (~/.claude/settings.json):
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
2. Validate Setup
./scripts/validate-setup.sh
Checks for: env var set, claude CLI available, tmux installed (optional).
3. Pick Template
| Template | Use Case |
|---|---|
parallel-review.md |
Multi-lens code review (security + performance + tests) |
competing-hypotheses.md |
Debug by testing competing theories |
fullstack-feature.md |
Frontend/backend/tests coordination |
architecture-decision.md |
ADR with adversarial debate |
bottleneck-analysis.md |
Cross-domain performance investigation |
inventory-classification.md |
Data-parallel classification/refactoring |
Each template includes: when to use, team structure, copy-paste spawn prompt, expected outcomes.
4. Spawn Team
claude --pty
# Paste spawn prompt from template
Monitor with ./scripts/team-monitor.sh (separate terminal) or Ctrl+T (in Claude Code).
Core Principles
- Clear file boundaries - Each teammate owns different files/directories (prevents conflicts)
- Use delegate mode - Lead coordinates, teammates implement (include in spawn prompt)
- Size tasks appropriately - 5-6 self-contained tasks per teammate
- Wait for completion - Don't let lead merge results while teammates are mid-task
- Start with research - Spawn researchers before builders to establish shared understanding
Cost Management
Agent teams multiply token usage 3-4x vs single session. Each teammate has its own context window.
Optimize with:
- Model mixing - Opus for lead (strategic), Sonnet for teammates (tactical) = ~40% savings
- Minimize broadcasts - Direct messages only (broadcasts copy to all teammates)
- Right-size teams - 3 teammates usually optimal; 6+ only for highly parallel work
See references/cost-management.md for detailed strategies.
Troubleshooting
Teammates not spawning?
- Verify
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1is set - Restart Claude Code after setting env var
File conflicts?
- Define explicit file boundaries in spawn prompt (directory-level ownership)
Lead implementing instead of coordinating?
- Add "Use delegate mode: coordinate but don't implement" to spawn prompt
- Or press Shift+Tab to cycle into delegate mode
See references/troubleshooting.md for full list.
Automation
Monitor progress:
./scripts/team-monitor.sh
Cleanup (graceful shutdown):
./scripts/team-cleanup.sh
Display Modes
In-process (default) - All teammates in main terminal
Shift+Up/Down- Select teammateCtrl+T- Toggle task listEscape- Interrupt teammate
Split-pane (requires tmux or iTerm2) - Each teammate gets own pane
- Set
teammateMode: "tmux"in~/.claude/settings.json
References
templates/- 6 copy-paste ready spawn prompts with usage guidancescripts/- Automation helpers (validate, monitor, cleanup)references/best-practices.md- When to use teams, task sizing, file boundariesreferences/cost-management.md- Token optimization strategiesreferences/troubleshooting.md- Common issues and solutionsexamples/- Real-world walkthroughs (PR review, bug hunt, feature build)
Comparison
| Approach | Best For |
|---|---|
| Single session | Sequential work, exploration |
| Agent teams (this skill) | Parallel independent tasks with coordination |
| OpenClaw subagents | Background work, long-running tasks |
Contributing
Found a useful pattern? Submit PR with:
- Template or example
- When to use + team structure
- Spawn prompt + expected outcomes
Credits
Built with insights from Claude Code documentation, ClaudeFast patterns, and OpenClaw community.
Repository: https://github.com/matthew-a-gordon/claude-code-teams
License: MIT
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install claude-code-teams - After installation, invoke the skill by name or use
/claude-code-teams - Provide required inputs per the skill's parameter spec and get structured output
What is Claude Code Agent Teams?
Coordinate multiple Claude Code agents to work in parallel on independent tasks like multi-lens reviews, debugging, and full-stack features with defined file... It is an AI Agent Skill for Claude Code / OpenClaw, with 1280 downloads so far.
How do I install Claude Code Agent Teams?
Run "/install claude-code-teams" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Claude Code Agent Teams free?
Yes, Claude Code Agent Teams is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Claude Code Agent Teams support?
Claude Code Agent Teams is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Claude Code Agent Teams?
It is built and maintained by matthew-a-gordon (@matthew-a-gordon); the current version is v1.0.0.