Codex runtime
Codex is a strong choice when you already use the official Codex CLI and want Jarvis to supervise sessions without replacing your normal CLI config model.
Good fit
Section titled “Good fit”Use Codex with Jarvis when you want:
- managed Codex sessions inside the Jarvis control tower
- discovery of compatible local Codex sessions
- terminal streaming and follow-up dispatch from Jarvis
- worker MCP reporting on managed sessions
- a runtime that keeps using your existing Codex defaults unless you explicitly choose otherwise
Prerequisites
Section titled “Prerequisites”- the Codex CLI installed and available as
codex, or configured through Jarvis runtime settings - a working Codex CLI authentication setup
- a workspace directory where project-scoped Codex config can be used if Jarvis injects worker MCP support
What Jarvis manages
Section titled “What Jarvis manages”For managed Codex sessions, Jarvis can:
- launch and supervise the Codex process
- attach terminal output to the Jarvis session view
- inject Jarvis worker MCP reporting tools for managed workers
- discover compatible local Codex sessions for Session OS
- include Codex sessions in summary capsules and intervention tracking
- stop or interrupt managed sessions through the runtime channel
Current managed-worker integration uses launch-time overrides and project-scoped MCP wiring where needed. That lets Jarvis add reporting tools without rewriting your user-level Codex identity.
What stays in your Codex CLI setup
Section titled “What stays in your Codex CLI setup”These remain under your control:
- your Codex login and account state
- your user-level Codex configuration, including default provider choices
- your broader CLI workflow outside Jarvis
Jarvis may read your Codex defaults so it can launch sessions honestly, but it does not use Jarvis as the new source of truth for your personal Codex auth.
Common failures
Section titled “Common failures”codex is not found
Section titled “codex is not found”Jarvis can only launch Codex after the CLI is installed or the command path is configured correctly.
A worker session starts, but reporting tools are missing
Section titled “A worker session starts, but reporting tools are missing”Managed Codex workers depend on project-scoped MCP wiring being visible in the session workspace. If that step failed or the runtime could not see the expected config, the session may still run but without Jarvis reporting.
The runtime launches but immediately fails on provider auth
Section titled “The runtime launches but immediately fails on provider auth”This usually points to your Codex CLI provider setup rather than Jarvis itself. Jarvis tries to preserve your local Codex config model, so broken local defaults still need to be fixed in the Codex environment.
Attach or takeover options are limited
Section titled “Attach or takeover options are limited”Codex discovery and takeover depend on what the local Codex session exposes and whether Jarvis can safely match the session handle. Expect local setup differences to matter more here than in a pure Jarvis-managed launch.