Claude Code Loves Worktrees. Your Infrastructure Doesn't.

If you use Claude Code daily, you've seen it: you ask the agent to implement a feature and, before you can blink, it's already spinning up a worktree with three parallel subagents — each one confidently working in isolation, each one about to crash into the same wall. The first time it happened to me, I was impressed. Three subagents, three worktrees, three features in parallel. It felt like the future. Then the logs started. DATABASE_URL is not defined . EADDRINUSE :4001 . A migration that corrupted a shared database. All three agents failing for reasons that had nothing to do with the code they wrote. That's when I realized: Claude Code's instinct to parallelize with worktrees is powerful, but it assumes your project is just code. Most projects aren't. The Promise claude --worktree is one of the best features in Claude Code. Each agent gets an isolated copy of the repo. No merge conflicts. No "who broke main?" No stepping on each other's code. For pure code changes, it's perfect. Cre