Selection order
- Identify required tools, continuation, files, previews, network restrictions, and idle recovery.
- Select an exact registered Harness id/version and supported model protocol.
- Configure and verify the actual endpoint/model.
- Choose a Sandbox capable of that distribution: OCI, private images, and allowlists are separate requirements.
- Bind authorized Tools with explicit readiness and approval policy.
- Preflight, execute, inspect output, and confirm cleanup.
Start from the task, not the matrix total
For the current first-Session and project tutorials, fresh dual-SDK evidence is available for Vercel, built-in Pi 1.5.2 and the configured Messages/DeepSeek-V4-Flash endpoint. Use that as a scoped reference, then verify your own connections. If you need a different model protocol, OCI distribution, external Tool approval or an enforced network allowlist, check evidence for that requirement explicitly; the tutorial pass does not supply it. Write down the required behavior before comparing alternatives: for example, “two project turns, private HTTP preview, retained exports, no external Tools.” A single row that proves those requirements is more useful than a larger count of unrelated passed combinations. If a requirement is unsupported, preserve the requirement and select another combination or report the gap.Starting points and alternatives
Historical dual-SDK journeys include E2B/Pi 1.5.2/SiliconFlow and E2B/OpenCode 1.2.27/SiliconFlow. Check exact records for endpoint, protocol, scope, and date. These support selecting a trial starting point, not skipping verification of your current account/model. Native OCI execution uses Modal or Fly Machines. E2B also prepares public OCI images through a Session-owned Template; verify build, execution, and template cleanup separately. Check private-image support independently. Built-in OpenCode success does not prove OCI OpenCode compatibility on that Provider. For allowlists, choose an explicitly capable adapter and allow credential ingress. For idle recovery, consult the separate lifecycle matrix; normal execution does not establish recovery.
For example, codex-v1 requires Responses; pairing it with Messages fails. Renaming a connection does not change its wire protocol.
Quota, endpoint behavior, network, and initialization can still fail after preflight. Retain request/resource identity and use recovery. Next: model connections, protocols. Source: resolver.
Compare three scoped routes
These routes answer different needs; the network probe is evidence for an enforcement requirement, not a drop-in replacement for a coding Agent. Keep the selected Harness version/digest and model protocol in your decision record. Empty matrix cells or a missing scenario are unverified, not inferred support.
Sources: execution combinations, model protocols, verified combinations. Next: Sandbox capabilities, Harness selection, model connections.