Pro
Our pick for agent work$75a month
5 agents plus the Docker services they test against
- vCPU
- 4
- RAM
- 8 GB
- disk
- 100 GB
- Internet
- 100 Mbit
- Terminals at once
- 5
Turn the backlog into branches while you build the next feature
Script Codex or Claude Code over a list of issues on compute that never sleeps. Each fix gets a test and a branch of its own, and your laptop stays yours. Pro is $75 a month.
From $39 a month · Docker and sudo included · Cancel from the dashboard any time
Forty small bugs, and each one costs a context switch
Every one-line fix means a branch, a test, a push and twenty minutes of your attention. Forty of them is a lost week.
Hosted CI runners are built for tests. An agent needs an hour, a database, warm caches and credentials to finish the job.
One backlog run
- 10:00
Write the loop once
A shell loop hands each issue to codex exec or claude -p with the same brief: fix it, add a test, push a branch.
- 10:02
Leave it in a tab
The loop runs inside a tmux session. Close the tab; it works through the list.
- 11:30
The stack stays up
Postgres and MinIO run in Docker on your Compute for every issue, so each fix is tested against the same services.
- 16:00
Review finished branches
Open the pushed branches as pull requests and review each diff like a colleague's.
The agent clears the backlog
Your backlog, as branches
Each issue ends as a branch with a test. You review diffs instead of writing them.
Headless agents with a home
codex exec and claude -p run without a UI. Checkouts and each agent's history stay in the project between runs.
The tenth run starts warm
Containers, dependencies and build caches stay in the terminal that runs the loop, so the tenth issue starts as fast as the second.
Every night, or on every new issue
The loop is a shell script in the project. Edit it in the terminal and start it. Add cron for a nightly run, or a webhook listener to start runs from events.
The size for this job
Pro · $75
Pro's 4 vCPU keep the test suite and containers busy while the next issue is already running.
- Compute
- pr-mill
- Projects
- /work/app
- Plan
- Pro · 4 vCPU · 8 GB · 100 GB · $75/mo
- Agent
- Codex
- Tabs
- 3
- Services
- postgres:18 · minio
- Runs
- Around the clock, lid closed
Questions about this
Can I start runs from a webhook or a cron job?
Yes. Each terminal is Linux with sudo, cron and systemd, running as long as the terminal does. Install a cron job or your own runner there, or serve a webhook listener on a public port, and start agents from it.
Where do the agent's git credentials live?
In the project's own home folder on your Compute, which no other project's terminal can see. Give the agent a deploy key or a fine-grained token scoped to the repos it works on.
What if a run leaves a mess?
Each terminal is its own Linux system, so one bad run stays in its terminal. End it and the next one starts clean; git restores the project folder.
What this job uses
More jobs people run
Turn the backlog into branches while you build the next feature
Pick a size, hand the agent the job and close the tab. Come back to finished work.
Get my ComputeYour first overnight run works, or your money back · Cancel from the dashboard; it runs to the end of the paid month