Claude Orchestra Get in touch

PrototypeTypeScript · Electron

Claude Orchestra

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

One performance

A plan fans out, then the work merges back in.

The Conductor turns your idea into a Score. Section Leaders split their sections into tasks, and each task gets its own git worktree and its own claude -p session. Finished work is checked by running the task’s verify commands, then lands on main through a single merge queue, with the cost written into the commit.

Idea “A recipe box. Save recipes, tag them, and build a shopping list for the week.”

Performance symphony

  1. Conductor model best · strict done $0.41 of $5.00
  2. s-api Section Leader sonnet · strict done $0.14 of $3.00
  3. t-1 Recipe store and schema worktree t-1-a1 done $0.62 of $3.00
  4. t-2 Tags and search worktree t-2-a1 · after t-1 done $0.48 of $3.00
  5. s-web Section Leader sonnet · strict done $0.12 of $3.00
  6. t-3 Recipe list and editor worktree t-3-a1 done $0.91 of $3.00
  7. t-4 Weekly shopping list worktree t-4-a1 · after t-2 done $0.77 of $3.00
Score
v1 · movements m1, m2
Sections
s-api, s-web
Plan gate
approved
Spent
$3.45
Sessions
7
Merged
4 of 4

main merge queue

  1. tag v0.1.0DELIVERY.md written by the Conductor
  2. feat(web): weekly shopping list Orchestra-Task: t-4
    Orchestra-Agent: coder@v1 (section s-web)
    Orchestra-Cost-USD: 0.7700
  3. feat(api): tags and search endpoints Orchestra-Task: t-2
    Orchestra-Agent: coder@v1 (section s-api)
    Orchestra-Cost-USD: 0.4800
  4. feat(web): recipe list and editor Orchestra-Task: t-3
    Orchestra-Agent: coder@v1 (section s-web)
    Orchestra-Cost-USD: 0.9100
  5. feat(api): recipe store and schema Orchestra-Task: t-1
    Orchestra-Agent: coder@v1 (section s-api)
    Orchestra-Cost-USD: 0.6200
  6. seed commitmade when the project was created
An animated illustration of one run of the default symphony preset. The idea, the plan and every dollar figure are made up. The roles, models, per-task caps, worktree names and commit trailers are Claude Orchestra’s shipped defaults.

Orchestras

Pick how many layers you want.

Five presets ship with it. You can also build your own hierarchy of any depth in the Orchestra Editor, and change any role’s prompt, model, tools, permission profile and budget.

  1. solo

    One coder does everything

    No planning step and no planning spend.

  2. duet

    Conductor, then one coder

    A plan first, then the tasks one at a time.

  3. chamber

    Conductor and parallel musicians

    The Conductor writes the tasks itself and they run side by side.

  4. symphony

    Conductor, Section Leaders, Musicians

    The default. Each section gets a leader that breaks it into tasks.

  5. symphony+qa

    Symphony with review

    Adds reviewers and a QA tier on top.

A role

Every agent is a YAML file you can edit.

This is the shipped Musician. Edits save as overrides, so the defaults are always there to go back to. Budgets warn at 75% and pause the task, section or project at 100%.

# roles/coder.yaml (excerpt)
name: coder
title: Musician — Implementation
kind: worker
model: sonnet
effort: high
tools:
  allowed: [Read, Edit, Write, Glob, Grep,
            "Bash(git *)", "Bash(npm *)", ...]
  disallowed: [WebSearch, WebFetch]
permission_profile: standard
limits: { max_turns: 80, max_budget_usd: 3.00,
          max_wall_minutes: 45, retries: 2 }
report_schema: worker-report

From source

It runs on your machine.

It’s a prototype, and there’s no installer to download yet. From a checkout, it needs Node 22, Git 2.40 and a signed-in claude CLI. The daemon and web UI run on 127.0.0.1:4573, and an Electron shell wraps them. Tests run against a fake claude -p that emits real stream-json, so they cost nothing.

npm install
npm run build
npx claude-orchestra doctor   # checks claude, git, auth, port
npx claude-orchestra serve    # http://127.0.0.1:4573

Capabilities

What it does.

Engineers who want to supervise a build and let the agents do the typing.

  1. 01

    Three layers of agents, each working in its own git worktree

  2. 02

    Commits as it goes, with token and cost tracking per task

  3. 03

    Live views of the plan, progress, git graph and spending

  4. 04

    Every prompt, model, tool permission and budget can be edited

Specification

What it’s built with, and when.

Pulled from the repository each time this site is built.

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 hooking it up to the repositories and agents you already run.

This site isn't finished. Anything on it may still change, and none of it is binding until the site is live.