Explainers
Preview. These pages describe moca on
main; interfaces and limits may change.
Each explainer is a single self-contained page you step through, rather than read: press Next, or click a step, and watch the request, the pool or the lease move. They open in a new tab and need an internet connection (they load their styling from a CDN).
Each one illustrates a written design. The links below go to the prose docs that cover the same ground, and each explainer's footer cites the code and the design record it was built from.
Start with the two overview explainers if you are new to moca. The four after them go deeper on one part of the sandbox service or the harness.
| Explainer | Shows | Capability | Written docs |
|---|---|---|---|
| Moca: the harness and the sandbox | How the two capabilities differ, how a harness turn runs end to end, and the relay, workers and route profiles they share | Both | Overview, Brain and hands |
| The moca sandbox service | Why the agent stays on your laptop, and how one command reaches a fresh microVM and comes back as a patch | Sandbox service | Overview, Isolation and data handling |
| Sandbox authentication and exec flow | How a client gets a sandbox token, and how one Exec reaches a fresh microVM and comes back | Sandbox service | Isolation and data handling, Direct API |
| Admission and the microVM pool | How the VM pool admits, queues and reclaims work against a memory budget, and when a workspace is deleted | Sandbox service | Limits, Install the sandbox service |
| Lease mode | Why lease keeps one guest warm between commands, and what survives in each of the three modes | Sandbox service | Keep a guest between commands |
| Async fan-out | How async: true leaves are queued, drained inside a worker under the turn admission budget and recovered after a crash | Harness | Dispatch archetypes |