The Worktree + Agent Pattern

Here's the problem: you want two AI agents working on the same codebase at the same time. But they can't both edit the same files in the same directory without creating chaos. If Agent A is modifying src/lib/auth.ts while Agent B is also modifying it, somebody's changes get overwritten.

The solution is a pattern that experienced developers have used for years with human teammates: git worktrees. Each agent gets its own isolated copy of the codebase, works on its own branch, and merges via pull request. Clean, conflict-free, reviewable.

What Are Git Worktrees?

A git worktree is a second (or third, or fourth) working directory linked to the same repository. Each worktree can be on a different branch, and they all share the same git history.

# Your main working direc