Claude Code and Codex in parallel, without the context switching.
Private beta · Apple Silicon · sign in with GitHub
One window from typing a task to shipping it. No terminals to watch, no tabs to juggle: ten agents cost you no more attention than one.
Ten agents usually means ten terminals to check, and every check is a context switch. Control Room does the checking. Your attention stays on one thread, until another one needs you.
Type what you want. Control Room creates the git worktree, names the branch after the task and starts the agent in it.

Threads sort themselves into Needs attention, Working, Snoozed, Done and Archived. A question from an agent is a card you answer in a click.
The whole branch as one diff. Drop comments on lines and they go back to the agent as its next instruction.
The header always shows the single thing to do next. Press it and the agent does the work: write the pull request, fix the failing check, answer the review, resolve the conflict. Or start with Start & merge and skip the pressing.
While it works, an agent notices what does not belong in its task: a bug next door, a test that already failed, a follow-up. It proposes a new thread, with the brief already written. Start it now, or keep it as a ticket.

Agents show a new screen as a live mockup before they build it. Pin comments on its parts and send them back in one go. Explanations come with a diagram, drawn in the thread.
With several Claude accounts, Auto starts each thread on the one with the most left to spend before its reset, and moves a thread that runs out to the next. Each account shows its 5-hour and weekly gauge. Provider, model and effort stay yours to choose, per thread.

A rendered chat with tool cards and diffs, or the agent's own terminal interface. Your choice, per thread.
⌘T opens another agent on the same branch, each with its own model and status.

⌘K searches every thread by name, branch, ticket or pull request, across all your repositories.
Setup, run and archive scripts, ports and environment for each worktree. Your own prompt buttons in the header.
Start from an issue, see issues delegated to agents in the sidebar, and let finished work close its ticket.
/ completes the agent's commands and your project's skills. Your MCP servers come along unchanged.
A plugin is a folder with a manifest and one JavaScript file. It reacts to what threads do and gives every agent standing instructions. Design preview, Diagrams and Keep awake ship as plugins; yours stay off until you enable them in Settings.
module.exports = (api) => {
api.on('thread-state', () =>
console.log(api.workingAgents()))
api.prompt('session',
'Always answer in French.')
}Mermaid diagrams in your Markdown files are drawn in the diff, like the ones in a thread. Agents add one to the pull request and the ticket too.
Archive, snooze or close a thread. Control Room warns about an open pull request or unpushed commits first.
An agent can list the other threads, read one, start one and message one. You approve each start and each message, unless you chose bypass.
Light, dark or system theme, and settings that sync between your computers. Connections never leave the machine.
Control Room drives the claude and codex you already have. Your code stays in git worktrees on your machine.
From GitHub or a local folder. Control Room keeps its worktrees out of your way, in its own folder.
Each one gets a worktree, a branch and an agent. They work at the same time without touching each other.
Work comes back to one list, already sorted. Handle what is waiting on you; the rest keeps running.
Control Room is where you direct agents live. The factory is where work runs without you: standing jobs, versioned with your repository, that audit, fix and open pull requests overnight. Connect the two and everything that waits on you lands in the same list.
Claude Code and Codex, with the accounts and subscriptions you already use. You choose the model and the effort for each thread, and can change the model while it runs.
Nowhere new. Agents work in git worktrees on your Mac and talk to their own provider, as they do in your terminal. A cloud thread runs in the agent provider's cloud, when you choose it.
No. Control Room works alone with a git repository. Linear, GitHub issues and the factory are connections you add in Settings when you want them.
A Mac with Apple Silicon, git, and the claude or codex command line signed in. The GitHub CLI gh for pull requests.
Control Room is in private beta. Sign in with GitHub; approved accounts download the installer from Settings, and the app updates itself from there.
Give every task its own agent, and keep your attention for the decisions.