claudeers.
// Developer Tools

Orchestra-Board

🎼 Be the maestro of your AI orchestra. A desktop canvas where you drop Claude Code, Codex and other CLI agents, each in a real terminal, and link them: rela…

// Developer Tools[ cli ][ api ][ desktop ][ web ][ claude ]#claude#ai-agents#antigravity#claude-code#codex#developer-tools#electron#mcp#devtools◷ MIT$open-sourceupdated 17 days ago

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up Orchestra-Board (git-clone project) into my current project.
Found on https://claudeers.com/orchestra-board
Repo: https://github.com/Adoraay/Orchestra-Board
Homepage/docs: —
Detected install method: git-clone → git clone https://github.com/Adoraay/Orchestra-Board
Category: devtools. Platforms: cli, api, desktop, web.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or clone
git clone https://github.com/Adoraay/Orchestra-Board

// compatibility

Platformscli, api, desktop, web
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageJavaScript

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

Orchestra: be the maestro of your AI orchestra

A big canvas where you drop AI coding agents, each in its own real terminal,
and wire them together so they hand work to each other.

Claude Code · Codex · Gemini CLI · Aider · and any CLI you add  ·  🇫🇷 Lire en français

Download for Windows   Download for macOS

Download What's new Demos Features Tutorial Shortcuts Privacy FAQ Build

An Orchestra board: a Claude Code lead delegating to a Codex and a Claude Code reviewer, and running commands in a visible terminal

[!NOTE] Orchestra is an independent open-source project. It is not affiliated with Anthropic, OpenAI or Google. It only starts the CLIs you already use, with your own accounts, on your machine.

Orchestra-Board

Orchestra-Board Why Orchestra

You already run Claude Code or Codex in a terminal. Orchestra puts as many of them as you want side by side on an infinite map, each one in a real terminal, and lets you link them.

Orchestra-Board
1. Drop your agents
Pick a folder in the explorer and drag Claude Code, Codex or any CLI onto the map. Each tile is a real terminal.
Orchestra-Board
2. Link them
Draw a link from one tile to another: relay a finished answer, let a lead delegate, or give an agent a terminal or a shared note.
Orchestra-Board
3. Let them work
Watch every exchange in the log, answer permissions as they come, and get a glow, a sound and a notification when an agent finishes.
  • A Lead agent can delegate tasks to other agents and collect their answers by itself.
  • A Frontend agent can relay its finished work to a Reviewer automatically.
  • An agent can drive a terminal you can see (npm run dev, tests, builds) instead of running hidden commands.

Orchestra-Board

Orchestra-Board What's new in 0.1.3

Orchestra-Board
Tasks: prompt sequences
Save ordered steps for Claude Code and Codex. Orchestra sends the next prompt when the previous agent finishes, can attach its answer and wait for your approval.
Orchestra-Board
Team templates
Start a board from Developer + reviewer, Lead + two workers or Developer + terminal, or save your own board as a template.
Orchestra-Board
Blockers inbox and permission notch
Every waiting permission, refused exchange or stopped terminal in one place. Accept or refuse a simple permission request without opening the tile.

Boards

  • Formations: select tiles with a right-button rectangle and lay them out as a grid, rows, columns or a line, with a live preview.
  • Groups: name a set of tiles, move them together, and keep them in team templates.
  • Undo / redo (Ctrl+Z / Ctrl+Y) for positions and groups.
  • Find a tile on every board (Ctrl+Shift+F) and enlarge a terminal over the whole map (Ctrl+Shift+M).
  • Board backups: up to 10 previous workspaces, and a recovery screen if workspace.json can't be read.

Links and agents

  • Review before sending on Relay links: edit, send or discard the prepared message. Queued messages can be cancelled until they are delivered.
  • Exact session resume for each Claude Code and Codex tile, even when two tiles share a folder.
  • History tab in Tasks: every message sent through a link, with its reply and the files changed since the task started.
  • Diagnostics in Settings: where each agent's command was found, its version and its Orchestra hooks.
  • A new first-launch setup: language, theme, terminal font, grid, glow and dock agents, then the guided tour.

Full history: releases

Orchestra-Board

Orchestra-Board Demos

Delegation
A lead Claude asks a Claude and a Codex for an idea, waits for both answers and picks one.

A lead agent delegating to two agents and comparing their answers

Drop an agent
Drag it from the dock: it starts in the active folder.

Dragging an agent from the dock onto the map
Link two agents
Link tool, first tile, second tile, then pick the type.

Drawing a link between two tiles
Relay
When one agent finishes, its answer travels down the link.

An answer relayed from one agent to another
A terminal the agent drives
It runs the command where you see it, reads the output and can stop it.

An agent running a command in a linked terminal tile
Give a role
A lasting instruction, given again at every session start.

Editing the role of an agent
Switch branch
Drop the Branch square on a tile: the agent moves to its own worktree.

Moving an agent to another Git branch

Orchestra-Board

Orchestra-Board Features

Orchestra-Board Infinite map
Pan, zoom, minimap, several boards in tabs. Agents keep running in the background.
Orchestra-Board Real terminals
xterm.js + node-pty, started in the folder you picked in the explorer.
Orchestra-Board Links between agents
Relay, Delegation, Terminal and Note links, with turn limits against endless loops.
Orchestra-Board Tasks
Prompt sequences across agents, plus the history of every exchange.
Orchestra-Board Team templates
Ready-made teams, or your board saved for next time.
Orchestra-Board Roles
“You are the reviewer, you never edit files…”, kept across sessions.
Orchestra-Board Exchange log
Every message, reply, command and refusal, with filters and JSON export.
Orchestra-Board Changes
Colored diff of the worktree, or since a task started. Open in VS Code.
Orchestra-Board Git branches
Move an agent to another branch, in its own git worktree.
Orchestra-Board Blockers inbox
Waiting permissions, refusals and stopped terminals across boards.
Orchestra-Board Status & notifications
Working, waiting or done, with a glow, a sound and a system notification.
Orchestra-Board Themes
Standard, Light, ChatGPT, Gemini, VS Code, GitHub, Dracula, Nord, your accent color. English and French.

Orchestra-Board

Orchestra-Board Download

Windows 10 / 11
64-bit installer

Download for Windows

✓  Run Orchestra-Setup-<version>.exe
✓  Choose the folder, desktop and Start menu shortcuts
✓  Built-in update check and installer

macOS
Apple Silicon (arm64) and Intel (x64)

Download for macOS

✓  Open the .dmg and drag Orchestra to Applications
✓  First launch: right-click Orchestra, then Open
✓  Built-in update check

[!IMPORTANT] You need the agent CLIs you want to use, installed and logged in: claude and/or codex must work in a normal terminal.

[!NOTE] The app isn't code-signed yet. On Windows, SmartScreen may say “Windows protected your PC”: click More info → Run anyway. On macOS, use right-click → Open the first time.

Orchestra-Board

Orchestra-Board Tutorial

First launch

Orchestra asks a few quick choices (language, theme, terminal font, grid, glow and the agents shown in the dock), then offers a one-minute guided tour on your own board. Skip goes straight to the tour. Both can be replayed from Settings › General.

First-launch setup: choosing the agents shown in the dock   The guided tour pointing at the agent dock

1. Drop your agents

  1. In the file explorer on the right, click the folder you want to work in: it becomes the active folder.
  2. Drag an agent from the dock on the left onto the map. It starts in a real terminal, in the active folder.
  3. Drop a second one. Each tile can be moved, resized (click its title bar first) and renamed (double-click its name).

Pick the Link tool (L), click the first tile, then the second. With the Select tool (V), click the label in the middle of the link to choose how they talk:

Relay, Delegation and Terminal links

LinkWhat happensGood for
RelayWhen A finishes, its last reply is pasted into B with your instruction ({response} is replaced by the reply).Dev → reviewer, writer → translator
DelegationA sends a task with a unique ID. Requests to the same agent are queued in order; each reply goes back to its caller.A lead that splits work between agents
TerminalA runs commands in a Terminal tile you can watch, after asking your permission.Dev servers, tests, builds
NoteA reads and updates a linked sticky note (list_notes, read_note, write_note).Shared plans, checklists, findings

Relay and Delegation links can be reversed or made two-way, and have a turn limit (3 by default).

The link panel: Relay or Delegation, instruction, turn limit

Review before sending and queued messages

Tick Review before sending on a Relay link to stay in control: when the source finishes, the message is prepared but not sent. Edit it, send it or discard it from the link panel or the Log. When the link label is visible, it expands to show a short preview and Send / Discard buttons; with several drafts, it shows the oldest first and how many remain.

Queued messages (Relay or Delegation, waiting for a busy target) can be cancelled until they are pasted; a cancelled delegation tells its caller instead of leaving it waiting. A message already delivered cannot be recalled.

3. Give a role

Hover the small tab above a Claude Code or Codex tile and click the mask. The role is given to the agent at the start of each session (and again after /clear). The editor also shows the text last injected into the current session. A role is an instruction, not a restriction on the agent's tools.

Editing the role of an agent

4. Share a note

Drop a sticky note and link an agent to it. Ask the agent to read or update it; you see the changes on the map and can edit it yourself. Lines such as - [ ] To do, - [~] In progress and - [x] Done show status icons. A write replaces the whole note, so agents should read it first.

5. Follow the exchanges

Open the Log on the right edge of the map (Ctrl+Shift+J): relayed messages, delegated tasks and their replies, terminal commands and their output, and refusals in red. Each message shows its state (to review, waiting, sent, reply received, cancelled, refused). Filters narrow by board, tile and type; click a task ID (#1a2b3c4d) to follow one task. Export log saves the filtered list as JSON. The log stays in memory only.

The exchange log next to the board

6. Answer permissions

When an agent waits for you, a notch slides out of the inbox icon in the top bar. For a simple yes/no permission, Accept or Refuse right there; for a question or a plan, it takes you to the terminal. The Blockers inbox also lists refused exchanges, turn limits and stopped terminals across boards.

7. Review the changes

When a tile works in a Git repository, a tab above it opens the Changes window: every changed file in its worktree with a colored diff, and Open in VS Code. Other tiles in the same worktree are listed, since changes in a shared folder can't be attributed to one agent. Orchestra only reads Git here.

The changes window with a diff

8. Resume and recover

Claude Code and Codex resume the exact session saved for each tile. If a saved session is missing, Orchestra asks you to start a new conversation instead of resuming another tile's. Settings › General › Board backups keeps up to 10 previous workspaces; if workspace.json is unreadable at startup, choose a backup or a new board.

Orchestra-Board

Orchestra-Board Recipes

A lead and two workers. Put a Claude Code Lead above a Codex and a Claude Code, linked with Delegation. Ask the lead: “Ask each of your agents for a short poem and tell me which one is best.” It writes to both, waits for their replies and answers you. (Also available as a team template.)

Dev + reviewer. Link a Frontend agent to a Reviewer with a Relay and the instruction “Review this change and list any bug: {response}”. Give the reviewer the role “You never edit files.” Every time the frontend agent finishes, the reviewer checks its work.

An agent that runs your dev server. Link an agent to a Terminal tile, then ask: “Start the dev server in the linked terminal and tell me when it's ready.” You see the command run; the agent reads the output and can stop it with Ctrl+C.

A prepared sequence. Open Tasks, create a task with a step for your developer and a step for your reviewer with Attach the previous response, then click Run. See the sequence guide.

Team templates: the Lead + two workers recipe   Tasks: a prompt sequence

More: Tasks, History, Formations, groups and team templates in detail

Tasks › Sequences. A task is a saved list of prompts. Orchestra waits for each response before sending the next one, to the same agent or another. Start it on Run or when a given agent finishes; a step can attach the previous response or wait for your approval. Pause, resume or stop at any time; the current agent always finishes its answer. Sequences are stored in task-sequences.json (50 tasks, 50 steps each).

Tasks › History. Every message sent between agents through a link, with its reply and the files changed since the start. Read the reply, then mark the result as done or failed. You can also Track a task you give an agent yourself. Files changed since the start compares the worktree with a snapshot taken when the work began, without any commit or stash. Snapshots stay local and are bounded (20 references, 500 files each, 200 KB per file).

Formations and groups. Select several tiles with a right-button rectangle, then open Formation: adaptive grid, 3 or 4 per row, 2 columns, horizontal line or centered column. Hover a formation to preview it; Ctrl+Z undoes it. Create a named group from the selection: drag its name to move its members, double-click to rename, or ungroup without closing tiles.

Team templates. Choose the project folder and replace any unavailable agent with an installed one, then create a new board. Roles and links are registered before the agents start. Each instance gets fresh tiles and sessions. Saved templates live in team-templates.json.

Top bar. Tasks, Search, Teams, Inbox and Settings are compact icons. To show their names on hover, turn on Settings › Appearance › Expand toolbar buttons on hover.

Orchestra-Board

Orchestra-Board Keyboard shortcuts

Everywhere (even in a terminal)

Ctrl+Tab / Ctrl+Shift+TabNext / previous board
Ctrl+1…9Go to board
Ctrl+Shift+TNew board
Ctrl+,Settings
Ctrl+Shift+E / A / U / JFiles / active agents / usage / log
Ctrl+Shift+FFind a tile on every board
Ctrl+Shift+MEnlarge or restore the selected terminal

On the map

V P N T LSelect, pen, sticky note, text, link
FFit everything in view
DelDelete the selection (with confirmation)
F2Rename the selected tile
Ctrl+Z / Ctrl+YUndo / redo

In a terminal, Ctrl+C copies when text is selected (otherwise it interrupts) and Ctrl+V pastes. The full list is in Settings › Shortcuts.

Theme picker: Standard, Light, ChatGPT, Gemini, VS Code, GitHub, Dracula and Nord

Orchestra-Board

Orchestra-Board Privacy and safety

🔒 Local orchestration
Agents talk to Orchestra through a small server bound to 127.0.0.1, protected by a secret token that changes at every launch. Update checks contact GitHub (can be turned off in Settings › General). Git fetches and the agent CLIs use their own connections.
✋ Your permissions stay yours
Orchestra never approves a permission on its own. Its own tools are pre-approved, except run_in_terminal, which always asks. The notch only sends your Accept or Refuse.
🌿 Git, read-mostly
Only git fetch, git worktree add (when you pick a branch) and read-only commands. Orchestra never commits or pushes.
📁 What it writes outside its folder
~/.claude.json: marks a folder as trusted before launching Claude Code (can be turned off). ~/.codex/orchestra.config.toml and Orchestra's entries in ~/.codex/hooks.json, inactive outside Orchestra.

App data (settings, boards, tasks, templates) lives in %APPDATA%\Orchestra (macOS: ~/Library/Application Support/Orchestra). The exchange log and the blockers inbox stay in memory only.

Orchestra-Board

Orchestra-Board FAQ

Codex asks me to approve “5 hooks”

That's Orchestra's status hooks (working / done). Choose Trust all and continue once; Codex remembers it.

Which agents can use links?

Claude Code and Codex can relay, delegate, drive a terminal, use linked notes and run task sequences. Other CLIs (Aider, Gemini CLI, your own…) work in a tile and can receive relayed messages; their integration does not include Orchestra hooks or orchestration tools.

Can I add another CLI?

Yes: Settings › Agents. Pick a known agent (Google Antigravity, Aider, Qwen Code, OpenCode, GitHub Copilot CLI, Cursor CLI, Goose, Amp, Kimi CLI…) or add your own command, logo and color. Test checks that the command exists, and Settings › Diagnostics shows where it was found.

An agent seems stuck

Look at the inbox icon in the top bar: the agent may be waiting for a permission or an answer. The Blockers inbox also shows turn limits reached and refused exchanges. Settings › Diagnostics tells you whether the agent has Orchestra hooks and which hook it sent last.

Linux?

Orchestra runs on Windows and macOS (Apple Silicon and Intel), with an installer for each in every release. Linux is not tested or packaged yet.

Orchestra-Board

Orchestra-Board Build from source

Use Node.js 22.12+. Install the locked dependencies with npm ci.

npm ci           # node-pty ships prebuilt binaries: no Visual Studio or Python needed
npm run dev      # Vite + Electron with hot reload
npm test         # session, recovery, queue, review, undo and diagnostics tests
npm run dist     # Windows installer in release/Orchestra-Setup-<version>.exe

The macOS version lives on the macbook branch: npm run dist:mac there builds the .dmg files (on a Mac), and every push to that branch builds them on GitHub Actions.

Windows launcher and build notes

launcher.exe at the root rebuilds the interface and prepares a local Orchestra.exe with Orchestra's icon and product metadata (npm run build:launcher recompiles the launcher; npm run build:runtime prepares the runtime). The original Electron executable stays unchanged. The branded copy adds about 250 MB under ignored node_modules and is reused until Electron, the icon or the version changes. Close the app before applying a runtime update.

If Windows' ransomware protection (Controlled folder access) is on and the project is in Documents, it may block the installer build: allow makensis.exe or build elsewhere.

Project structure
electron/            Node side: windows, terminals, files, local server, MCP
  main.cjs           window, IPC routes, notifications
  preload.cjs        the only bridge to the UI (window.pty, fs, settings, workspace, git…)
  ptyManager.cjs     one real PTY per tile
  hookServer.cjs     local server (127.0.0.1 + token) for agent hooks and MCP tools
  mcpServer.cjs      the "orchestra" MCP server started by each agent (stdio)
  linkRelay.cjs      Relay links
  delegation.cjs     Delegation links (list_agents, send_to_agent, wait_for_replies)
  terminalLink.cjs   Terminal links (run_in_terminal, read_terminal, interrupt_terminal)
  activityLog.cjs    exchange log (memory only)
  agentStatus.cjs    tile status and permission requests
  claudeHooks.cjs    per-tile Claude Code settings and MCP config
  codexProfile.cjs   Codex profile and hooks
  git.cjs            branches, worktrees, read-only changes and diffs
src/                 React interface (map, tiles, panels, settings, tutorial)
docs/images/         README images, demos and artwork

The path of a keystroke: xterm.js → window.pty.write → IPC → node-pty → the CLI, and back through pty:data:<id>.

Orchestra-Board

Orchestra-Board Feedback & support

Found a bug or have an idea?
Open an issue (a short form for bugs, one for feature requests) or share how you use Orchestra in Discussions.
For anything else: orchestraboardai [at] gmail [dot] com

If Orchestra saves you time, a ⭐ on the repository helps other people find it.

Orchestra-Board License

MIT © 2026 Dimitri (@Adoraay)

// faq

What is Orchestra-Board?

🎼 Be the maestro of your AI orchestra. A desktop canvas where you drop Claude Code, Codex and other CLI agents, each in a real terminal, and link them: relay work, delegate tasks, let an agent drive a terminal. Roles, exchange log, Git worktrees. Windows, local-only.. It is open-source on GitHub.

Is Orchestra-Board free to use?

Orchestra-Board is open-source under the MIT license, so it is free to use.

What category does Orchestra-Board belong to?

Orchestra-Board is listed under devtools in the Claudeers registry of Claude-compatible tools.

9 views
★ 10 stars
unclaimed
updated 17 days ago

// embed badge

Orchestra-Board on Claudeers
[![Claudeers](https://claudeers.com/api/badge/orchestra-board.svg)](https://claudeers.com/orchestra-board)

// retro hit counter

Orchestra-Board hit counter
[![Hits](https://claudeers.com/api/counter/orchestra-board.svg)](https://claudeers.com/orchestra-board)

// reviews

// guestbook

0/500

// related in Developer Tools

🔓

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Curs…

// devtoolsaffaan-m/⟨JavaScript⟩★ 297,269◷ MIT[ claude ]
🔓

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

// devtoolsDietrichGebert/⟨JavaScript⟩★ 187,728◷ MIT[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// devtoolssafishamsi/⟨Python⟩★ 147,800◷ MIT[ claude ]
🔓

Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA

// devtoolsgarrytan/⟨TypeScript⟩★ 140,465◷ MIT[ claude ]
→ see how Orchestra-Board connects across the ecosystem