Runtimes

Provider CLI

Supported provider CLIs, maturity levels, shared runtime behavior, and extension points.

A provider CLI is the program that executes an agent task, such as Claude Code or Codex. Mopheus discovers the CLI on the daemon host, dispatches tasks to it, and collects the result.

Supported Provider CLIs

Provider CLIs are ranked by maturity and integration depth in Mopheus:

Provider CLIProvider valueProtocolSession resumeAgent steeringMopheus-managed MCPSkill pathFilesystem sandboxMaturity
Claude CodeclaudeNativeYesActive-turnYes.claude/skills/YesCore (5★)
CodexcodexNativeYesActive-turnYes.codex/skills/YesCore (5★)
AntigravityantigravityNativeYesNext-turnNo.agents/skills/YesNative (4★+)
PipiNativeYesNoneNo.pi/skills/YesNative RPC (4★)
OpenCodeopencodeNativeYesNoneYes.opencode/skills/YesAvailable (3★)
KimiCodekimi-codeNativeYesNoneNo.kimi/skills/YesAvailable (2.5★)
MimoCodemimo-codeNativeYesNoneYes.mimocode/skills/YesDerivative (2★)
ACP-Compatible CLIsacpACPYesNext-turnYes.<cli>/skills/YesProtocol standard

Interaction delivery references

  • Claude Code: CLI reference; supports active-turn steering with next-turn fallback.
  • Codex: active-turn turn/steer real-time interaction.
  • Antigravity: stream-json line protocol; supports thinking block expansion and next-turn interactions.
  • Pi: native JSON-RPC subprocess communication; independent session management and event sanitization.
  • ACP and compatible ACP CLIs: ACP v2 prompt lifecycle proposal; use next-turn delivery, including Hermes, Kiro, Qoder, etc.
  • Native CLIs reporting none: OpenCode, Kimi Code, and MiMo Code.

Provider Guides

Workspace-Scoped Session History

For Claude Code, Codex, and Pi, resumable session history is separated by workspace whether or not the filesystem sandbox is enabled. Some other providers use host-global history without the sandbox. The sandbox mounts only the current workspace's managed session data at the path expected by the CLI.

Credentials, global CLI preferences, plugins, and caches not listed in a provider guide remain owned by the daemon user and are not copied into a workspace. Existing host-global session history is not migrated automatically.

See Filesystem Sandbox for the visibility boundary and read-only filesystem rules.

Auto-Discovery

At startup, the daemon probes built-in provider commands through their path-override environment variables and $PATH, then reads --version when possible. A new CLI installed while the daemon is running is detected during the next workspace sync cycle, normally within 30 seconds.

Extending Providers

Use Custom Provider CLI to clone a built-in provider or register an ACP-compatible CLI. Run mopheus provider list to inspect built-in and custom entries.