Interactive Codex to File-Based Fallback When to use Use this when: - the user prefers tmux + interactive Codex first - you are executing a plan-approved GitHub issue in or a similar repo - interactive Codex repeatedly fails to make write-phase progress - the repo or parent checkout may already be dirty, so you need worktree-safe verification after the run Why this exists A recurring failure mode is that interactive Codex works well for planning and approval-safe prep, but can fail during implementation in two different ways: - immediate upstream errors such as / - long context-gathering sess…