Skip to main content
This is preview documentation. The official release is not yet available.
Runtime Host includes five provider adapters. runtime probe checks executable discovery; real work also needs valid login, models and tools.

​
Runtime types

Install and authenticate the provider before connecting Host. These are Service adapters; provider binaries are not bundled in the Service CLI release.

​
Portable definition mapping

Support indicates an implemented adapter path; installed CLI version and account capabilities still matter. Native Subagent mapping requires Codex 0.153.4+ or Qoder 1.0.37+ and currently requires shared workspaces. Codex mapping cannot enforce Subagent tools or maxIters. Qoder tool names must map to supported native tools. Codex, Qoder and QwenPaw provide control-plane tool approval integration. Claude Code uses its CLI permission configuration; this does not promise the same Inbox approval flow. OpenClaw uses the task CLI through Shell for collaboration because its adapter does not inject MCP.

​
Choosing a provider

Check the columns for persistent sessions, approvals and Subagents before choosing. Review tool policy support before reusing a definition designed for Managed Agents. For example, Codex supports MCP while rejecting Managed built-in tool policies. Teams can mix providers. Verify each member’s independent execution and collaboration tools before testing Leader delegation and final delivery. Native Subagents and Service Teams operate at different levels. Next: configuration and execution model.