Build four features at once.
Lose track of none of them.

• One queue, every agent. Nothing waits in a tab you forgot to check.
• The one stuck longest comes first — unblocking it frees the most work.
• It comes to you. A prompt rises above whatever you're doing — and stays quiet about the chat you're already reading.
• Not now? Put it off in one click. The nagging stops; the work doesn't disappear.

• Run out of one, carry on with the other. Your next conversation is one click from a different subscription — same repo, same branch, same queue.
• Watch both allowances. Every conversation shows what it has left — of the plan it is actually spending, not the other one.
• See which model is answering — and change it without leaving the conversation. No more finding out an hour later that it was the cheap one.
• Every tab says whose it is, so you always know who you're talking to.

• Every repo, one branch name. Each gets its own checkout of the feature, named the same, so the pull requests on either side find each other.
• Review and ship each repo on its own. Pick the repo and the diff, the commit, the push and the terminal follow — nothing lands in the wrong one.
• Each repo's own rules. The agent reads the instructions every repo keeps for it before it starts, so both sides get their conventions followed.
• Bring another repo in later. Add one to an agent you already have, and every feature in flight gets it — nothing to start over.

• Read it, stage it, or throw it away — file by file, right beside the diff, or open it at that line in whichever editor you use.
• Every change in its surroundings — the whole file, not a keyhole around each edit, so you can tell whether it belongs. A strip down the edge shows where every change is and takes you there in a click; one key steps to the next, and search finds anything in the file.
• The commit message is already written, drawn from the diff and matching how your repo words things. Edit it or send it.
• Push and open the PR from the same panel, with the state read straight from git rather than guessed.
• Answer the review where you work. Every open comment on your pull request, with a plain-English read of whether it holds and the ways to resolve it. Reply, resolve, or hand it to a chat that proposes a fix and waits for your pick.
• Shipped one? Point that branch at the next thing and keep going.

Anywhere

Keep shipping from your phone

Scan a code once and orc opens in your browser. Read what an agent did, answer the question holding it up, check the diff, push the branch — from a train, or the queue at lunch.

• Only devices you pair can reach it, and any of them can be revoked in one tap.
• It tells you when you're needed — a question that stops an agent, a turn that finished, one that failed — with orc closed and your phone in your pocket.
• Your computer stays awake while orc runs, so there's always something there to answer you.