223 conflict resolutions. One model call per file. Repeated twice, with Git’s already-merged text preserved in all 214 auditable outputs.
In 9 of the 223 files one side deleted the file while the other changed it, so there is no merged text to compare. The checks for markers, for git’s merged text and for the developers’ match use the other 214.
Outside the conflicts, the file still holds exactly what git had merged on its own. A resolver that edits there changes code nobody asked it to touch.
The file matches the resolution the project’s developers committed at the time. A different resolution can still be a correct one.
Real tokens at the model’s list price, with the model’s thinking billed as output and cached tokens charged at the full input rate, so a real bill is lower.
Real conflicts from Vue, Express, Tokio and Flask. All attempted files were resolved; Vue contributed 163 of the 223.
How to read thisBars on the left count the conflicted files each repository contributed. On the right, modeled dollars per file, the average of the two current runs; that track ends at $0.035.
Full results: both runs
Both runs: every file resolved, git’s merged text kept and no markers left, with the match rate per run.
| Run | Date | Resolved | Kept git’s merged text | Markers / open fences left | Matched the developers |
|---|---|---|---|---|---|
| Run 1 | 2026-10-30 | 223 of 223 | 214 of 214 | 0 / 0 | 179 of 214 (83.6%) |
| Run 2 | 2026-10-30 | 223 of 223 | 214 of 214 | 0 / 0 | 181 of 214 (84.6%) |
The token counts behind the modeled cost. Output tokens include the model’s thinking.
| Run | Input tokens | Output tokens | Modeled cost | Per file |
|---|---|---|---|---|
| Run 1 | 1,205,242 | 152,564 | $3.936124 | $0.0177 |
| Run 2 | 1,205,242 | 163,256 | $4.043044 | $0.0181 |
For conflicts like these, one model call per file was enough. Agent sessions are kept for the conflicts that need them.
The one-call resolver resolved every one of the 223 benchmark files. None of the 214 checkable outputs left a conflict marker or changed what Git had already merged, and about 84% matched the developers’ own resolution.
Its model cost was about $0.018 per file. In the queue, this resolver runs first, and Merget falls back to an agent session only when it is needed.
Try it on your conflicts. Connect one repository and see what Merget resolves between your open pull requests.
Sign up freeMeasured October 30, 2026: one model call per conflicted file, production settings, up to 10 merges per repository from vuejs/core, express, tokio and flask.
Merge queue planning: 40 merges in under 30 seconds