Your coding agent stays on your laptop. Every command it runs
goes to a fresh, isolated microVM on a shared service. The agent keeps your files, your credentials and your
editor. The service keeps the command away from all three. Step through one command, from the tool call to
the patch you apply. Press Next for one step. Press Prev to go back one step. The wire box below the stage
shows the messages of the current step. The messages stay until you move on.
The agent stays where the credentials and the editor are. The command runs where the service can isolate it.
One Exec gets one fresh microVM. Files under
/workspace persist. Nothing else does.
This is the positioning on the
moca overview: one of two
capabilities, usable alone or beside the harness. The harness runs the agent itself. The sandbox service
runs the agent's commands. This page follows the second one.
What one Exec guarantees
bash -c <command> with /workspace as the working directory.
One fresh Firecracker VM, by default one per Exec (ADR-0035).
Files under /workspace persist for the sandbox's lifetime.
No process survives the Exec. No file outside /workspace survives it.
Output is capped at 8 MiB. The end frame reports truncation.
The sandbox token
typ
moca-sandbox+jwt
alg
EdDSA
aud
moca-sandbox
sbx
one sandbox id
wrk
one worker
wsk
one workspace key
exp
≤ 15 min, ≤ the sandbox expiry
The control plane mints it for the owner. The relay
checks it with a public key. The relay reads no Redis record to authorize a call.
What the guest cannot reach
No network device. A template with egress reaches only allowlisted hosts, through the host's proxy.
No secrets. No credentials, no tokens, none of your laptop's files except the ones you pushed.
No shared user with another sandbox: each sandbox is its own VM.
Any other destination answers 403 destination_denied.
Why it is built this way
Sandbox workers dial out to the relay, so a sandbox needs no inbound route.
That lets a KVM host sit outside the cluster, behind NAT or on another network.
One deploy serves many developers and many agents from one template store.
The relay is a single replica. A restart drops attached streams; recovery is a retry.