Verified but agingThis is an efficiency signal, so it belongs beside quality rather than being mistaken for quality.
source
BridgeBench
metric
Strict (%)
judge
Speed / cost
direction
higher better
group id
bridgebench_cost_strict_2026_05
domain
Coding
What it measures vs what it misses
✓ Measures
Strict success rate for the cost benchmark's evaluated tasks.
✗ Misses
Broader capability beyond the cost-task set.
Why this countsIt tells you whether the model can generate, repair, and reason over code under evaluator pressure rather than marketing examples.Same-test ruleThis percentile only compares models inside the exact benchmark/version group shown here. It is not a universal score.What it missesIt does not fully capture repo-scale iteration, IDE ergonomics, or long debugging loops.