Start Parallel Codex Work Safely With a Git Worktree

The decision behind the technique

Worktrees let concurrent tasks share object history without sharing a mutable checkout. They are ideal when the tasks can merge independently.

Name the base, branch and ownership boundary before the first edit.

A practical step-by-step workflow

Use this sequence as a default, then tighten or expand it only when the evidence changes.

• Choose the exact base branch or commit
• Create a named worktree and task branch
• Run setup and a baseline check inside it
• Commit and review before integrating

Failure boundary and finish line

Uncommitted changes in the original checkout are not automatically present in the new worktree.

Finish when the next action, owner, evidence and stop condition are all explicit.