Git Worktrees Explained — Run Multiple AI Agents in Parallel (Claude Code Tutorial)

Most developers run Claude Code sessions sequentially — one task finishes, then the next one starts. That's a tool constraint, not a task constraint. When your tasks are independent, your agents should run in parallel. Git worktrees solve this. One repo, multiple isolated working directories, each on its own branch — each with its own Claude Code session running simultaneously. Zero conflicts. Standard git merge when done. This video covers everything: → Git worktrees explained from scratch (no prior knowledge needed) → Why two Claude Code sessions in one directory breaks → Manual setup: git worktree add, list, remove → Claude Code's built-in --worktree flag (the fast path) → Live demo: two agents, one Solana repo, running simultaneously → Advanced: agent-vs-agent comparison, --tmux flag, CLAUDE.md scoping → .worktreeinclude for copying .env files into new worktrees → 5 gotchas: shared .env, migrations, dependencies, cleanup Key commands: git worktree add git worktree list git worktree remove claude --worktree ← built-in Claude Code flag claude --worktree --tmux ← launches in its own tmux session