Run AI coding agents on several computers.
Each start lands where there is room.
You have a box that never sleeps and a laptop or an office PC you actually sit at. Give a project an ordered list of those computers, its machine pool, and every new agent starts on the first one that is online, has the project and still has room.
Each computer also gets a budget: a maximum of live agents, a free memory floor and a stricter cap for the night. Twenty open projects no longer run one machine out of memory.
- 1Always-on box6 / 6 agents
- 2Office PC2 / 6 agents
- 3Laptop0 / 3 agents
The order of the pool decides. The first computer with room gets the agent; a full, asleep or switched-off computer is skipped.
A common setup: a Linux box or a small server runs all day and all night, and a Windows or Mac machine is where you read mail, join calls and review what the agents did. Without a pool, every launch asks the same question, which computer, and you answer it by hand each time. Forget once and the heavy refactor runs on the laptop you are about to close.
The machine pool answers that question once per project. You tick the computers the project may use and put them in order, the always-on box first. From then on, opening an agent, Start on a backlog ticket, the quick agent and triggers set to the pool all go to the first computer of the list that is online, has the project and is under its budget. When that computer is full, asleep or off, the next one takes the agent.
The budget is the other half. Each computer accepts a number of live agents for all projects together, keeps a minimum of free memory, and can have a lower cap at night, in its own local time. It is what keeps a box with many open projects from being killed by the out-of-memory killer at three in the morning.
Set it up in three steps
On the desktop app, or from the AgentsRoom mobile app.
- 1
Build the pool
Open Project settings, Machines. Tick at least two computers of your account and order them, the preferred one first. With fewer than two, the pool stays off and nothing changes.
- 2
Give each computer a budget
Settings, Agent behavior, Budget of this computer. For another computer, open the Machines chip in the status bar and click the gauge at the end of its row. Every field is optional: no value means no limit.
- 3
Work as usual
Agents now start on the first computer of the pool with room. Pick a machine by hand in Run on or Launch on and your choice always wins.
A budget per computer, not per project
It counts every agent console of the computer: all projects, all windows, and the agents started from your phone.
Maximum live agents
How many agent consoles may run at the same time on this computer. Past it, the computer is reported full and the pool skips it.
Keep memory free
No new agent starts while free memory is below the amount you set. Free memory is measured the way each system counts it, on macOS, Windows and Linux.
Night budget
A stricter cap for a time window, in the computer's local time. Useful when nightly triggers should not compete with a backup or a build.
Saved on your account
The budget is stored on your AgentsRoom account and applied by the computer itself, so you can set the budget of the box from the laptop, or from your phone.
What happens when a computer is full
The answer depends on who asked for the agent.
You clicked: you choose
A short dialog offers to start on another computer of your account that has room and has the project, to start here anyway, or to cancel. A start you asked for is never refused outright.
The app started it: it waits
A trigger, an agent spawned by another agent, a ticket started by an agent or a team step does not ask anything. It waits for room and starts by itself once an agent ends or memory frees up.
Another computer asked: a clear refusal
A start sent from another computer is refused with the reason: at its budget, short of free memory, or night budget. The pool then moves on to the next computer.
An agent keeps its conversation
An agent whose conversation lives on this computer keeps starting here while this computer is in the pool and has room. To move it with its conversation, use Continue the conversation on.
Triggers that run once, on the pool
A trigger can target the machine pool instead of a fixed list of computers. Each occurrence then runs once, on the first computer of the pool with room. The preferred computer gets three minutes to take it, then any computer of the pool may.
So a nightly agent no longer depends on the laptop being open: put the always-on box in the pool and it runs the job. When no computer could run it and the trigger does not catch up, the run is recorded as missed and you get a notice on the desktop and on your phone.
The whole project, from the other computer
A project that only lives on the box still opens in full from the laptop.
Files
Browse the project tree and preview files as they are on the other computer. Read only, and very large files are not shown.
Changes
See the Git status and the diff, commit the files you tick and push, all executed on the computer that has the repository.
Backlog
The project's backlog, with Start on and the name of the computer in the detail of a ticket to do.
Terminals
The dev terminals open on the other computer show in the bottom bar and stream live from the machine that runs them.
Your agents can use the pool too
An agent or the assistant can start another agent on a chosen computer, or let the pool decide. Over there, the agent runs on that computer's own account and CLI. Triggers and settings can be set the same way.
agents_spawntriggers_savesettings_setPlacement decides where the agent CLI starts. The CLI itself is resolved on the computer that runs it, so Claude Code, Codex, GitHub Copilot CLI, Antigravity and the other supported CLIs all work the same way.
Good to know
- It needs Remote Fleet: the computers are signed in to the same AgentsRoom account and connected.
- Each computer reports its load every 30 seconds. Two starts in the same instant may both pick a computer that had room for one; its budget then makes the second one wait.
- An agent opened over SSH counts on the computer that opened it.
- A project shared by another account is never part of a pool and never shows its files or changes here.
- Files of another computer are read only. Changes commits and pushes, without discarding or staging part of a file.
FAQ
Can AgentsRoom start my agents on the least loaded computer automatically?
Yes, with a machine pool. In Project settings, Machines, tick the computers the project may use and order them. Each start goes to the first computer of the list that is online, has the project and is under its budget, and moves to the next one when it is full or off. It is an ordered list, not a round robin: the order is how you say which computer you prefer.
How do I stop many open projects from running my server out of memory?
Give that computer a budget: a maximum of live agents and an amount of memory to keep free, counted for all projects together. Past it, the computer accepts no new agent: your own click asks where to start, a trigger waits for room, and the pool sends the agent to the next computer.
Do triggers still run when my laptop is asleep?
Yes, if the trigger targets the machine pool and an always-on computer is in it. Each occurrence runs once, on the first computer of the pool with room. If no computer could run it and the trigger does not catch up, you get a missed run notice.
Can the assistant on my laptop start an agent on my always-on box?
Yes. Ask it in plain words. It can name the computer or let the pool decide, and the agent starts over there with the project's usual settings. The result shows up in the project like any other agent of the fleet.
Can I see the files and Git status of a project that only exists on my other computer?
Yes. Open the project from the sidebar, then Files, Changes or Backlog in its header. Files are read only, Changes can commit and push on that computer, and its dev terminals appear in the bottom bar.
Does it work with Codex, Antigravity and other CLIs, not only Claude Code?
Yes. The pool only chooses the computer. The agent CLI is then started on that computer like any other launch, with that computer's own installation and accounts, whatever the provider.
What changes if I never set a pool or a budget?
Nothing. Without a pool, agents start on the computer you are using, Start on a ticket runs here, and the quick agent defaults to this computer. Without a budget, a computer accepts every agent, as before.
You may also like
Remote Fleet
The link between your computers that the pool builds on: every project and every agent of every machine, in one window.
Continue on Another Computer
Move one agent with its whole conversation to another computer, by hand, when you want it there.
Process Guard
When the memory is already gone: find the runaway processes your agents left behind and end them.
Scheduled Tasks
Agents that start on a schedule, the triggers you can now point at the machine pool.
AgentsRoom MCP
The tools that let your agents start other agents, on this computer or on another one.
Put every computer to work
Install AgentsRoom on each computer, sign in with the same account, and let each project's pool decide where its agents start.
Companion app: monitor your agents on the go
Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.
Push bugs and requests straight to your public backlog.