Worktrees: Parallelism Without Coordination

Say you're refactoring the billing module and also fixing an unrelated UI bug. Those two jobs have nothing to say to each other, they just need to not overwrite each other's files. That's not a job for agent teams (several Claude sessions coordinating on one task). It's a job for something much simpler: git worktrees.

Separate checkouts, separate sessions, edits that cannot collide. Name each session and resume it independently. Each workstream keeps its own persistent context, like a branch you can walk back into.

It is the low-tech version of parallelism, and each worktree still runs one agent at a time, so it doesn't carry agent teams' roughly 7x token overhead.

The test is whether the tasks need to exchange information. If they do, that's a team. If they just need to not step on each other, that's a worktree.