Recipes
Small patterns for using Cloudbox in CI, with agents, and as a proof-producing computer for repo work.
Use recipes when you know the job and need the smallest working pattern.
Prove your deployed runner can boot, execute, verify, and return a causal artifact.
Let your agent emit a structured run, then use Cloudbox as the computer/proof layer.
Add Chrome next to Cloudbox repo tools, with optional profile reuse for logged-in flows.
Clean-room repo checks that return a handoff, receipts, and an artifact.
Continuously check the computer lifecycle: start, ready, response.
Secondary surface for typed ComputerSpec tasks, collaborators, submissions, receipts, and grading.
Expose a materialized computer as typed env_* tools with createCloudboxTools, then hand them to any agent runner.
Core loop
Every recipe should preserve the same shape:
repo -> fresh Cloudflare computer -> live steering -> explicit verification -> artifact + diff + receiptsIf the artifact is not caused by the run, it is not proof. If the receipt is missing, the claim did not happen.