collaborating-with-codex

# Collaborating with Codex Use Codex CLI as an independent collaborator while the primary agent remains responsible for verification, synthesis, and final user-facing decisions. The bridge script (`scripts/codex_bridge.py`) wraps `codex exec` in JSON mode, streams progress to stderr, returns structured JSON, and manages multi-turn continuity via `SESSION_ID`. Commands below write `<skill_dir>` for the absolute path of the directory containing this SKILL.md. Your harness usually reports that path when it loads the skill. If it does not, use this SKILL.md's own location. Substitute it before running, for example `~/.claude/skills/collaborating-with-codex`. In Claude Code, run bridge calls in the background by default for non-trivial tasks: ```text Bash tool call: command: python3 <skill_dir>/scripts/codex_bridge.py --cd "/project" --PROMPT "Analyze auth flow in src/auth/" run_in_background: true ``` `run_in_background` is a host tool parameter, not a shell argument. Use the host's task-output view to monitor timestamped stderr progress, commands Codex ran, response previews, stalls, and completion. ## Safety model Default to read-only delegation: - `--sandbox read-only` - default; use for review, diagnosis, research, and second opinions. - `--sandbox workspace-write` - use only after write access is appropriate; prefer an isolated worktree under `/tmp`. - `--sandbox danger-full-access` - use only in an externally sandboxed environment. - `--bypass-sandbox` - forwar...