Nice! I have a very similar tool I built just for myself to use for CR at work.

I'll have to install this and check it out

Very cool. I've been using worktrees a lot recently at work, mostly reworking tools or CI jobs that try to manage branches into just using a worktree and cleaning up after yourself.

It's made a big difference in readability and cleanliness. I'll often use, eg, `mktemp -d` with a template argument that's relevant to the usage, then use the base name of the temporary directory as the worktree branch, followed by `git fetch <remote> <remote-branch>:<worktree-branch>`.

I've been thinking about using worktrees more for my general development, since I'm frequently working across multiple branches.

I had to google what a git worktree is and it's quite neat! Is this supported by GitHub or Azure DevOps?

How would you recommend using this for working with multiple agents? I'm thinking about scenarios where you might have several AI coding agents (or automated processes) that need to work on different branches simultaneously without stepping on each other's toes.

Any recommended workflow for coordinating multiple agents? For instance, handling naming conventions, cleanup strategies, or preventing race conditions when multiple agents try to create worktrees at the same time?

This seems like it could be really powerful for that use case, especially with the hook system for per-worktree setup.

There's also the simpler/smaller git-worktree-switcher (`wt`):

https://github.com/yankeexe/git-worktree-switcher

It does what it says on the tin.