How it works
A hierarchy of coding agents that turns an idea into a committed codebase. The full technical description of Claude Orchestra — what it does, what it is made of, and what state it is in.
The premise
A self-hosted orchestrator that takes a plain-English application idea and produces a working, git-committed codebase, built by a tiered hierarchy of agents running as parallel headless sessions in isolated git worktrees.
A Conductor turns the idea into a machine-readable plan. Section Leaders decompose their sections into tasks. Musicians execute those tasks in parallel. The system commits continuously, meters every token and dollar per task, and renders the plan, live execution, git graph and cost analytics in a desktop shell. Every layer is user-editable — tier count, prompts, models, tools, permissions and budgets.
What is included
Three-tier agent hierarchy running in isolated git worktrees
Continuous commits with per-task token and cost metering
Live views of the plan, execution, git graph and cost analytics
Every prompt, model, tool grant and budget editable by the operator
How it is built
Claude Orchestra is built on TypeScript, Electron, git worktrees and Claude Code.
The repository is 94% TypeScript, 5% JavaScript by volume — a description of what the work actually consists of rather than what it is filed under.
It carries 13 commits since Jul 2026, most recently changed in Jul 2026.
The method behind it
Every project here starts as a written specification, and the specification stays authoritative once code exists. The repository keeps a build plan with live status, an append-only decision log recording where the implementation departed from the plan, and a handoff document describing the true current state — including the parts that are not finished.
That is why a portfolio this wide is not a shallow one, and it is why this page can describe the product without overstating it.
Current state
Prototype. Working, not yet finished.
The source is private. What this page claims is checkable against the product itself, not the repository.
Next
Put Claude Orchestra in your pipeline
Ask about integrating it with the repositories and agents you already run.