Git worktree isolation for multi-agent coding
Branches alone do not isolate file state. Phasr creates disposable worktrees per agent task so code changes never collide before review.
Why branches are not enough
Branches point to commits. They do not provide separate working directories for concurrent agents.
Worktree lifecycle in Phasr
Create isolated worktree, run task, review diff, merge approved branch, and clean up the workspace.
Merge strategy checklist
- Use branch-per-task naming for traceability.
- Require tests before review approval.
- Merge only approved branches into target branch.
- Remove completed worktrees to keep environments clean.