Many terminals. One project.
Each Claude Code and Codex job runs in its own terminal, and together they work on one project. Rillby keeps them going without you typing "continue", and puts their questions for you in a single queue.
macOS 14+ · Apple Silicon · requires Claude Code, Codex or both, installed and signed in
Waiting for you
01Running · 4
Waiting for you
01Example data
Five jobs, five terminals. When an agent asks something, the question goes to the queue, and your answer goes back to its terminal.
01The problem
Eight terminals open. Which one is waiting for you?
An agent asks a question, and it scrolls away under the output. Later you go through the windows one by one to find it. If the context was compacted in the meantime, you also have to work out what the question was about.
Eight terminals. One has been waiting for you since 14:20.
02How it works
Start it. It keeps going. It asks when it needs you.
Start.
Pick a project, say what needs doing, and choose Claude Code or Codex. Rillby starts the one you have installed, in a terminal, with the sign-in you already use.
It keeps going.
When the agent ends a turn and the work isn't done, Rillby starts the next one. It goes on until the work is done or there's a real question for you. You don't type "continue".
Answer in one place.
Next to the question you see the output it came up in. You answer, and the agent carries on from the same spot.
03The queue
One queue for everything that needs you.
Questions, failures and finished work waiting for review, from every project and both agents, in one list, most urgent at the top. Each card shows which job it came from and what it needs from you. Press Space to see the output around a question. The count is in the menu bar too.
Example data
Waiting for you 3
3 orders have no status. Set them to "pending" or "cancelled"?
The login test needs a user. Take the seed user from fixtures, or create a new one?
Two hooks compute the same total. Merge them now, or keep both until the next version?
Today: what needs you, what's running, what's done.
04The terminal
A real terminal under every job.
Not a chat dressed up as a terminal. Each job runs in a real terminal with the agent's own interface: colours, scrollback, keys. Open it and type to the agent yourself; while you're in, Rillby sends it nothing on its own. Need two at once? Put them side by side.
Example data
Waiting for you 1
Running 3
Done 1
The work happens in the terminal. Rillby shows which jobs are running and which need you.
05Review
See the result before you accept it.
A job doesn't just say "done". You get a card: what was done, screenshots or a video of the result, the browser console and network requests from the check, and the diff, folded until you want it. Accept it, or send it back with a comment, and the comment goes straight to the agent.
Example data
You decide when the work is done.
06Survives restarts
Updates and restarts don't cut your work off.
Close the window, update Rillby, restart its service: your jobs keep running, terminals and all. An update installs when your work reaches a safe moment. A Mac reboot is another matter: it stops running agents.
before — Window closed · 5 jobs running
after — Window reopened · the same 5 still running
Close it, update it, come back. Your jobs are still running.
07Your data
Rillby runs on your Mac. Here's what leaves it, item by item.
Rillby and your jobs run on your Mac. Rillby doesn't send your code or project keys to its own server unless you choose to. This is what does leave the machine:
Rillby runs the Claude Code and Codex you already have installed, with your own sign-in.
08Beta
Sign up for the beta.
We invite people in small groups, once a week. Leave your email; three optional questions help us choose who to invite first.
You are on the list. We will write when your group is invited.