Skip to main content
Codex does not have a cross-platform lifecycle-hook mechanism, so the integration uses two pieces: the MCP server (scan tools) and AGENTS.md guidance (when to use them). There is no deterministic stop-hook enforcement for Codex — if you need that guarantee, pair Codex with ZeroPath PR scanning so the diff is caught at review time.

What the installer writes

Manual MCP setup

Append to ~/.codex/config.toml:

Notes

  • If your Codex deployment restricts MCP servers (managed/cloud config or an mcp_servers allowlist), zeropath must be included in that allowlist; cloud-managed configuration takes precedence over ~/.codex/config.toml.
  • The zeropath CLI is installed at ~/.zeropath/bin/zeropath, so Codex can also scan from the shell: ~/.zeropath/bin/zeropath scan-code --diff --base-ref HEAD --caller agent --json. The AGENTS.md guidance mentions this as the fallback when MCP is unavailable.

Verify

Run /mcp in the Codex TUI and confirm zeropath is listed, or:
Then ask Codex to “scan my uncommitted changes with ZeroPath” — it should call asyncCodeScans.submit, poll asyncCodeScans.status, and report the asyncCodeScans.results findings.