One worktree per task: where a coding agent's work actually goes
This story is from 2026-09-29. It is preserved in the archive; the latest stories are on the live feed.
Run two coding agents at once in the same checkout and you have two writers on one tree. Both sessions look fine, both print a marker, and one has already overwritten the other's file. The fix is not a better prompt, it is a boundary: every task gets its own git worktree, and the results stay apart…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-09-29 13:03 · DEV Community — AI
One worktree per task: where a coding agent's work actually goes