Git worktree

“things get wonky once you consider processes and environments variables”

“They are the right abstraction for people that do not want to relocate terabytes of their existing data”

“You get other things like mutual exclusion, a clean baseline regardless of whats in the main directory”

“One thing I like about worktrees is that you get a clean copy”

“Worktrees are significantly faster to use and checkout than clones.”

“The main issue with worktrees is that you can't have the same branch opened in multiple worktrees which makes many things harder than the ought…”

“agents increasingly work across multiple repos, and that's where (my approach to) worktrees broke down”

“git 'knows' about all the associated branches, so you don't have to deal with pushing/pulling”

“It makes coordination easier. For eg if you want to fetch and pull master, you only have to do that once.”

“The big advantage of using worktrees is the shared git state”

“you have go through the annoyance of giving the local branches different names”

“Worktrees force you distinguish the "main" repo from the swarm of checkouts”

“I don't have to think about local vs upstream there's just one place to push”

“worktrees are cool, i find i need some bash aliases to like them as a human”

“To me that is exactly what mounting a branch would be. I use them a fair amount.”

“Worktrees don’t support git submodules and it’s killing me in my monorepo”

“Sadly worktrees do some stuff with the git folder that's made one development environment we inherited incompatible.”

“still leaves you reinstalling node_modules per tree and fighting over a dev server port”

“For most practical uses of same repo checking out different branches locally, worktrees are better.”

“Doesn't work. You need to mount both the worktree and the repo which defeats the point”

“git worktrees are the right Git abstraction and the wrong abstraction for this problem”

“Exactly, worktrees solve this problem, every "agentic IDE" uses them”

“Worktrees have a pitfall IMO that they don’t allow you to test changes in a running local env”

“git worktree is a pretty standard solution, straightforward to leverage in any IDE or AI harness worth its salt”

“worktrees provide a safe place to actually perform that work”

“orchestrating multiple agents with native tmux and git worktree does feel cumbersome”

“Agreed here’s a blog I read where I found out about Claude’s support”

“Git worktrees are a simple way to work on the same codebase in parallel”

“git worktrees in a VM are much faster over spinning up new containers”

“Check out the “brainstorming” skill and the “git worktrees” skill.”

“one git worktree per Claude session specifically to avoid this issue”

“They have separate reflogs, you'd still get separate directories, but less duplication.”

“With git worktrees you can you have your agents working on literally different folders”

“You give each agent a git worktree and if you want to check, you checkout their branch.”

“git worktrees is a semi-recent addition that may be nicer than your git archive setup”

“an awesome productivity multiplier, but with a terrible UX”

“git worktree' is adequate. Granted, self-hosted agents is a niche use case, but IMO…”

“It's very useful when your repos are a significant fraction of disk space.”

“This restriction of git worktrees is annoying but I just learned one simple rule to follow”

“if you need to do a "quick bug-fix and get back into the main thing" worktrees are really nice”