Claude Maestro

Claude Maestro: Multi-Agent Claude Code Orchestration

**Run multiple Claude Code agents in parallel, each in its own tmux pane with an isolated git worktree.** One script. No frameworks. No experimental flags.

Drop one shell script into your project. Get parallel agents with file locking, inter-agent messaging, and automatic branch management — zero configuration.

---

Table of Contents

1. The Problem
2. The Solution
3. How It Works
4. Setup (1 minute)
5. Usage
6. Communication Between Agents
7. Team Patterns
8. Customizing
9. FAQ
10. Architecture

---

The Problem

You're deep into a complex task with Claude Code. Maybe you need to:

• Refactor a module while another agent writes tests for the old behavior
• Have a security reviewer scanning your codebase while you implement features
• Run three agents with competing hypotheses about a bug, in parallel
• Split a large feature across multiple agents to finish faster

Running multiple terminals manually is chaos. Two agents edit the same file — merge conflict. No one knows what the other is doing. You spend more time coordinating than coding.

The alternatives aren't great either:

Approach	Problem
Multiple terminals manually	File conflicts, no coordination, chaos
Agent Teams (experimental)	Requires experimental flag, limited control
Python orchestrator frameworks	Heavy setup, dependencies, over-engineered
Single agent, sequential work	Slow — you're leaving parallelism on the table

---

The Solution

**`orchestra.sh`** — a single shell script (~400 lines) that:

• Creates a tmux session with one pane per agent (tiled grid)
• Gives each agent its own git worktree (isolated filesystem — zero merge conflicts)
• Sets up a shared .orchestra/ directory for inter-a