# Git worktree

Hacker Approved page: https://hackerapproved.com/p/git-worktrees/

46 people recommended Git worktree in Hacker News comments, 10 had mixed feelings and 19 criticized it, November 2025 to October 2026. It was recommended in 10 of 12 months, in 35 threads. It meets the Hacker Approved badge rule.

**Verdict:** Lets you check out several branches of one repo in separate folders, sharing history without full clones. Caveat: a branch can't be open in two worktrees at once.

Summary written by Claude from 54 comments.

## Why people recommend it

- Runs parallel agents in separate folders (4 comments in the sample): "You give each agent a git worktree and if you want to check, you checkout their branch." ([source](https://news.ycombinator.com/item?id=46524130)) "With git worktrees you can you have your agents working on literally different folders" ([source](https://news.ycombinator.com/item?id=46749436)) "one git worktree per Claude session specifically to avoid this issue" ([source](https://news.ycombinator.com/item?id=46908615))
- Less disk use than clones (4 comments in the sample): "They are the right abstraction for people that do not want to relocate terabytes of their existing data" ([source](https://news.ycombinator.com/item?id=49661842)) "They have separate reflogs, you'd still get separate directories, but less duplication." ([source](https://news.ycombinator.com/item?id=46847763)) "It's very useful when your repos are a significant fraction of disk space." ([source](https://news.ycombinator.com/item?id=46194649))
- Shared git state, no push-pull (4 comments in the sample): "It makes coordination easier. For eg if you want to fetch and pull master, you only have to do that once." ([source](https://news.ycombinator.com/item?id=49414309)) "git 'knows' about all the associated branches, so you don't have to deal with pushing/pulling" ([source](https://news.ycombinator.com/item?id=49414637)) "I don't have to think about local vs upstream there's just one place to push" ([source](https://news.ycombinator.com/item?id=48823713))
- Clean isolated working copies (3 comments in the sample): "You get other things like mutual exclusion, a clean baseline regardless of whats in the main directory" ([source](https://news.ycombinator.com/item?id=49658997)) "One thing I like about worktrees is that you get a clean copy" ([source](https://news.ycombinator.com/item?id=49657278)) "worktrees provide a safe place to actually perform that work" ([source](https://news.ycombinator.com/item?id=47574025))

## What people warn about

- Breaks environments, dependencies, submodules (5 comments in the sample): "Sadly worktrees do some stuff with the git folder that's made one development environment we inherited incompatible." ([source](https://news.ycombinator.com/item?id=48377996)) "Worktrees have a pitfall IMO that they don’t allow you to test changes in a running local env" ([source](https://news.ycombinator.com/item?id=47716150)) "still leaves you reinstalling node_modules per tree and fighting over a dev server port" ([source](https://news.ycombinator.com/item?id=48355104))
- Clunky, annoying to use (4 comments in the sample): "This restriction of git worktrees is annoying but I just learned one simple rule to follow" ([source](https://news.ycombinator.com/item?id=46194289)) "an awesome productivity multiplier, but with a terrible UX" ([source](https://news.ycombinator.com/item?id=46236773)) "orchestrating multiple agents with native tmux and git worktree does feel cumbersome" ([source](https://news.ycombinator.com/item?id=47430635))
- Poor fit for multiple repos (3 comments in the sample): "agents increasingly work across multiple repos, and that's where (my approach to) worktrees broke down" ([source](https://news.ycombinator.com/item?id=49415005)) "Doesn't work. You need to mount both the worktree and the repo which defeats the point" ([source](https://news.ycombinator.com/item?id=48345536)) "git worktrees are the right Git abstraction and the wrong abstraction for this problem" ([source](https://news.ycombinator.com/item?id=48025040))

## Other version control features people recommend

- [git rebase](https://hackerapproved.com/p/git-rebase/): 21 recommend, 2 mixed, 11 criticize
- [git rerere](https://hackerapproved.com/p/git-rerere/): 16 recommend, 2 mixed, 4 criticize
- [git add -p](https://hackerapproved.com/p/git-add-p/): 11 recommend, 2 mixed, 4 criticize
- [Git notes](https://hackerapproved.com/p/git-notes/): 10 recommend, 1 mixed, 2 criticize

## The badge

A product earns the Hacker Approved badge when at least 10 people recommend it, recommenders outnumber critics at least 2 to 1 (mixed feelings count toward neither side), it was recommended in at least 4 of the 12 months and in at least 5 different threads, and no single thread supplies more than half of the people who recommend it. Health and money products are never badged.

## Cite as

Hacker Approved, "Git worktree", https://hackerapproved.com/p/git-worktrees/ (46 recommend, 10 mixed, 19 criticize; Hacker News comments, November 2025 to October 2026).

Counts updated 2 Nov 2026, with data through October 31, 2026.