You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your comparison page is the most honest one in this space, so this is a note about the category rather than a request for a listing.
Every tool on it, including Parallel Code, isolates first and merges later: worktrees, containers, separate branches. For genuinely separable work that's the right call and it costs nothing. But the collision doesn't go away, it moves to merge time. Both agents end up in src/auth/ on different branches and you find out at the end with two versions to reconcile.
There's a second approach that isn't represented on the page: agents share one working tree and claim path globs before they edit. If one asks for something inside a glob another already holds, the claim is refused right there and it picks different work. First writer wins, claims expire on a TTL so a crashed agent can't wedge a directory shut.
Not asking you to endorse anything. If you think isolation vs coordination is a real axis, it might deserve a row either way, even if the entry in it isn't yours or mine. Happy to go into the glob intersection part, that was harder than I expected (src/**/api has to match src/api, ** matching zero directories broke my first implementation).
I build befall.net, so obviously not a neutral party here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Your comparison page is the most honest one in this space, so this is a note about the category rather than a request for a listing.
Every tool on it, including Parallel Code, isolates first and merges later: worktrees, containers, separate branches. For genuinely separable work that's the right call and it costs nothing. But the collision doesn't go away, it moves to merge time. Both agents end up in
src/auth/on different branches and you find out at the end with two versions to reconcile.There's a second approach that isn't represented on the page: agents share one working tree and claim path globs before they edit. If one asks for something inside a glob another already holds, the claim is refused right there and it picks different work. First writer wins, claims expire on a TTL so a crashed agent can't wedge a directory shut.
Not asking you to endorse anything. If you think isolation vs coordination is a real axis, it might deserve a row either way, even if the entry in it isn't yours or mine. Happy to go into the glob intersection part, that was harder than I expected (
src/**/apihas to matchsrc/api,**matching zero directories broke my first implementation).I build befall.net, so obviously not a neutral party here.
All reactions