Orchestra
lcsmas/orchestra
Executa agentes Claude paralelos em worktrees Git isoladas com spawning recursivo
Ver no GitHubOrquestrador de agentes Claude Code paralelos em worktrees isoladas do Git. Permite que agentes criem novos agentes autonomamente, cada um em seu próprio branch e diretório, com dashboard central para monitoramento em tempo real, visualização de diffs e criação de PRs com um clique.
Instalação
npx convez-ai lcsmas/orchestra1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Paralelizar grandes refatorações de código com múltiplos agentes autônomos
- Monitorar múltiplos branches de trabalho simultâneos em um único dashboard
- Automatizar fluxo completo de desenvolvimento: código → commit → push → PR
Veredito

Orchestra é uma ferramenta sofisticada para times que precisam de paralelização avançada de agentes. O suporte a spawning recursivo e worktrees isoladas oferece controle fino, mas exige setup especializado (Node 20+, CLI do Claude, gh) e compreensão profunda de Git — recomendado para engenheiros sênior.
README
A tradução para o português deste README ainda está na fila.
Orchestra
A Conductor-like app for Linux: run parallel Claude Code agents in isolated git worktrees — and let agents spawn agents.
If you've seen Conductor on macOS, Orchestra is that idea for Linux (it runs on macOS and Windows too, built from source). Each agent gets its own branch in its own git worktree, and you watch them all from one dashboard: live terminal, cumulative diff, one-click PR.

What makes Orchestra different
Agents can spawn other agents. Every Orchestra agent is told, at session start, that it can delegate independent work to a brand-new worktree with its own autonomous agent — one curl to Orchestra's local socket and the new workspace appears in the dashboard, branch cut from base, agent already working. Spawned agents get the same capability, so a worktree agent can spawn worktree agents that spawn worktree agents. Ask one agent to parallelize a refactor and watch the sidebar fill up.
Everything else you'd expect is there:
- Isolated worktrees — each workspace is a real
git worktree(own directory, ownHEAD, shared.git); agents never clobber each other - Live terminals — real TTY per agent, full color, resize, scrollback
- Diff-first review — side-by-side Monaco diff per workspace, refreshing while the agent works
- One-click PR — commit → push →
gh pr createfrom the dashboard - Hook-based status — running/waiting flips off Claude Code's own hooks, no polling or terminal scraping
- Self-naming branches — the agent renames its branch once it understands the task
- Per-repo setup scripts and one-step archive (worktree + branch removed together)
Install
Linux (AppImage)
Download the latest Orchestra.AppImage from the releases page, then:
chmod +x Orchestra.AppImage
./Orchestra.AppImage
Note: Requires FUSE. Without it, run with
--appimage-extract-and-run.
ARM64/Asahi: no pre-built AppImage yet — build from source for a native build.
macOS / Windows
No pre-built binaries yet — build from source. Contributions to the release pipeline welcome.
Build from source
Requires Node 20+, plus the claude CLI and gh on PATH. On Linux you'll also need build tools for the node-pty native module (build-essential on Debian/Ubuntu, gcc-c++ make on Fedora).
git clone https://github.com/lcsmas/orchestra.git
cd orchestra
npm install
npx electron-rebuild # rebuild node-pty for Electron's node ABI
npm run dev # vite + electron, hot reload
npm run build produces a distributable in release/.
How it works
- Worktrees — each workspace lives at
~/.orchestra/worktrees/<repo>-<branch>-<uid>/, created withgit worktree addoff the configured base branch. Archiving removes the worktree and deletes the branch. - Agents — spawned via
node-ptyin the worktree, wired to an xterm.js terminal in the UI. - Hooks — Orchestra installs Claude Code hooks into each worktree's
.claude/settings.local.json. They talk to a Unix-socket HTTP server in the main process: activity status, agent-driven branch rename, and the/spawnendpoint that lets any agent create a new workspace + agent. All hooks are env-guarded, so runningclaudeoutside Orchestra is a silent no-op. - PRs —
commit → push -u origin <branch> → gh pr create --base <baseBranch>.
Storage
- Config + workspace list:
<userData>/orchestra/store.json - Worktrees:
~/.orchestra/worktrees/ - Per-workspace setup logs:
<worktreePath>/.orchestra/setup.log
Contributing
Issues and PRs welcome. For non-trivial changes, please open an issue first to discuss the approach.
License
Apache License 2.0 — see LICENSE.