Fresh Cloudflare computers for agents.
Boot a repo computer. Steer real work. Review the proof.
Cloudbox gives your agent a clean Cloudflare Container with a real Git checkout. Keep it live for human steering, run explicit verification, then get receipts, diff, and the artifact that proves what happened.
const response = await fetch("https://cloudbox.coey.dev/api/runs", {
method: "POST",
headers: {
authorization: "Bearer $CLOUDBOX_API_TOKEN",
"content-type": "application/json",
},
body: JSON.stringify({
repo: "https://github.com/acoyfellow/cloudbox",
commands: ["pnpm install --ignore-scripts"],
verify: ["pnpm run build", "pnpm run test"],
artifact: "HANDOFF.md",
live: true,
ttlSeconds: 3600,
public: true,
}),
});
const proof = await response.json();
console.log(proof.runId, proof.ok);
console.log(proof.artifact?.content);
// receipts + runnerReceipts + diff + optional publicUrl A clean Cloudflare Container boots with the repo already cloned.
Inspect files, run follow-up commands, write safe paths, and open preview URLs.
Lifecycle evidence, command output, verification, diff, and one named artifact.
Your agent calls Cloudbox over HTTP or through the TypeScript adapters. Cloudbox is not the model loop; it is the repo computer and proof layer. Bring your agent →
How runs work
One product path: repo → computer → steering → verification → proof.
A first run should be boringly concrete: clone a repository, boot a Cloudflare computer, let the agent work, inspect while it is live, then close with verification output, lifecycle receipts, a diff, and a human-readable artifact.
Repo
Start from a real Git URL and a clean checkout. Learn more →
Boot
Spin up a fresh Cloudflare Container for the task. Learn more →
Steer
Exec, read/write files, and open an authenticated dev preview while it is live. Learn more →
Verify
Run explicit checks before the work counts. Learn more →
Receipts
Return lifecycle receipts, diff, and the requested artifact. Learn more →
Product center
A run you can steer while it is alive.
Cloudbox stays run-shaped: boot a clean repo computer, let an agent work, inspect files, execute follow-up commands, start an authenticated dev preview, and close with receipts plus an artifact. Stop, resume, and fork keep the same work reviewable without turning Cloudbox into a generic IDE or sandbox marketplace.
Repo computers
A fresh checkout per task, real commands, live file access, authenticated dev preview, explicit verification, artifacts, and shareable receipts.
Live steering
Humans can inspect the live repo, run follow-up commands, edit safe relative files, open preview URLs, and resume or fork work later.
Receipts first
Every claim points back to runner lifecycle evidence, command receipts, verification output, the diff, and a named artifact.
Learn next
Pick the path that matches how you want to use it.
Try the hosted demo
Run a public GitHub repo and inspect the returned artifact and receipts.
Read the quickstart
Install with pnpm, run the demo, and see exactly where Bun is used.
Bring your agent
Use any model loop. Cloudbox is the repo computer and proof layer.
Run it from CI
Upload Cloudbox proof as a build artifact with commands, diff, and receipts.