lead-session-orchestrator
Many sessions, one lead, and whatever only you can decide waits in one inbox.
For developers · Version 0.x, for macOS and GitLab. MIT. · session-orchestrator.com/lead (opens another website)
What you do with it
You have several coding sessions working on your projects at once, and sooner or later each one has a question for you. Instead of going through every window, you look at one tab with the Inbox. Each question waits there with its answers and a recommendation, say “Continue or wait?” You press one key when it suits you, and the count of open questions goes down.
- Who it's for
- For people who run several coding sessions at once and lose track of which one is waiting for them.
- Where it stands
- An early version for macOS and GitLab, and the Inbox is in English. The lead session keeps the others in order, but it never gives the go-ahead itself.
Step by step
Install the tool
You install the tool with one command in the terminal. You need Node.js and Claude Code for that.
Set it up
A second command registers the Inbox with Claude Code and checks that your computer has everything it needs.
Inbox in a new tab
You open a new Claude Code tab and type /inbox. From then on, your sessions' questions land there.
Answer with one key
When a session raises a question for you, you press the key for the answer you want and confirm. The count goes down and the session carries on.
How it works
- The language model
- runs the lead session: it reads the situation, orders the merges and bundles your decisions.
- The code
- sets the limits: only ever one lead, one rule file per repository, and whatever it cannot measure, it leaves alone.
Why it exists
With three or four sessions running at once, I became the bottleneck: each one asks, each one wants to merge. In the morning I want to see what ran and what only I can decide.
The proof
15 days from the first line to npm.