Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.compose.market/llms.txt

Use this file to discover all available pages before exploring further.

Harness subagents run in-process by default. Physical isolation is opt-in through isolated: true on a task step or requireIsolation: true on a plan path that routes into the sandbox adapter.

​
Behavior

harness/sandbox.ts uses the Daytona integration in runtime/src/mesh/sandbox.ts.
ConditionBehavior
DAYTONA_CONCLAVE_SNAPSHOT_ID configuredBoot a fresh Daytona sandbox and run the harness boot command.
Snapshot missingReturn a typed sandbox_unavailable error.
Sandbox command exits 0Return completed.
Sandbox command exits nonzeroReturn error with stderr preview.
Explicit isolation never silently downgrades to in-process execution.

​
Example

steps:
  - op: task
    saveAs: isolatedResult
    agentWallet: "0x1111111111111111111111111111111111111111"
    prompt: "Analyze the untrusted archive."
    isolated: true
    budget:
      maxWallMs: 180000

​
Sandbox Evidence

Sandbox execution can return metering records, sandbox labels, stdout/stderr, wall time, and exit code. Proof bundles can include sandbox metadata when isolation is active.