hey, i m damir, cto at agentmash.
when we started running claude code and codex on the same repo, the thing that kept biting us was two agents quietly editing the same file and one of them finding out at merge time. anthropic s own docs basically tell you to split file ownership by hand for agent teams, which works fine until a task touches the shared types or the router and you re back to babysitting
we went the other way and let each agent see what the others are changing so they can work it out between themselves. in our benchmarks they caught 98.6% of overlapping work before touching the file, compared to 55% without agentmash, but i m pretty sure there are setups where splitting by hand is still the saner call
the easiest way we've found to explain who agentmash is for is splitting ai coding into three levels. level 1 is ai helping you write code (cursor, antigravity), level 2 is where you don't write it but still read and run it (claude code, codex), and level 3 is where you never see the code at all (lovable, bolt). agentmash is for level 2, the moment you start running several agents on one repo, so each agent sees which files the others are changing and gets a warning before it touches one of them
Congrats!
@suleimenov thank you legend
The claim-before-you-edit part is what sells this for me — most setups only tell you at merge time, when it's already a mess. When I run two agents on the same repo, the painful case is a shared type changing under the other agent, so the name-level warnings for JS/TS sound right. Curious what happens to a claim if an agent dies mid-task or just wanders off — does it expire on its own, or does a teammate have to clear it?
congrats on the launch! 🚀🚀
mine are in separate worktrees, one branch each, so two agents never write the same file at the same moment. the collision just shows up later when the branches meet, which is worse because nobody is watching by then.
does it see across branches or only inside one checkout??