Sandbox Harnesses
OpenCode is one harness. Do not describe Tangle’s sandbox product, SDK, or AI Agent Sandbox blueprint as an OpenCode integration.
There are three related surfaces:
| Surface | Source of truth | Current harness set |
|---|---|---|
| Published Sandbox SDK | @tangle-network/sandbox BackendType | OpenCode, Claude Code, Kimi Code, Codex, AMP, Factory Droids, Pi, Hermes, Forge, OpenClaw, NanoClaw, ACP, Cursor, and CLI base. |
| Current Sandbox UI picker | sandbox-ui harness picker | OpenCode, Claude Code, Codex, AMP, Factory Droids, Kimi Code, OpenClaw, NanoClaw, Hermes, and CLI base. The picker defers SDK backends such as Pi, Forge, ACP, and Cursor until copy and compatibility policy land. |
| AI Agent Sandbox blueprint sidecar | The operator’s /api/capabilities response | Claude Code, Codex, OpenCode, Kimi Code, and Gemini CLI in the current ghcr.io/tangle-network/blueprint-sidecar:all-harness image. |
The centralized sandbox infrastructure can expose a broader harness menu than a specific protocol-backed service instance. A blueprint service instance must read the operator endpoint before promising a harness to a user.
Centralized sandbox infrastructure
The hosted sandbox infrastructure is product/API-key gated. It can present the Sandbox UI harness picker, model picker, session controls, and profile system without implying any protocol guarantee.
The published SDK accepts these backend types:
| Harness | Notes |
|---|---|
| OpenCode | Coding harness. |
| Claude Code | Claude Code CLI harness. |
| Kimi Code | Kimi Code CLI harness. |
| Codex | Codex CLI harness. |
| AMP | Sourcegraph AMP harness. |
| Factory Droids | Factory Droid harness. |
| Pi | SDK backend type; not surfaced in the current Sandbox UI picker. |
| Hermes | Hermes coding harness. |
| Forge | SDK backend type; not surfaced in the current Sandbox UI picker. |
| OpenClaw | Dispatcher path for Claude, Codex, and Gemini CLIs. |
| NanoClaw | Local socket-bridge agent backend. |
| ACP | Agent Client Protocol bridge for ACP-compliant agent binaries. |
| Cursor | Cursor Agent SDK backend. |
| CLI base | Shell and workflow tools without a coding harness. |
The current Sandbox UI picker exposes OpenClaw and NanoClaw while deferring Pi, Forge, ACP, and Cursor. Product docs should say which surface they mean and should prefer /api/capabilities for live operator surfaces.
These are execution harnesses, not routing categories. Every coding harness runs inside the sandbox. Unless a profile, user setting, or operator config points elsewhere, model calls go through Tangle Router. Do not describe routing as a property of one harness.
AI Agent Sandbox blueprint
The AI Agent Sandbox blueprint is a protocol-backed service. The blueprint ABI creates and manages service instances; the sidecar image supplies the runtime toolchain.
Current capability discovery returns:
| Capability | Meaning |
|---|---|
computer_use | Browser/computer-use sidecar services. |
all_harness | The all-harness sidecar image for Claude Code, Codex, OpenCode, Kimi Code, and Gemini CLI. |
Read GET /api/capabilities before rendering a harness choice. The image tag is a hint, not a live proof. Operators can publish a different sidecar image or build a smaller subset while keeping the blueprint jobs unchanged.
Copy rule
Any public copy that names OpenCode must name the peer harnesses or link to this page. The correct framing is:
The sandbox supports multiple harnesses. OpenCode is one adapter beside Claude Code, Kimi Code, Codex, AMP, Factory Droids, Pi, Hermes, Forge, OpenClaw, NanoClaw, ACP, Cursor, CLI base, and blueprint sidecar images that may advertise a smaller set through
/api/capabilities.
The wrong framing is:
Tangle’s sandbox is a single CLI integration.