moca · harness + sandbox · v0.11.0
moca runs AI coding agents safely and at scale. It has two capabilities. The harness runs the agent itself, in long-lived sessions on a warm worker pool. The sandbox service runs the agent's commands while the agent stays on your laptop. Both use the same relay, the same sandbox workers and one control plane. 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. Use the tabs to change the flow.
‹ moca docs · written pages: Brain and hands, Sessions and turns, Sandboxes and tiers
The decision
Keep the agent's commands away from the agent's process. The two capabilities differ only in where the agent runs. The harness keeps the agent in a warm worker. The sandbox service keeps it on your laptop.
This is the positioning on the moca overview. Use one capability alone, or both together on one control plane with the combined profile.
A harness session runs its tools in the harness's own sandbox. A sandbox-service workspace is a separate thing. mocactl sbx commands neither see nor manage a harness session's sandbox.
Not a fit today: a sandbox service on your laptop (it needs OpenShift and a KVM host), scheduled dispatch (no P6 design yet, #536), and a hosted service (moca is self-hosted only).