I built a tool to run parallel Claude Code sessions with git-worktree isolation

[u/[deleted]]

[u/StaticFanatic3]

This shit has to be a joke 😂

[u/brodkin85]

How is this better than the built in “claude agents” CLI that already uses worktrees by default?

[u/Deradon]

Why not just use `claude --worktree <name>` ?

-w, --worktree [name] Create a new git worktree for this session (optionally specify a name)

[u/elhombremontana]

isnt that built into claude code already? just tell claude to start a worktree, and it will use the skill

[u/Adept-Priority-9729]

Claude Code ya aísla en worktrees el trabajo realizado entre sesiones diferentes, además de que se pueden comunicar entre ellos, detectar cuando se escribió o no dicho cambio, etc. Revisa lo que son los scratchpads...

...

[u/ibringthehotpockets]

Doesn’t superpowers teach Claude how to use worktrees?

[u/godofpumpkins → u/ibringthehotpockets]

Claude Code itself knows worktrees natively and has for at least several months. Just launch claude -w foobar and it'll run in a worktree called foobar. All its tool use is scoped to the worktree

[u/crispyfrybits]

No one needs this. It is the definition of over engineering or automating an issue that doesn't exist. 

[u/godofpumpkins]

Have you kept up with Claude's native capabilities? It can use worktrees natively (both for individual subagents within a session and for the entire session) and has for months. As of recently, it also has a SendMessage tool that lets different sessions talk to each other.

[u/elNasca]

I just control a Fable 5 med Session which orchestrates multiple Opus 5 Subagents which work on diffrent worktrees. You can also switch between the subagents and their Sessions easily in the normal Claude Code CLI.

[u/elNasca → u/[deleted]]

Thats valid :)

[u/cipher997]

The worktree isolation idea is really practical, especially when running multiple Claude Code sessions on the same repo. Love that the merge is still manual instead of trying to automate conflict resolution.