O
oarthurbg/orchestra
Many voices. One composition. A Claude Code plugin for running one project with an orchestrator session and…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"oarthurbg-orchestra": {
"command": "npx",
"args": ["orchestra-install"]
}
}
}Parsed from the README we fetched on 2026-11-03; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"oarthurbg-orchestra": {
"command": "npx",
"args": ["orchestra-install"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio oarthurbg-orchestra -- npx orchestra-install
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 2 ★ · oarthurbg/orchestra · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-04 · last seen 2026-11-14 · seen 11× · listed by 1 sources
- Score
- score 103 · 2 ★ · 1 sources · repo
- Install
npx orchestra-install
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx orchestra-install. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
oarthurbg/orchestra；first catalogued 2026-11-04；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# orchestra
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Run one project with many Claude Code sessions at once.
One session plans. One session per feature builds. You make the decisions, and every change is reviewed before it merges.
orchestra is a Claude Code plugin, built while developing an internal media-planning app. It works for any kind of app, new or already under way: no database, server or Docker required.
## How it works
1. You and the maestro plan the app. It splits the work into features and opens one session for each, as many at once as your machine and your plan limits allow.
2. Each principal builds one feature in its own worktree: it mocks up and specs with you, then sends subagents to plan, build, review and test.
3. Every feature ends as a pull request. The maestro checks it and merges it. When a session needs a decision, it asks you.
## Who does what
Wherever orchestra draws a session, its shape tells you the role and its fill tells you the state: solid is running, outlined is idle, over a heavy rule is waiting on you. Agents has the nine subagents.
## See it
The band sits above the prompt in every session: your plan limits, when the week will run out, and who needs you, most urgent first. It also offers new versions of orchestra. More about the band.
The liveview is a page with every workstream's progress, ETA and timeline. It runs on your machine, uses no tokens, and opens on your phone too, over Tailscale. More about the liveview.
The inbox lists every question waiting on you, oldest first, with the mockups and specs you need to answer it.
## Why orchestra
Ship features in parallel. One session and one worktree per feature, as many as your machine and plan allow. Read more
The right model for each job. Nine subagents: Opus for judgment, cheaper models for chores. Read more
A proven process, built in. Brainstorm, spec, plan, build, review, PR, with the best skill at each stage. Read more
Nothing merges unreviewed. Spec, quality and finish reviews, then the whole branch. No session merges its own PR. Read more
No surprises with your limits. The band shows what is left, when the week runs out, and who needs you. Read more
See everything from anywhere. Progress, ETAs and your questions, on your phone too. No tokens. Read more
Fewer tokens to find code. A language server instead of grep: up to 65% less, measured. Read more
Long sessions stay sharp. A handoff note and a clear past 250k tokens; nothing lost on a compact. Read more
Cheaper waits. The prompt cache stays warm while subagents run. Read more
Safe to leave running. You set what sessions may do alone; a branch guard blocks direct pushes. Read more
## Does it help?
Measured, not estimated: every number comes from a script in bench/, explained in Benchmarks.
Code navigation saves tokens. Finding who calls what with a language server instead of grep reaches the same answers with fewer tokens, most of all for small models on big codebases.
One session plans. One session per feature builds. You make the decisions, and every change is reviewed before it merges.
orchestra is a Claude Code plugin, built while developing an internal media-planning app. It works for any kind of app, new or already under way: no database, server or Docker required.
## How it works
1. You and the maestro plan the app. It splits the work into features and opens one session for each, as many at once as your machine and your plan limits allow.
2. Each principal builds one feature in its own worktree: it mocks up and specs with you, then sends subagents to plan, build, review and test.
3. Every feature ends as a pull request. The maestro checks it and merges it. When a session needs a decision, it asks you.
## Who does what
Wherever orchestra draws a session, its shape tells you the role and its fill tells you the state: solid is running, outlined is idle, over a heavy rule is waiting on you. Agents has the nine subagents.
## See it
The band sits above the prompt in every session: your plan limits, when the week will run out, and who needs you, most urgent first. It also offers new versions of orchestra. More about the band.
The liveview is a page with every workstream's progress, ETA and timeline. It runs on your machine, uses no tokens, and opens on your phone too, over Tailscale. More about the liveview.
The inbox lists every question waiting on you, oldest first, with the mockups and specs you need to answer it.
## Why orchestra
Ship features in parallel. One session and one worktree per feature, as many as your machine and plan allow. Read more
The right model for each job. Nine subagents: Opus for judgment, cheaper models for chores. Read more
A proven process, built in. Brainstorm, spec, plan, build, review, PR, with the best skill at each stage. Read more
Nothing merges unreviewed. Spec, quality and finish reviews, then the whole branch. No session merges its own PR. Read more
No surprises with your limits. The band shows what is left, when the week runs out, and who needs you. Read more
See everything from anywhere. Progress, ETAs and your questions, on your phone too. No tokens. Read more
Fewer tokens to find code. A language server instead of grep: up to 65% less, measured. Read more
Long sessions stay sharp. A handoff note and a clear past 250k tokens; nothing lost on a compact. Read more
Cheaper waits. The prompt cache stays warm while subagents run. Read more
Safe to leave running. You set what sessions may do alone; a branch guard blocks direct pushes. Read more
## Does it help?
Measured, not estimated: every number comes from a script in bench/, explained in Benchmarks.
Code navigation saves tokens. Finding who calls what with a language server instead of grep reaches the same answers with fewer tokens, most of all for small models on big codebases.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/oarthurbg-orchestra/)
- Source
- github · https://github.com/oarthurbg/orchestra
- Browse by field
- Open source
- Traction
- 2 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.