Keep your laptop fast while your agents build
Headroom runs your coding agents' builds and tests on other computers or cloud sandboxes, so a few agents at once can't max out your laptop.
Every agent you start builds on this Mac.
Builds run where there's room
Your agents send their builds and tests to Headroom, and it runs them on another computer or sandbox with room. Uncommitted changes go too, with no commit or push. Each branch keeps its own checkout there, so node_modules and target carry over to the next run. When every machine is full, jobs wait in line and each agent is told its place.
$ headroom run --os macos -- xcodebuild test headroom: syncing 4c1e09d27a plus uncommitted changes to mac-mini headroom: job 7f3a20c9 running on mac-mini ** TEST SUCCEEDED **
Connect each agent with one switch.
- Claude Code
- Codex
- OpenCode
- Cursor
- Pi
A row for each computer and account
This Mac and each computer get a row, and each cloud sandbox account gets one row for all its sandboxes. Beside the meter is what's running or waiting, in amber when something needs you.
Add a computer or a sandbox account
Type a computer's name or address, or paste an exe.dev, E2B or Daytona API key, into one field. Nearby computers, Tailscale devices and SSH hosts are listed below it.
exe.dev jobs max out the CPU 84% of the time
8 cores and 32 GB would save about 7 agent hours a week, at a higher hourly price.
Each row opens to its jobs
Hover a computer's row for its CPU and memory. Click it for its load and running jobs, each with a × to cancel. An account's row opens its sandboxes.
Bigger sandboxes when builds need them
When an account's jobs spend most of their time at full CPU, Headroom says how many agent hours a week the next size up would save. One click resizes it.
Safe to hand to your agents
Your .env files, keys and credentials never leave your laptop, even ones you've committed. Agents can run jobs but can't add machines, change settings or raise a limit.
Nothing is installed on your computers. Headroom adds one line to ~/.ssh/authorized_keys, and only when you add a computer with a password.
- .env* (not .env.example)
- .dev.vars
- private keys
- certificates
- .npmrc
- .netrc
- .git-credentials
- .ssh/
- .aws/
- .gnupg/
- .kube/
- .docker/
- .config/gh/