Built to understand conflicts and resolve them efficiently. Each result links to its workload and measurements.
Call-graph accuracy vs graphify
More of the real dependency graph, with higher verified precision in 10 of 12 repositories too. We tested 12 open-source repositories across 9 languages.
Conflict resolution with one model call
One model call per conflicted file, at about $0.018 modeled cost per file. All 214 checkable files kept Git’s already-merged text and contained no conflict markers, and about 84% matched the developers’ resolution.
Planning speed as workers are added
Merget planned 40 Flask merges in 28.9 seconds, down from 241.9 with one worker. On Ripgrep the speedup was about 13×.
Less agent work with the one-call resolver
On Flask batch 2, the resolver cut agent sessions from 7 to 2 and median time from 478.3 to 354.3 seconds, with the same branch outcomes. List-price spend was 57% lower.
We ran these on real code. Open-source repositories, historical merges and repeated runs.
Every benchmark uses open-source repositories such as Flask, Ripgrep, Vue and TypeScript, at pinned commits.
Conflicts and batches are replayed from each project’s own merge history, and resolutions are compared with what its developers committed.
Timing, cost and resolution results come from repeated runs on a pinned Merget build, with the same model and budget on every side of a comparison.
Give your agents a merge queue that helps finish the work. Start with evidence from your own repository.
These results are why we pair a detailed PR graph with a low-cost first resolution pass. More dependency context finds more collisions, and resolving files without a full agent loop cuts the work needed to finish a batch.
Start in Advisory mode to see Merget’s findings on your own pull requests.
Sign up free. Connect one repository and see where your parallel pull requests collide.
Sign up free