codex-bridge

# Codex Bridge

Call OpenAI's Codex CLI to get responses, reviews, or perform tasks.

## When to Use

Activate when user says:
- "Ask Codex...", "Have Codex...", "Let Codex..."
- "Get GPT's opinion on...", "What does OpenAI think..."
- "Get a second opinion on..."
- "Have Codex review...", "Let Codex fix/refactor/implement..."
- "Compare Claude vs Codex...", "Run this through Codex..."

## Quick Reference

| Flag | When | Example |
|------|------|---------|
| _(none)_ | Opinions, reviews, questions, analysis | `node "$CODEX_BRIDGE" "Review this code" --working-dir "<project>"` |
| `--full-auto` | Fix, refactor, implement, update files | `node "$CODEX_BRIDGE" "Fix errors" --full-auto --working-dir "<project>"` |
| `--model MODEL` | Override model (default: Codex default) | `node "$CODEX_BRIDGE" "Explain" --model gpt-4o --working-dir "<project>"` |
| `--json` | Bridge outputs raw JSON events (debugging) | `node "$CODEX_BRIDGE" "Analyze" --json --working-dir "<project>"` |
| `--timeout MS` | Override 20-minute default timeout | `node "$CODEX_BRIDGE" "Long task" --timeout 2400000 --working-dir "<project>"` |

## Setup

```bash
# Resolve bridge path (one command):
CODEX_BRIDGE=$(ls -1 "$HOME/.claude/plugins/cache/saurun-marketplace/saurun/"*/skills/codex-bridge/codex-bridge.mjs 2>/dev/null | head -1)
```

**CRITICAL:** Always pass `--working-dir` with the project directory. Without it, Codex runs in its install location and can't access project files.

## Decision Logic

| Mode | When |
|------|------|
| Read-only _(no flags)_ | Opinion, explanation, review, comparison, questions |
| `--full-auto` | Modify files. Trigger words: "fix", "refactor", "implement", "update", "change" |

## Handling File Reviews

When user wants Codex to review a file:
1. Read the file content with the Read tool
2. Include content in the prompt to Codex

```bash
node "$CODEX_BRIDGE" "Review this document for feasibility, risks, and suggestions:

---
[FILE CONTENT HERE]
---" --working-dir "/path