Long-form articles about git worktree: what GitHub sees when you push from one, why the Claude Code team bet on worktrees, the manager landscape in 2026, and the honest tradeoffs you should hear before you wire them into your team workflow.
git worktree is not magic — it is a tool with sharp tradeoffs. This is the version of the worktree pitch you would get from a senior engineer over a coffee, not from a marketing page. With three reasons to skip it.
Read the article →git worktree is built into Git itself — no extension, no plugin. The command shipped in Git 2.5 on July 27, 2015 as the modern replacement for git-new-workdir. Here is the full timeline of every feature added since.
Read the article →Plain git worktree is fine for two or three branches. Past five, you need a manager. We installed eight of them — VS Code extensions, JetBrains plugins, CLIs, TUIs — and ranked them by what survived a real day of parallel work.
Read the article →Boris Cherny — creator of Claude Code — has talked publicly about why he wired worktrees into the agent runtime. Here is what he said, with the timestamps, the direct quotes, and what it means for your workflow.
Read the article →GitHub treats every worktree push exactly like a regular branch push — the server has no idea you are using worktrees locally. We pushed from three worktrees, watched the GitHub UI, and inspected the receive-pack logs.
Read the article →