Fewer conflicts, less repeated work.

We benchmark the parts of our semantic merge queue that make it work: finding the right dependencies, resolving real merge conflicts and cutting repeated agent work. These are our findings from running Merget on open-source repositories.

Merget resolved all 223 conflicted files in two runs and found more reference calls than graphify in 11 of 12 repositories. On a Flask workload, its one-call resolver cut modeled spend by 69% against Merget with agent sessions alone, with the same branch outcomes.

MeasuredOct 13 – Nov 1, 2026
CodeOpen-source repositories
RunsRepeated on pinned builds

We ran these on real code. Open-source repositories, historical merges and repeated runs.

Real repositories

Every benchmark uses open-source repositories such as Flask, Ripgrep, Vue and TypeScript, at pinned commits.

Real merges

Conflicts and batches are replayed from each project’s own merge history, and resolutions are compared with what its developers committed.

Repeated runs

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.

Next step

Sign up free. Connect one repository and see where your parallel pull requests collide.

Sign up free