Five Claude Code sessions, five panes. One waits for a permission, one finished an hour ago with a question, two are working. orch watches all of them, tells you what matters, queues every question for you and starts new workers with tests and a two-model review. From your desk or your phone.
› what's going on ● One needs you: api is blocked on a permission to run migrations (D-12). fix-login passed its gates, review is running. pr118 is a Claude + Codex pair, both still working. 6 idle. › accept D-12 ● Told api: yes, go ahead.
orch is a Claude Code session with a few skills and a small TypeScript toolkit. A hook in every session writes one line per event to a local feed; orch reads it and acts within rules you can edit.
Every Claude and Codex session on your machine, who is working, blocked, idle or asking you something.
Anything that needs you becomes a decision with a recommendation and one phone notification. Your answer gets typed into the right session.
New work goes to a worker in its own git worktree. orch runs your tests when it's done and commits on the branch only if they pass.
Claude and Codex review the same change independently. What both find counts; the rest gets checked against the code first.
No commands to learn. These all work as typed.
what's going onBlocked first, then questions waiting for you, then who is working. Idle as a count.
run my-app fix-login: Safari login button does nothingA worker on its own branch. Tests, then a commit, then a decision if it should be pushed.
… with bothSame task to Claude and Codex. orch picks the winner by tests and review.
look at the PRs of my-appWorkers for review comments on your PRs, drafted reviews for your colleagues' PRs.
continue my-appPlans the next steps toward your goal and dispatches up to your worker cap.
reject D-7, keep the old APIYour words go into that session verbatim.
Type /deck and a live pane docks next to the chat: every session as a map, a dot running along the line whenever a message moves, each worker's stage, the bus of prompts and replies, open decisions. It's a Claude Code mod, so it lives right in the terminal.
fix-login ■■■■□□ review 12m fix Safari login · "gates green, 3 files" pr118-cl ■■□□□□ work 4m address review on #118 pr118-cx ■■□□□□ work 4m address review on #118 (Codex) brief work gates review judge push
These always come back to you as a decision. Workers never commit; orch commits on the worker's branch only after your tests pass. The rules are a plain Markdown file you can read and change.
No dependencies to install. Setup checks your tools, creates your local files and adds one hook to Claude Code (and Codex). It backs up what it changes.
Clone and set up
git clone https://github.com/cf-lucas-moskau/orch ~/orch cd ~/orch && npm run setup
Put your name in local.md and your repos with their test commands in projects.md.
In a herdr workspace called orch, start it and say hi.
npm start
Needs macOS, Node 22.6+, Claude Code, herdr and jq. Optional: Codex for two-model work, gh for PRs.