Launched this week
AVP
Open source alternative to Git for AI coding agents
87 followers
Open source alternative to Git for AI coding agents
87 followers
Worktrees isolate your agents. AVP integrates them: every change proven on the exact head of main before it lands.
Hey Product Hunt !
I'm Moss'Ab, co-founder of Murmell.
Earlier this month, Anthropic shared that it had moved its monorepo off Git after its agents took it from about 2,500 merged changes a day to more than 30,000. Their system, Scion, is internal. On Hacker News, the top complaint was simple: nobody outside Anthropic can use it.
We had hit the same wall at a much smaller scale. Murmell is currently two people and a lot of coding agents from different providers on one monorepo, and the agents had stopped being the slow part. Every change waited for a pull request and a CI run, rebased on a main that had moved, and two agents on the same file ended in a conflict someone had to settle by hand.
So we built AVP (Agent Versionning Protocol), and it's open source.
An agent opens a task, writes, and lands it. Every landing is proven on the exact head of main in seconds; if the line moved, the task is replayed on it and proven again. Every landing is still an ordinary Git commit, so GitHub and your deploys don't change.
On our repo, CI runs for pull requests went from 104 a day to 4. In our benchmark, with 6 to 8 Claude Code agents on one repo, main went red under Git and Jujutsu and tasks silently went missing.
With AVP, main stayed green and nothing was lost, in every run so far.
Method and numbers: avp.murmell.com
One binary: `avp up` in any Git checkout connects Claude Code and Codex.
The Git side is there to make the transition easy for teams on Git today.
At Murmell now we don't use Git ourselves anymore. We work through AVP, we're slowly moving to our own client, and GitHub only stays as a fallback that stores the code. I think most teams will make the same move in the coming years.
I truly believe AI will reshape the tools we use every day. MCP changed how agents interact with APIs. Now it’s time for AVP to replace Git.
Git was built for humans. AVP is built for AI agents.
@moss_ab_mirande_ney What happens to the rest of the queue when one fails? Also curious how it differs from a merge queue on GitHub.
Proving every landing on the exact head of main, in seconds, is a strong answer to the usual worktree pain. I am curious how AVP handles the case where two agents touch the same lines at almost the same time: does the later task replay cleanly most of the time, or does it usually need human help to resolve? Keeping each landing as an ordinary Git commit also seems like a smart way to lower the cost of trying it.
What does proven mean exactly, the test suite passing on the new head? We had an agent decide one of our discount rules was backwards, flip it and write two tests for its own version, so the whole suite stayed green. Does AVP know when the same agent wrote the change and the test that proves it?