Git worktrees have been around since 2015, but they've made a resurgence. 🔥 @cassidoo explains what they are and why AI-era parallel work makes them feel essential. 👇 github.blog/ai-and-ml/github…
Screenshot of the GitHub Copilot app user interface, showing a drop-down menu for a new worktree.

ALT Screenshot of the GitHub Copilot app user interface, showing a drop-down menu for a new worktree.

Jul 5, 2026 · 6:35 PM UTC

32
42
436
85,582
Sort replies: Relevant Recent Liked
Replying to @github @cassidoo
Yeah, really useful with AI coding agents, i wish vscode would handle them better tho... 😀
1
771
Replying to @github @cassidoo
git worktrees saving my parallel workflow life rn, anyone else?
1
1
343
Replying to @github @cassidoo
3 worktrees help until every agent edits the same migration file
117
Replying to @github @cassidoo
worktrees having a moment thanks to agents. would love a GitHub guest on techimpact.tv @techimpactTV

TECH IMPACT - National TV Series with Evan Kirstel

Understanding the disruption of new technologies like Blockchain, AI, Machine Learning, and Big Data is crucial for business survival.

techimpact.tv
461
Replying to @github @cassidoo
Worktrees are the only thing saving my local repo from Copilot's parallel chaos 🙃
3
294
Replying to @github @cassidoo
underrated
1
167
Replying to @github @cassidoo
Worktrees went from “nice Git trick” to almost mandatory once AI agents started working in parallel. Separate workspace, same repo, less branch chaos — it fits the way dev work is moving now.
1
463
Replying to @github @cassidoo
Been using worktrees since 2018 so my AI agent doesn't wipe my uncommitted stashes during parallel runs. 🤷
1
171
Replying to @github @cassidoo
generation speed helps, but if review is serial, the bottleneck stays the same. faster generation ≠ faster shipping.
1
165
Replying to @github @cassidoo
when parallel agents both touch the same file across worktrees, does the merge step actually get cleaner or just... differently messy?
1
1
141
Replying to @github @cassidoo
Git worktrees are becoming a must-have for Al-assisted development. Parallel workflows just make more sense now.👀
2
Replying to @github @cassidoo
Worktrees 最被低估的点：Git 切换分支会把索引和暂存区全部冲掉，AI 助手的历史上下文也跟着丢。用 worktree 每个分支开独立目录，Cursor 每个窗口绑定一个分支，AI 不会混淆你改的是哪个版。
64
Replying to @github @cassidoo
Worktrees feel newly important because agent work is naturally parallel: one branch for exploration, one for implementation, one for review. The primitive was old, but the workflow pressure is new.
1
Replying to @github @cassidoo
AI 시대의 worktree는 단순한 Git 팁보다 작업 격리 장치에 가깝네요. 여러 에이전트가 동시에 고칠수록 브랜치보다 작업 공간 분리가 더 중요해지는 것 같습니다.
65
Replying to @github @cassidoo
Worktrees finally make sense in the agent era.
22
Replying to @github @cassidoo
Curious how teams are naming and cleaning up AI-created worktrees. The feature is powerful, but without a simple convention it can turn into workspace clutter fast.
1
287
Replying to @github @cassidoo
The underrated part is safety. Let an agent explore a fix, spike a refactor, or test an approach in its own worktree without dirtying your main local repo. That alone saves a lot of cleanup.
405
Replying to @github @cassidoo
I've been meaning to try worktrees, this might be the nudge
129
Replying to @github @cassidoo
就是每次拉一个 worktrees 依赖都要重新安装一次，对于还在使用 npm 下载的项目，内存占用又多了😂
56
Replying to @github @cassidoo
Been using worktrees for years, but yeah—Cursor and Claude Code running parallel agents completely breaks regular git branches. 🌿
300
Replying to @github @cassidoo
Come on, worktrees were a niche Git trick until AI turned every repo into a tiny coworking space.
155
Replying to @github @cassidoo
多分支并行时确实省很多来回切换
138
Replying to @github @cassidoo
Worktrees are the perfect companion to local LLM swarms. You need clean, isolated environments for every experiment to avoid state pollution. Spinning up a new worktree for specific agent tests—without re-cloning—is a massive productivity multiplier for local dev loops.
57
Replying to @github @cassidoo
new slop feature
69
Replying to @github @cassidoo
running 4 worktrees for parallel claude code sessions now, cant go back to one branch
150