Skip to main content
This page lists what each Harness supports on each placement. Core decides admission from the Harness’s engine profile in services/core/internal/engine, and the Runtime that runs the Session must also advertise the operation. The linked contracts define each operation; Harness onboarding describes how a Harness is qualified. Placements are none (no Environment), hosted (openai_hosted) and self-hosted (self_hosted). Hosted acceptance ran on Docker nodes; E2B and microsandbox run the same Runtime and adapters, and every Verified hosted cell counts as Admitted there. Self-hosted acceptance ran on Linux machines; the self-hosted guide lists the supported platforms. A verified operation is verified on its own, not in every combination with other options; combinations that a profile rejects are listed in the operation’s contract.

Execution and input

Native model parameters and provider protocols per Harness are in model execution.

Tools

Claude structured output requires a single Agent, medium verbosity and no Skills, Plugins, capability directories, MCP or tool_search. Claude deferred discovery requires a single Agent, only function tools besides tool_search and the disabled controls, no Skills, Plugins or capability directories and no structured output. Claude on a workspace placement needs the packaged bridge features for each operation (workspace_functions, workspace_structured_output, workspace_tool_search, workspace_mcp_http).

Environment preparation

These operations need a workspace, so they apply to hosted and self-hosted placements only.