Using git worktrees to isolate concurrent AI agent sessions and prevent silent commit loss

Short summary

When AI agents share a single git working tree, concurrent branch switches can silently orphan commits and lose in-progress work. The solution is git worktree add, which gives each agent session its own HEAD, index, and working files while sharing the object database — no full re-clone needed. The author's orchestration tooling already supports an explicit isolation: 'worktree' option for exactly this scenario.

• •Shared git working trees cause silent commit loss when agents switch branches concurrently
• •git worktree gives each session isolated HEAD and index while sharing the object store
• •Agent orchestration tools should default to worktree isolation for parallel file-mutating tasks

Generated with AI, which can make mistakes.