Skip to content

v1.5.1 — Auto-discover a system codex (macOS XProtect fix)

Choose a tag to compare

View all tags
@AmirShayegh AmirShayegh released this 02 Jul 07:26
v1.5.1
4e52ceb

Out-of-box Codex now works on macOS.

The fix

The @openai/codex-sdk spawns its own bundled codex binary — never the one on your PATH — and macOS XProtect false-positively quarantines that bundled copy, so on a fresh install every Codex review failed with PROVIDER_UNAVAILABLE (silently degrading to Gemini in failover/deliberate modes). The only way out was manually setting codex_path.

The bridge now auto-discovers a working system codex and retries. When a review fails PROVIDER_UNAVAILABLE and no explicit codex_path/CODEX_PATH is set, it scans your PATH and the usual install locations (~/.local/bin, /opt/homebrew/bin, /usr/local/bin), verifies the candidate actually runs (--version probe — a quarantined file can exist yet be killed on spawn), swaps it in, logs the substitution on stderr, and retries. Concurrent reviews share a single discovery. An explicit codex_path or CODEX_PATH always wins and disables discovery entirely.

Most macOS users already have a properly-notarized codex from OpenAI's standalone installer — the bridge now finds it instead of making you diagnose the quarantine maze.

Docs

  • codex_path and the auto-discovery behavior are now documented in the README (config reference + troubleshooting).

Verified live against the real failure path; 807 tests passing.

Assets 2
Loading