PROBE

Frontier Coding Agents Find Different Bugs
Than Maintainers Fix

Marco Paina, Mark Müller, Niels Mündler-Sasahara, Martin Vechev

Leaderboard

Can your agent find the bugs maintainers fix? In PROBE, coding agents are tasked to audit a whole repository for bugs. We compare their findings against 2,457 bugs that maintainers fixed over the following 18 months.

2,457 reference bugs across 20 repositories. Models use PROBE audit harness.

PROBE model results. Use the column buttons to sort. All percentages are relative to the maintainer-fixed reference set.
#
01DeepSeekDeepSeek V4.1 Flashhigh10.5 percent15.2 percent8.1 percent5,019$73
02OpenAIGPT-5.6 Solhigh10.2 percent20.8 percent6.7 percent8,285$1,185
03OpenAIGPT-5.6 Lunaxhigh10.1 percent17.3 percent7.1 percent6,636$131
04Z.aiGLM 5.3 Flashhigh9.7 percent15.8 percent7.0 percent6,029$120
05OpenAIGPT-5.6 Solmedium9.6 percent16.9 percent6.7 percent6,675$678
06OpenAIGPT-5.6 Lunahigh9.0 percent13.0 percent6.9 percent5,017$55
07OpenAIGPT-5.6 Sollow9.0 percent11.4 percent7.5 percent3,903$276
08OpenAIGPT-5.4medium8.5 percent11.0 percent6.9 percent4,204$655
09OpenAIGPT-5.6 Terramedium8.3 percent9.1 percent7.6 percent3,093$224
10Google / GeminiGemini 3.5 Flashmedium7.8 percent9.8 percent6.4 percent3,867$493
11MetaMuse Spark 1.3*high7.4 percent15.9 percent4.8 percent8,372$164
12OpenAIGPT-5.6 Luna*medium7.3 percent7.6 percent7.0 percent2,774$15
13Anthropic / ClaudeClaude Sonnet 5medium6.7 percent7.9 percent5.8 percent3,472$421
14OpenAIGPT-5.6 Lunalow5.8 percent5.3 percent6.5 percent2,027$8

Tap a row for detailed scores.

F1 score

Harmonic mean of recall and precision. Higher is better.

Recall

Share of reference bugs recovered by the agent. Higher is better.

Precision

Share of agent findings matching the reference set. Unmatched findings may still be valid.

Findings

Total bug findings reported by the agent across the benchmark, including reports that do not match the reference set.

Cost

API cost in US dollars for one full benchmark run.

GPT-5.6 Luna (medium) and Muse Spark results are means over 10 and 5 runs, respectively. Other configurations use one run. Different reasoning efforts are listed separately.

THE BENCHMARK

What is PROBE?

We use the bugs maintainers actually fixed to evaluate
what an agent could have found months earlier.

FIGURE 1 / EVALUATION OVERVIEWView full-size figure
The paper’s main figure: a repository snapshot at T₀ feeds two parallel paths. Maintainer fixes from T₀ to T₁ form a reference set after excluding bugs introduced later. A coding agent audits the same snapshot without later history or network access. Its reports are matched against the reference set to calculate recall and precision, while distinguishing unfixed real bugs from incorrect reports.

Scroll horizontally to explore the diagram.

Overview of PROBE. We snapshot a repository at T₀. In parallel, we mine maintainer fixes during the reference window T₀ → T₁ and ask a coding agent to audit the original snapshot. Only fixed bugs already present at T₀ enter the reference set. We then match agent reports against that set to compute recall and precision.

An open world needs a partial reference. A bug absent from the reference set is not necessarily a false positive. Maintainers may not have fixed it yet. We independently assess validity to make that distinction.

Real projects. A wide range of bugs.

KEY FINDINGS

Agents find different bugs.

PERFORMANCEFull size

Cost Efficiency Comparison

F1 scores versus API cost. GPT-5.6 Luna improves from about 6% to 10% F1 across reasoning efforts, while GPT-5.6 Sol reaches about 10% F1 at substantially higher cost. Other evaluated models are shown for comparison.
F1 scores against the maintainer-fixed reference set versus API cost. Luna (blue) and Sol (orange) are connected across reasoning efforts; faint markers show reruns.

Preprint

PROBE

Proactive Repository-wide
Open-world Bug Evaluation

2026

Frontier Coding Agents Find Different Bugs Than Maintainers Fix

Marco Paina, Mark Müller, Niels Mündler-Sasahara, Martin Vechev

Proactive bug discovery is an important software-engineering problem, yet the ability of coding agents to find the bugs that human maintainers would repair across an entire repository remains understudied. PROBE measures this capability using 2,457 bugs fixed over 18 months across 20 diverse repositories.

Agents find many valid bugs, but their findings follow a different distribution from maintainer fixes. The benchmark makes this gap measurable and provides a reference for improving repository-wide bug discovery.

RESOURCES

Resources for researchers

Preprint

Evaluation methodology and detailed results and analysis.

Download paper

Dataset / Hugging Face

The PROBE benchmark dataset will be available on Hugging Face.

Dataset forthcoming

Citing PROBE

If you use PROBE in your research,
please cite this work.

BIBTEX
@misc{paina2026probe,
  title  = {PROBE: Frontier Coding Agents Find Different Bugs Than Maintainers Fix},
  author = {Marco Paina and Mark Müller and Niels Mündler-Sasahara and Martin Vechev},
  year   = {2026},
  url    = {https://probebench.com}
}