Git Worktrees for AI Coding: Run Multiple Agents in Parallel

Last Tuesday I had Claude Code fixing a pagination bug in my API layer. While it worked, I sat there. Waiting. Watching it think. For eleven minutes. Meanwhile, three other tasks sat in my backlog: a Blazor component needed refactoring, a new endpoint needed tests, and the SCSS build pipeline had a caching issue. All independent. All blocked behind my single terminal. I thought: I have 5 monitors and a machine that could run a small country. Why am I running one agent at a time? Then I discovered that Claude Code shipped built-in worktree support, and everything changed. I went from sequential AI coding to running five agents in parallel, each on its own branch, none stepping on each other's files. My throughput didn't just double. It went up roughly 5x. Here's exactly how I set it up, the .NET-specific gotchas I hit, and why I think worktrees are the single biggest productivity unlock for AI-assisted development right now. Table of Contents What Are Git Worktrees (