Claude Clue #12: Let Claude Spawn More Claudes

Claude Code can spin up multiple Claudes to work in parallel, and it is genuinely one of those features that feels a bit like magic when you watch it happen. Think Mickey and the brooms in Fantasia, except hopefully with better outcomes. The orchestrating Claude manages the whole operation, spawning workers, assigning tasks, and using git worktrees to keep everything tidy. Each spawned Claude gets its own branch, does its thing, and then everything merges back together when the work is done. You can keep your main Claude relatively unburdened by having it spin up a dedicated orchestrator Claude whose whole job is managing the chaos.

Recently, I completed a code audit that surfaced dozens of issues, including state management problems touching almost the entire codebase. Each fix would have taken anywhere from 5–45 minutes on its own, maybe hours. I told Claude I wanted to address these issues simultaneously, and we worked out a plan: spawn one team of agents to find and fix all identified issues in parallel, then spawn a team of reviewers to verify the changes. An orchestrator agent set a base commit, duplicated it into worktrees for each agent, created agents with their instructions, and spawned reviewers when they finished. Once complete, it sequentially merged everything back into my working branch. I watched it all happen in real time, and when one agent started drifting off-task, I reached in mid-flight, adjusted its instructions, and got it back on track.

The secret? Just tell Claude to do things in parallel. Almost too easy.

Prototyped with AI, published for humans.

Another pro-tip from Roscoe!