Using Codex Collaboration · jewel591 bundle Use proactively whenever the work involves substantial code changes (multi-file, core logic, architecture), a freshly written execution plan, a sticky bug that resists single-perspective diagnosis, or a non-obvious design decision that needs adversarial challenge — establishes when and how to bring Codex in as a reviewer (not as an executor). The ONLY channel is the persistent Codex pane reached via tmux — this holds even when Claude's own session is NOT running inside tmux (drive the tmux server externally). Direct `codex` CLI invocation (codex exec etc.) is FORBIDDEN unless the user explicitly requests it. Covers the bundled codex-pane.sh helper (find-or-launch, send, wait, capture, cleanup), the predefined collaboration scenarios (change review, plan review, adversarial challenge, bug rescue), and the review⇄fix consensus loop that runs until a clean verdict.
