32b5178e-cea3-4795-8d0d-3aeece57910b

[giscus[bot]]

32b5178e-cea3-4795-8d0d-3aeece57910b

Learn how to use Git worktrees to run parallel AI coding agent sessions without file conflicts, enabling faster development with tools like Claude Code and OpenAI Codex.

https://www.ssw.com.au/rules/git-worktrees

[JeanThirion]

Worktrees are great - real solution to a real problem.
I'm just worried it also means junior will ship more and more untested, unchecked, unprofessional code more and more though...

[Aibono1225]

It's simple and worth using. Just need to pay attention to branch management and merge conflicts

[andrewwaltosssw]

Multiple branches can be confusing depending on the git strategy. Adding another layer of complexity is powerful and helps solve real problems so having a good understanding is key. This seems well suited to letting AI cook without stepping on it's own toes - great for AI power users.

[jerryluossw]

Worktrees are valuable, however we still need to focus on the followings:

• Logic Isolation: Ensure agents work on decoupled modules to avoid complex merge conflicts later.
• Resource Decoupling: Isolate shared resources like databases, network ports, and caches to prevent data corruption or runtime collisions.
• Dependency Management: Account for increased disk usage and ensure package lock files don't conflict during concurrent updates.
• API Quotas: Monitor rate limits for LLM and external services, as parallel agents will consume your API credits and throughput much faster.

[thom-wang]

I kind of felt insecure when letting AI Agents do tasks unsupervised. And the reviewing of PR would cost a lot of time.

[ClaraFang-SSW]

While this tool is designed for software development, I’m saving it to understand how AI sub-agents handle multi-tasking. It’s a great example of how AI can manage complex workflows, which might inspire how we automate financial processes in the future.

[yaqi-lyu]

It’s especially useful when we’re developing and don’t want to stash our work and switch to another branch to fix an urgent bug.

[ZenoWang1999]

Very insightful, I’d never considered combining AI agents with the Git tree to improve efficiency. However, my concern is that branches in Claude Code are isolated from each other, so they’re not aware of one another’s changes, which could make merging a real challenge.

[jimmidier]

It's something existed long ago but just shines in the AI ear. Great rule to bring it up

[bahjatalaadelssw]

This was a blast to edit!

[suiyangqiu]

And you killed it, it was awesome to watch! :D

[PennyWalker]

It was ridiculously fun to watch! Great job! 👏

[kulesy]

Git worktrees are amazing, it's great not to have to worry about cleaning my current working directory.

[ricksu978]

Git worktree is a secret ingredient for becoming a 10x developer.

After I started using git worktree, I realised that human code review had become the bottleneck.

To keep code quality high, I avoid working on more than two features at a time, because the human brain is basically a single-threaded processor.

[0xharkirat]

Git worktrees are awesome.
I also blogged this: https://www.harksingh.com/posts/git-worktrees-for-dummies

[thomas-sepanosian]

Cool feature, when I am ready to go full-vibes, I think this would be great, but for now I will be focusing on one thing at a time, as I don't think I have reached the right level for focusing at all branches at once just yet 🤖

[18-th]

Awesome rule and an awesome feature to use, I wish I had enough tokens to run agents in parallel 😄

[suiyangqiu]

Loving git worktrees, I already try to parallelise my agents by running them concurrently, and then having them address any merge conflicts or trying to manage them so that they never overlap, but Git worktrees solves a bunch of problems 🤩

[Ben0189]

Yes — I’d use Git worktrees for small, isolated features or low-risk tasks.
No — I’d avoid relying on worktrees for critical module changes, large cross-cutting refactors, or major feature releases. In those cases, I’d rather keep the work more controlled and focused on a single branch.

[RobJT-wq]

Worktrees sound like a great idea.

[joshbermanssw]

I think the biggest win is the point made about being able to work on one feature branch whilst testing another simultaneously with Git worktrees.

I've seen some experimentation around getting an agent to try tackle a complex issue in different methods on different worktrees, evaluate the success of each method, and then chose a solution path. I think processes like this are cool and could become more normal but for the moment are definitely in that experimentation or "fad" phase.

I still haven't found myself working on too much simultaneously to need to introduce Git worktrees into my everyday workflows.

[Username-must-be-unique]

Worktrees are great with AI when you use tools that allow you to easily work in parallel. I would use it on smaller isolated features that are at best completely isolated. This way you have an AI session per worktree and just chat along you work. Merging and the resulting merge conflicts could be handled with AI again but I ran into scenarios where it basically fixed it by removing the failing code instead of updating it.

[griffenedge]

Sounds interesting! Will have to play around with this

[jeoffreyfischer]

I'm not comfortable letting AI unsupervised: I'm happy to use worktrees for hotfixes, but not as a daily routine.

[TobyChurches]

Git Worktrees sound great! Perfect in the 'Age of AI' - Just as long as everyone is still checking the output of the AI Agents 🫣

[Hajir2005]

Git Worktrees are a game-changer. Whenever I need to knock out a quick bug fix and open a pull request, they're my go-to.

[sam-s-maher]

Haven't tried this, but would love to use this workflow for simpler issues to save on context switching whilst chipping away at larger issues/features.

[stephanfakossw]

Worktrees sound like a great idea in the AI age

[jimmy1992abc]

It sounds very useful to me. I need to give it a try and learn how to use it.

[MarcusIrmscherSSW]

Seems like a great way to maximise your workflow