Git Worktrees

What's inside

Every Claude turn takes minutes. Most engineers run one Claude and wait. Boris runs five — on the same repo, each with its own branch, each in its own folder. The Git primitive that makes this possible is `git worktree`: a second working directory of the same repo, sharing the underlying `.git` data but with independent working files.

This guide gives you the exact commands to set up 5 worktrees (named after real features — auth, billing, migration, docs, tests), the Ghostty terminal config that turns the bell character into a silent per-tab visual notification, and the Claude Code Stop hook that fires every time a Claude finishes a turn so you don't have to babysit them.

Includes the cleanup pattern (use `git worktree remove`, not `rm -rf`) and 3 specific gotchas: Git enforces one worktree per branch, node_modules don't follow worktrees so you'll `npm install` per folder, and `.env` files need to be copied in manually since they're gitignored.