Run a team of AI agents with Roundhouse
Roundhouse gives a team of AI agents a mission, a lead and a shared ticket board, and asks you before it plans, spends past its budgets or opens a pull request.
Roundhouse lets a team of AI agents work through a shared ticket board for you. A team has a mission, one lead who reports to you, and helpers who report to the lead. You approve the plan, the budgets keep the spending in check, and nothing reaches GitHub until you click.
Roundhouse is in Preview: it is still in development and off until you turn it on.
Then open it from the sidebar under AI Tools > Roundhouse.
Start a team#
Click New team.
Pick the kind of team (Software team, Research team, Content team or Just a lead), give it a name and say in a sentence or two what it should do.
Pick where it works: one of your projects (each agent works in its own copy and never pushes) or its own workspace.
Check the budgets and the model, then click Create team. Nothing runs yet.
On Home, click Start the team. The card shows what the run sets aside, what the team has left this month and which account pays. Confirm.
The lead reads the mission and writes a plan: goals, first tickets and any extra agents. It can read the project but cannot change anything while it plans.
When The plan is ready shows, click Open the plan and approve it in the Inbox tab, or ask for changes.
Turn on Automatic work in the team's Settings tab when you want the agents to pick up their tickets by themselves.
Approving the plan creates its goals and tickets once. Until you turn on Automatic work, agents only run when you press Run now.
Keep the spending in check#
Budgets. The team and each agent have a monthly budget (by default $200 for the team and $100 for each agent). At 80% you get a note; at 100% that agent or team is paused until you click Raise budget and resume or a new month starts.
Today's cap. One daily cap covers every team. Once it is reached, nothing new starts until tomorrow. Change it on the Spend tab with Change daily cap: a lower cap applies at once, and a higher one asks you to confirm the new amount.
Pause everything. The switch at the top of Roundhouse stops every new run on every team at once. A run already going finishes the step it is on and stops.
Who pays. Agents use your Claude subscription, so runs count against its usage limits. An agent is billed to a pay-per-use key only when you pick that key for it on the Team tab. With no Claude account on the computer, nothing starts and Roundhouse says so.
Answer questions and review work in the Inbox#
The Inbox tab lists what waits on you: questions from agents, approvals (a plan, a new agent, a bigger budget), finished work to review and tools an agent wants to use. Answer, Approve, Request changes with a note, or Reject. Your decision wakes the agent through the same money checks.
Open a pull request#
For a team that works in a GitHub project, approved work shows Open a pull request. Before anything is pushed, the confirm names the GitHub account it will use: the account that owns the repository, or else the one signed-in account that can push to it. If none or more than one qualifies, Roundhouse tells you instead of guessing. It pushes exactly the work you approved and opens a draft. Not needed hides the item; nothing is pushed.
Start from GitHub's latest#
A team that works in a GitHub project remembers the commit its agents start from. To move it to the newest commit on GitHub, open the team's Settings tab and click Start from GitHub's latest. You see the newer commits first and move only if you click Start from this commit. Work already started keeps its own starting point.
If your copy of the project does not have GitHub's latest commit yet, Roundhouse asks you to get the latest code the way you usually do, then look again. It never downloads anything for you, and it waits while an agent of the team is working.
Stop or pause a team#
Pause team at the top of Roundhouse stops every agent of the team from starting, on its own or with Run now. Resume team on the banner lets it start again. A team paused for its budget comes back only with Raise budget and resume.
Turn off Automatic work in the team's Settings tab: agents then run only when you press Run now.
Pause one agent from its pane on the Team tab, and Resume it there. My Automations can pause a started team too.
Stop run on a run stops it where it is; what the agent already did stays.
Delete team in Settings removes the team once none of its runs is going.
Main inbox cards. Each waiting request also shows as one card in your main inbox, and deciding it in either place settles both. Turn off Also show these in the main inbox to keep them in Roundhouse.
Project instructions. Agents get the project's CLAUDE.md from the commit the team starts from, never your personal one. When they would get none (no CLAUDE.md, or no record of the code yet), the team's Settings tab and the Start card say so plainly.
One run at a time per agent. Every start, by a click or by itself, passes the same checks: Pause everything, pauses, budgets and today's cap.
Reviews by another agent. A ticket can go to a reviewer agent first; three rounds of changes in a row send it to you.
Shallow copies. If the project holds only part of its git history, Roundhouse refuses to start or open a pull request and says how to get the full history.
Export and import. Export team saves the mission, agents, goals and budgets to a file, never keys, accounts or folders. Import a team shows everything first and makes a new team that is not started.
Clean up. An agent's copy of the project is removed only after its pull request merges, or a week after its ticket is cancelled, and never while it holds unsaved changes.