Skip to main content
Version: next

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.

ExplainerShowsCapabilityWritten docs
Moca: the harness and the sandboxHow the two capabilities differ, how a harness turn runs end to end, and the relay, workers and route profiles they shareBothOverview, Brain and hands
The moca sandbox serviceWhy the agent stays on your laptop, and how one command reaches a fresh microVM and comes back as a patchSandbox serviceOverview, Isolation and data handling
Sandbox authentication and exec flowHow a client gets a sandbox token, and how one Exec reaches a fresh microVM and comes backSandbox serviceIsolation and data handling, Direct API
Admission and the microVM poolHow the VM pool admits, queues and reclaims work against a memory budget, and when a workspace is deletedSandbox serviceLimits, Install the sandbox service
Lease modeWhy lease keeps one guest warm between commands, and what survives in each of the three modesSandbox serviceKeep a guest between commands
Async fan-outHow async: true leaves are queued, drained inside a worker under the turn admission budget and recovered after a crashHarnessDispatch archetypes