Codex Issue Waves

Run GitHub issues through codex exec in isolated worktrees, then shepherd the resulting PRs through review and merge. Four phases: dispatch → monitor → review wave → correction wave.

Orchestration model. Claude is the PO / engineering manager. Codex is the worker — implementer per worktree (parallel across worktrees), reviewer per worktree (parallel across worktrees, sequential after the implementer finishes its worktree), and corrector when fixes are needed. Claude never edits source files, never reads diffs for judgment, never runs in-place fixes. Every code touch — build, review, correction — goes through a codex dispatch. See invoking-codex-exec "Codex roles" and "Orchestrator boundaries" for the full rule.

When to use

Triggered by requests like:

• "Spawn codex on issues #A, #B, #C"
• "Have codex handle these issues in parallel"
• "Manage the PRs" / "process feedback" after such a batch
• "Get them merged"

Not for: single-issue work (implement directly or use /pr), or batches where codex CLI isn't available on the host.

Pre-dispatch: conflict triage

Before creating any worktree, surface conflicts between issues in the batch. Don't just fan out blindly.