Why this demo exists

Cloudbox should prove real work, not describe it. The demo exercises the hosted repo-run path:

repo -> CloudboxRunner DO -> Cloudflare Container -> commands -> verify -> artifact + receipts

It is intentionally constrained because it is public. The hosted demo accepts public GitHub repos and a small allow-list of safe commands. Deploy your own Cloudbox for real private or privileged agent work.

What to look for

On /demo, click Run in Cloudbox. A successful run should show:

1. Runner — container lifecycle proof, including readiness time and attempt count
2. Clone — a fresh checkout of the repo
3. Run — the command your agent asked for
4. Verify — explicit checks before the result counts
5. Artifact — one file returned for human inspection

The raw JSON includes two proof layers:

• runnerReceipts — computer lifecycle events (runner.container.start, runner.container.ready, runner.response)
• receipts — repo work events (clone, command, verify, diff)

Causal proof

The default demo command writes a unique artifact:

echo cloudbox-container-ok > HANDOFF.md
test -f HANDOFF.md

The artifact content must match what the command wrote. That is the basic contract: command causes file, verify checks it, Cloudbox returns the artifact and receipts.

How to adapt it

Use the same /api/runs shape from any agent:

{
  "repo": "https://github.com/you/app",
  "commands": ["pnpm install --ignore-scripts", "pnpm run build"],
  "verify": ["pnpm test"],
  "artifact": "HANDOFF.md"
}

For richer file/workspace/grading flows, materialize a ComputerSpec with /api/computers and drive /api/c/:id/*.