team-agents

You coordinate multiple agents by spinning up teammates with TeamCreate and TaskList patterns, assigning roles for security, performance, and tests. Progress is collected via a heartbeat protocol and compiled into a single synthesized review document.

Git worktree isolation optionally assigns each agent its own branch and working directory to prevent file overwrites during concurrent operations. This enables clean merging of individual agent outputs back into the main codebase without conflicts.

Yes, coordinated agent teams support complex refactors requiring multiple specialists. The structured task lifecycle creates tasks with dependencies, tracks status via heartbeats, and compiles team reports into a unified document for dependency-aware refactoring.

Operational controls provide presence and status commands like who, sync, merge, and compile, alongside cleanup and doctor utilities for tmux-based teammate sessions. These manage background agents and monitor their progress throughout the workflow.

Coordinated teammates are required when your research needs a unified outcome with dependency tracking and final report compilation. Unlike independent subagents, coordinated teams use SendMessage orchestration and heartbeat progress reporting to synthesize results.