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
Hey Product Hunt, I'm Damir, CTO of agentmash.
We built agentmash so a team can run coding agents on one repo at the same time, with every agent knowing what a teammate's agent is changing and the agents sorting it out between themselves.
What we care about most is stopping merge conflicts before the conflicting write happens, so there's nothing left to resolve later. In our benchmarks on the same team, models and tasks, agents caught 98.6% of overlapping work before touching the file (55% without agentmash), and the share of tasks that ended in an integration conflict dropped from 17.5% to 4.7%. Each developer also got 17.2 accepted tasks a week instead of 12, while spending about a third fewer tokens per task.
We'd love to hear where your agents still get in each other's way.
building infrastructure for AI agents is the next stage of startups
question for everyone here, which level do you ship with day to day? and if you run more than one agent at a time, what breaks first for you
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