One Agent. One Branch. One Worktree.
The simplest path to peaceful agentic coding.
Here’s a short and sweet post to help you avoid the thing I’ve been screwing up for the last, I don’t know, five hundred years?
Git doesn’t care about the chat window. Git cares about the working directory. If one agent switches branches, stages files, rebases, or merges, the other agent is standing in the same room while the furniture moves.
That is how you end up with one chat suddenly “mysteriously” on a different branch, or saying something like, “I’m only going to commit these changes without touching these other unrelated changes.”
Use Git worktrees.
I put together a short guide that explains the pattern, shows the basic setup, and includes a copy/paste prompt you can hand to an agent so it updates your AGENTS.md or CLAUDE.md for you.
The goal is simple: make parallel agent work safer without turning your repo into a branch circus.
The Guide is Here: Git Worktrees for Parallel Agents
Note: I would have spent more time writing this post, but the new Dungeon Crawler Carl is out. That being said, you should still do the pay-to-subscribe thing even if you get nothing extra from it
Thumbnails that didn’t make the cut
Why you gotta call me out like this after two days cleaning up my “own goal?” 🤦🏻♀️🤡
Missing Princess Donut on the thumbnails ;-)