Claude Orchestra Get in touch

Prototype · Developer tooling

Claude Orchestra

A hierarchy of agents that takes an idea and gives back a committed codebase.

Engineers who want to supervise a build rather than perform it.

Animated illustration of Claude Orchestra claude-orchestra — session $ claude-orchestra run --scope . resolving workspace … TypeScript indexed 1,284 files · 96 changed analysis complete — 4 findings, 0 blocking $ claude-orchestra report --format=json written to ./report.json UNCHECKED UNWRAP IN RETRY PATH src/net DUPLICATE CONFIG PARSE src/cli DEAD BRANCH AFTER EARLY RETURN src/store TEST ASSERTS ON FORMATTING tests
Animated schematic of a representative session. Command names are real; timings are compressed for the page.
Built on
TypeScript + Electron
Fits the workflow
A step in the pipeline, not a replacement for it
History
13 commits, in a private repository

What it is

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.

Capabilities

What it actually does.

Engineers who want to supervise a build rather than perform it.

  1. Three-tier agent hierarchy

    Three-tier agent hierarchy running in isolated git worktrees

  2. Continuous commits

    Continuous commits with per-task token and cost metering

  3. Live views of the plan

    Live views of the plan, execution, git graph and cost analytics

  4. Every prompt

    Every prompt, model, tool grant and budget editable by the operator

How it works

3 moves, end to end.

This is how Claude Orchestra works, not a set of steps you can follow yet — it is prototype and not distributed.

  1. Drop it in

    Claude Orchestra attaches to the repository or project you already have.

  2. Give it the job

    It takes a concrete task with a defined output, not an open-ended prompt.

  3. Review the result

    Everything it produces is a diff, a file or a report you approve before it counts.

The full technical description

Specification

Made of, and made when.

Read from the repository at build time rather than typed onto a marketing page.

State
Prototype
Discipline
Developer tooling
Shape
Developer tooling
Started
Jul 2026
Last change
Jul 2026
Commits
13
  • TypeScript
  • Electron
  • git worktrees
  • Claude Code
  • TypeScript 94%
  • JavaScript 5%

Next

Put Claude Orchestra in your pipeline

Ask about integrating it with the repositories and agents you already run.

This is a pre-production site. All content is subject to finalisation, and nothing stated here is binding until the site is live.