Skip to main content
A Harness executes Agent logic, model interaction, conversation, and Tools. Runtime supervises its process; the control plane manages tasks, authorization, and cloud resources. Built-in Pi 1.5.2 and OpenCode 1.2.27 currently declare conversation, Tools, initialization, and all three model protocols. Query catalog() for the actual deployment.

Minimal built-in selection

These preflight excerpts reuse an initialized client and enabled connection IDs from the first Session. They do not register an image or allocate a Sandbox. Choose one exact selector; replacing Pi with OpenCode changes the Harness, not the model protocol.
Continue with the tutorial’s durable create/submit/observe/close flow. A ready preflight checks configuration compatibility; it does not install the CLI, call the model or prove that a task succeeds. Keep the Harness selector fixed for an existing Session. To compare engines, create separate Sessions and compare actual task results, Tools, artifacts and cleanup.

Template index

See the image catalog for source/version and published-image versus recipe status. Names here do not establish complete cloud acceptance. The following repository snapshot is dated November 20, 2026. “Adapter contract” means local invocation/result tests, not a container execution pass. “Scoped cloud records” means exact image + command + protocol entries in the verification registry; consult their model, SDK and scenario fields before selecting a combination. An empty entry means no matching catalog evidence, not that the program cannot run. Contract sources: Runtime adapter tests, managed CLI tests, package result tests. These checks are narrower than image build, cloud startup or a complete user journey. Lifecycle behavior also depends on the Sandbox: native conversation IDs do not guarantee that arbitrary processes or memory survive idle.

Codex

codex-v1 uses Responses, MCP-bridged Tools, and native continuation. Verify the registered image source/digest and execution evidence.

Hermes

hermes-v1 uses Chat Completions, MCP Tools, and native continuation.

OpenClaw

openclaw-v1 declares all three protocols and MCP Tools. Evidence for one protocol does not certify the others.

DeepSeek Harness

deepseek-v1 currently uses Messages and a build recipe. Do not declare unsupported initialization. Build, distribution, and cloud execution are separate steps.

OpenCode

opencode-v1 declares all three protocols and Tools. Built-in and OCI OpenCode have different distribution/Provider requirements.

Aider

aider-v1 uses Messages and restored history. Its current adapter has no connected Tools and does not accept initialization capability.

Pi

pi-v1 supports three protocols and extension-based Tools. A buildable recipe is not automatically a published image.

Claude Code

claude-code-v1 uses Messages and MCP Tools. Respect actual permissions rather than assuming root-incompatible bypass modes.

Python Agent

hexagon-json-v1 is a Messages-based example with mailbox Tools and custom continuation. Custom code owns correct conversation persistence.

Select and verify

Match model protocols, Tools/initialization needs, and Sandbox OCI/private-image/recovery capabilities. Verify two turns, Tools, artifacts, cancellation, cleanup, and idle recovery when required. Capabilities cannot create missing adapter behavior. Registering Tools for Aider cannot implement them, and changing a version label cannot change image behavior. Next: OCI, source packages, model protocols. Sources: protocols, registration.