Documentation

Cloudbox docs

Cloudbox gives agents Cloudflare-native computers for real repo work: commands to execute, files to inspect, dev previews to steer, artifacts to return, and receipts to audit. These docs show the seven-minute path, the demo run, the core concepts, and the API.

Pick your path

Quickstart

Deploy or run locally, call /api/runs, and inspect proof in minutes.

Demo

Run a public repo in a Cloudflare Container and inspect runner receipts, work receipts, and an artifact.

Concepts

Repo computers are the product center. Typed workspaces remain as a secondary evaluation surface.

API reference

Repo-run, live-run, preview, and workspace endpoints with curl examples and response shapes.

Recipes

Bring your agent, run proof from CI, steer live work, and use optional advanced surfaces.

Architecture

Worker control plane, Container runners, live-run snapshots, R2/D1/DO state, and authority boundaries.

Product center

Cloudbox should stay centered on runs. A run is a clean remote repo computer that returns receipts, diff, and an artifact. Live runs can stay open for file and command access, an optional secure dev preview such as a remote bun run dev, stop/resume/fork lifecycle, and the same reviewable proof trail when the run closes.

Status

Alpha. Repo runs, live steering, dev preview, stop/resume/fork, shareable proof pages, and TypeScript adapters are in the repo. Desktop/browser-shell sessions, durable owner computers, and typed workspaces are advanced or evaluation surfaces. Source on GitHub.