Skip to main content
The connection provider identifies a wire protocol, not a vendor. The proxy forwards allowed paths without converting Messages, Chat Completions, and Responses or guessing a fallback protocol.

Current Harness contracts

This describes Hexagon adapters, not all upstream project functionality or live acceptance for every image/endpoint. OCI registrations pin versions and compatibility metadata. Existing registrations do not automatically expand when adapters change; inspect the actual registration and create a new version where required.

Dated endpoint examples

These are repository acceptance observations from November 18, 2026, not a current availability check or a recommendation to change providers. Model ID is MiniMax-M3 in all three rows. Each row was tested separately; the same brand does not make their interfaces interchangeable. The dated matrix specifies two-turn tasks, actual assigned MCP calls, inputs, environment, artifacts and cleanup for the tool-capable combinations. It also retains early unknown creation attempts: successful task rows do not establish global resource cleanup. These records supplement rather than replace preview, approval and failure-recovery journeys. Inspect the exact row for the chosen Sandbox. OCI variants additionally require the image digest and command; a built-in result is not an OCI result.

A shared protocol is only one requirement

Tasks depend on streaming, tool calls/results, continuation, errors, and actual model capability. A greeting response does not establish functioning Tools. An endpoint’s compatibility claim does not establish every optional field or mode. Responses validation currently uses store:false. It does not promise server-hosted built-in tools, background polling, WebSocket mode, or other protocol extensions. Harness Tools continue through the platform mailbox and approval system. Some OpenCode/Pi Responses tests use actual binaries with a deterministic endpoint. That validates those protocol branches, not every live account. Cloud evidence must identify endpoint, model ID, Harness version, SDK, and task scope.

Locate a failure in the request path

A validation error can occur before Sandbox allocation; a later Run can fail because the Sandbox cannot reach credential ingress even while the model endpoint remains reachable from the control plane. Diagnose the two network legs separately. Do not replace a protocol-mismatch problem with credential rotation, or a blocked ingress problem with embedding an upstream key in guest configuration.

Select and diagnose

Intersect the endpoint’s actual protocol with Harness support. codex-v1 requires a real Responses endpoint; renaming a Messages connection cannot convert it. Do not append the final operation path to the base URL. For incompatible_model, inspect protocol selection before credentials. For validation failure, check network, permissions, exact model ID, and response shape. Revalidate/re-enable after correction, then execute the required real journey. Sources: Runtime protocols, Pi, OpenCode. Next: model configuration, verified combinations, errors.