Harness
Preview. Every harness deployment path is Preview: interfaces and limits may still change (Maturity and lifecycle).
The moca harness runs the agent itself. A supervisor hands each connection to a pool of warm
workers, sessions are durable in Redis and resume by id, and the agent's tools run in a remote
sandbox (a container, or a Firecracker microVM per command). You drive it over HTTP (/turn,
/v1/runs) or with mocactl. It is not the sandbox service: a harness
session's tools run in the harness's own sandbox, which mocactl sbx neither sees nor manages.
New here? The quickstart runs it on your laptop in about five minutes.
Tasks​
| Page | What it covers |
|---|---|
| Set up mocactl against the Compose trial | from nothing to a streamed reply in mocactl |
| Use mocactl | install, keys, headless commands, spawn/subagents/get, files, troubleshooting |
| Promote a Claude Code workflow | mocactl promote: a local workflow as a config bundle |
| Context Service and workloads | what a workload is, its lifecycle, and the context it holds |
| Delegate from a coding agent | the moca-delegate-task skill for Claude Code and Codex |
Concepts and reference​
- Concepts: sessions and turns, brain and hands, session multiplexing, sandboxes and tiers, multi-user, dispatch archetypes, context workflows.
- Reference: the
mocactlcommand reference (generated from the CLI), the HTTP API and the leaf and envelope. - Deploying it: Deploy and operate.