onpath × C Codex integration

Monitor Codex,
locally.

Wrap codex with onpath and monitor each session you run through it. Detect stuck loops, get a recovery prompt, and let Codex inspect local findings over read-only MCP.

Get started Read the docs
Works with the Codex CLI from OpenAI · stable
zsh — Codex command walkthrough
# one prefix — Codex runs exactly as normal
$ onpath run -- codex exec "fix the failing test"
↳ illustrative session · local recording active
# onpath watches the stream and flags stuck loops
⚠ repeated-failure-output · 4× · f1a4·c0 · recovery prompt ready
# configure and verify read-only MCP
$ onpath install codex --workspace .
$ codex mcp get onpath
What onpath catches in Codex

Repeated failures

Same test, same error, on repeat — caught by failure signature.

warn

Edit loops

The same path edited repeatedly without a successful command.

warn

No progress & time budget

Configured session budgets crossed without successful progress.

warn
How onpath works with Codex

Three steps. Nothing changes about how Codex runs.

onpath sits between you and the codex CLI — observing, recording, and reporting without altering the agent's behavior.

STEP 01

Wrap the command

Prefix any Codex invocation. onpath spawns it as a child process and watches the stream.

$ onpath run -- codex
STEP 02

Detect locally

Commands, exits, and edits stream to local SQLite. Detectors flag stuck patterns in real time.

→ .onpath/events.sqlite
STEP 03

Feed back over MCP

Install the read-only MCP server so Codex can read its own findings and recovery prompt.

$ onpath install codex --workspace .
Read-only MCP

Codex can inspect local evidence — and cannot act through onpath.

The onpath MCP server exposes discovered projects, recent sessions, findings, reports, Work summaries, and deterministic recovery prompts. It has no tool that runs commands, edits files, or changes policy.

Active findingsOpen detections with severity, signature, and repeat count.
Recovery promptA concrete next step Codex can act on to break the loop.
Read-only by designNo write surface — onpath only answers questions about the session.
Codex · MCP
# configure and verify the server
$ onpath install codex --workspace .
$ codex mcp get onpath
# implemented read-only tools
onpath_list_findings
onpath_get_recovery_prompt
Compatibility

Codex support at a glance.

onpath wraps the codex CLI on macOS and Linux. Everything runs locally — no agent API keys are shared with onpath.

Invocationonpath run -- codex
Event capturecommands · exits · edits · timings
MCP serveronpath install codex --workspace .
Data handlinglocal SQLite · sync opt-in
Statusstable
More integrations

onpath works with your whole agent stack.

Use the same prefix and the same dashboard across every coding agent on your team.

Cl Claude Codeonpath run -- claude Cu Cursor Agentonpath run -- cursor-agent O OpenCodeonpath run -- opencode

Put Codex on path.

Local-first. Open-core. Two minutes to install and one prefix to start.

$onpath run -- codex
Get startedRead the docs