Cloud coding agents
Hand off the work.
Keep the judgment.
Every Aldo thread is a coding agent with a computer of its own. It writes the code, runs your app, opens the pull request and sees it through checks, review and deploy. When a decision is yours, it asks.
Add a usage page
acme/web · aldo/k3v9x2
Add a usage page that shows credits by day, like the one in admin. Ship it when it's green.
- Created your cloud agent4 vCPU · 8 GB
- Cloned acme/web onto aldo/k3v9x2
- Edited 7 files+248 −31
- Started web: pnpm dev on :3000
- Checked /usage in Chromedemo recorded
- Opened pull request #214
- Checks failed: lintfixed in a1c9e04
- Checks passed, merged on green
- Deployed, and checked /usage in production
Done. /usage is live with credits by day for the last 30 days, and its totals match the Usage API. The demo recording is on #214.
Runs
- Claude Code
- Codex
- OpenCode
- Grok Build
The latest release of each, on the subscriptions you already have.
01A computer for every thread
Each thread gets its own computer.
Not a chat with a diff at the end. A thread is a whole machine: your code on its own branch, your app running, a real browser and a desktop. Run several at once; they never step on each other.
Its own machine
4 vCPUs and 8 GB, with your repository cloned onto the thread's own branch. When the work runs short, the thread offers a 2× machine.
Your app, running
Agents run your dev servers as services that come back after every wake, and share preview links only you can open.
A real browser
Chrome runs on the machine. The agent clicks through what it built; you watch it in the Browser panel, or take over.
working
10 min idle
asleep, disk kept
you reply
Reminder, 5:00 · check whether the nightly import finished
Sleeps when it's done
Ten idle minutes and the machine stops, keeping its whole disk. Reply, or let a reminder come due, and it picks up where it was.
- Install
- pnpm install && pnpm db:migrate
- Services
- postgres, web, worker
- Built
- today, 6:02 · rebuilds daily
Ready to go
Save how to install and what to run once. New threads start from a snapshot with the database up and the app already running.
Across repositories
A thread can work in several repositories side by side, from GitHub, GitLab, Bitbucket and Azure DevOps.
02From prompt to production
It doesn't stop at the pull request.
Aldo follows every pull request an agent opens. Failing checks and comments come back to the thread as new work. After the merge, Aldo watches the deploy, so the agent checks production itself.
You ask
Describe the change in a thread, from your laptop or your phone.
It builds
Code and tests, the app running, and a look at it in the browser.
It opens the pull request
With a screen recording of the change attached for reviewers.
It answers checks and reviews
Failed checks and reviewers' comments wake the agent until it's green.
Aldo merges
When your policy says so, once it's been green for 10 minutes. Or you tap Merge.
It checks production
Aldo follows the deploy; the agent verifies it live and reports back.
Add a usage page #214
acme/web · aldo/k3v9x2 → main · +248 −31
Demo recording
/usage, credits by day · 0:24
- build1m 12s
- lintfixed in a1c9e04
- typecheck48s
- Vercel: previewReady
dana commented: Start weeks on Monday, please.
Agent: Done in 3be1f2a; the chart and the totals both start on Monday now.
- Checks
- Merged
- Deploying
- Deployed
Merged by Aldo after 10 minutes green, as the workspace's policy says. Production checked.
03Your rules
Asks once. Then it knows.
Aldo has no defaults for how you work. The first time an agent meets a decision you haven't made, it asks. Your answer becomes the workspace's policy, and every thread after follows it.
- Merge on green, or wait for you
- How each repository merges
- How much an agent may spend without asking
- Which automated review comments to act on
#214 is green. Should I merge pull requests in this workspace once their checks pass, or wait for you each time?
Merge on green. Squash them.
Saved to the policy for acme/web + acme/api
Workspace policy
- Merging
- On green
- acme/web merges by
- Squash
- Spending without asking
- Up to $25
- Automated reviews
- Fix what matters
04The vault
Secrets, sealed until a thread needs them.
Keep API keys, files and website logins in the vault. You choose how each reaches a thread: as a variable or a file the agent can read, or injected by the network on the way out, so the agent uses a key it never sees.
$ echo $STRIPE_SECRET_KEY
sk_live_•••••••••••••••••← a stand-in of the same shape
$ curl https://api.stripe.com/v1/balance -u "$STRIPE_SECRET_KEY:"
{ "object": "balance", "livemode": true, … }← the real key, added on the way out
$ git push
aldo: not pushing. These commits contain the value of STRIPE_WEBHOOK_SECRET from the user's vault.
Injected on the way out
For keys you choose, the machine holds a stand-in of the same shape. Aldo's firewall adds the real key to requests for the sites you list.
Logins filled for them
Aldo types a saved password into the page after checking the page's origin. The agent asks for the fill and never handles the password.
Refused in commits
A push, pull request or comment that contains a vault value is refused, and service logs hide them.
Tuesday, September 29
9:41
Stripe webhooksnow
Needs you. Which Stripe account should get test events: acme-dev or acme-staging?
Add a usage page4m ago
Done. /usage is live, and its totals match the Usage API.
Rate-limit the export22m ago
Done. The deploy failed on a missing variable. Added it and redeployed; it's live.
05From anywhere
Review from your phone.
Threads tell your devices when they finish or need you, with a line of what they did or asked. Answer from your phone and a sleeping thread wakes to pick it up.
- Needs you
- A question, an approval or a plan to look over.
- Done
- With a line of what it did, and the pull request's stage.
- Deploy failed
- The agent hears first. You hear when it's handled.
- Green
- Merge a pull request from the thread's list with one tap.
06Pricing
Bring your agents.
We bring the machines.
Aldo runs each agent's official CLI, signed in once with your own account. It doesn't resell tokens or mark up models. You pay Aldo for machine time, by the minute, while a machine runs.
- Claude Code
- Claude Pro, Max, Team or Enterprise
- Codex
- ChatGPT Plus, Pro, Business or Enterprise
- Grok Build
- SuperGrok or X Premium+
- OpenCode
- Installed on every machine
Plans
Starter
40 machine hours · 2 agents at once
$20/mo
Pro
150 machine hours · 5 agents at once
$60/mo
Max
550 machine hours · 15 agents at once
$200/mo
A credit is an hour of a standard machine. A thread that's asleep costs nothing.
Compare plans