Use recipes when you know the job and need the smallest working pattern.
CI/CD smoke tests
Prove your deployed runner can boot, execute, verify, and return a causal artifact.
Bring your agent
Let your agent emit a structured run, then use Cloudbox as the computer/proof layer.
Give your agent a browser
Add Chrome next to Cloudbox repo tools, with optional profile reuse for logged-in flows.
Proof runs
Clean-room repo checks that return a handoff, receipts, and an artifact.
Runner readiness
Continuously check the computer lifecycle: start, ready, response.
Workspace protocol
Use ComputerSpec workspaces for file tasks, collaborators, submissions, receipts, and grading.
Core loop
Every recipe should preserve the same shape:
agent or CI decides work -> CloudboxRun or ComputerSpec -> fresh computer -> verify -> artifact + receipts
If the artifact is not caused by the run, it is not proof. If the receipt is missing, the claim did not happen.