Maestro Orchestrator
Every agent in its own worktree. Every merge in your hands.
Orchestrator is the core of Maestro. It runs many Claude coding agents at once, gives each one its own git worktree and branch, shows you their diffs and report cards, and performs the merge itself after you approve.
How it conducts
From backlog to merged, without losing the thread.
01 —
Point it at the backlog.
Dispatch a task and Maestro creates a fresh worktree on maestro/, claims the task, and briefs the agent. A fix that spans coupled repos gets a worktree in each, all on the same branch, and Maestro merges them together.
02 —
Say “do every task in project X.”
A master Claude conducts the section: it lists the backlog, keeps eight to ten workers in flight, re-dispatches as branches land, and answers workers when they ask. You and the orchestrator are peers on the same conversation. It never merges.
03 —
Every branch arrives graded.
A report card on every finished branch, with a summary, a risk level and 0–100 gauges. Triage lanes keep human review, in-flight and needs-review apart. Chat with any agent about its diff, or run /code-review for a deep findings pass.
Adds the distribution statement CSV export behind the existing report permissions. Reuses the statement query; new code is covered by four unit tests. No schema changes.
- •Reuses the existing statement query — no new N+1
- •Four unit tests cover the export path
- •No migration: the export reads existing columns
The Maestro manifesto
We built the conductor, not another console.
You can point a raw agent at a repo and hope. We would rather a person stayed in the loop: reading the diff, steering the work, and owning the call on what lands. So rather than run fleets out of Codex or the Claude console, we built Maestro around that person.
Prove it runs
See it before you merge it.
Every agent can run its own dev servers. Maestro allocates the ports, clones the env and wires the traces.
Per-agent dev servers
Start the app inside any worktree. Many stacks coexist; nothing collides.
:6214 · :6215Ports handled for you
A free port per process, env cloned with PORT and OTEL overridden.
PORT=6214Traces on tap
Every dev server points at one otel-lgtm dashboard, filtered to the agent’s service name. Boot, click, inspect.
otel-lgtm :3000The signature move
Maestro does the merge. Never an agent.
Mergeability is known before you look, with git merge-tree in memory and no checkout. One human-gated button merges --no-ff into main, removes the worktree, archives the
branch and closes the task. Deterministic, every time.
Control
The kill switch is a feature.
Orchestrator keeps the operator in charge, with a way to stop any single agent or the whole fleet at once.
Notifications that matter
Native OS and in-app bell when an agent asks, blocks, finishes or fails, and when a dev server dies.
Stop anything
Stop one agent and watch it log Stopped agent 5 (SIGTERM), or hit the kill switch for the whole fleet.
Command palette
⌘K to reach any agent, task or repo. Installable as a PWA, usable from the couch.
Usage in the open
Token spend by model over time, plus an environmental impact page. No surprises at the end of the month.