Ranked 5 of 9 on the combined score

Claude Opus 5.5

Claude Code, max reasoning. 398 timed runs on 200 tasks from 18 benchmarks.

20%Combined scoreOver the three tests
6%Within 5%59% shorter, 35% longer
2.26×Forecasting missIts typical forecast against its runtime
1.71×Retrospection missNative, its typical estimate of a finished run
72.2Benchmark scoreOut of 100, 95% interval 67.2 to 77.1

Duration following

Does it work for as long as it is asked? Each task was asked for a short and a long duration: a quarter and four times its own forecast of each task (on PaperBench and PostTrainBench, of its runtime with no time asked).

Where Claude Opus 5.5's runs ended, from a tenth of the time asked to ten times it, for every run and for each ask, with the timing error of each.
AskTiming errorWhere runs ended
Every timed run398 runs2.13×
Short ask199 runs1.99×
Long ask199 runs2.27×

It ran long on short asks (median 1.10× at the short ask) and stopped early on long ones (median 0.57× at the long ask). See every run

Every Opus 5.5 run

Each row is one run, with a mark on the chart. Hover a row to find its mark; click a mark to find its row.

Ask
Result

398 runs

Claude Opus 5.5's runs. Each row links to its run page.
Loading 398 runs.

Forecasting

Before each task, it forecast how long the task would take. Each forecast is set against its own runtime on that task: its run with no time asked.

Typical miss
2.26×
Geometric mean of the factor between forecast and runtime
Most forecasts
58% too low
On 200 tasks
Median forecast
30 min
Median runtime
32 min

Retrospection

After its runs had finished, it was asked how long they took, with less time information at each step. Each figure is its typical miss against the real runtime, two answers per condition.

Oracle
1.01×
Native
1.71×
Context-only
2.12×
Replay
1.34×
Scrubbed
1.77×

Oracle adds an elapsed-time tool. Native and Context-only continue the finished session, with tools on or off. Replay sends a rebuilt transcript to the model's API, and Scrubbed does the same without timestamps or other time cues. On 23 tasks.

Across the 18 benchmarks

Timing on its timed runs, and how good the work was. Score is the mean of its graded runs out of 100, from its runs with no time asked; the benchmark score is the mean of these, each benchmark counting the same.

Claude Opus 5.5 across the 18 benchmarks
AppWorld28 runs
4.02×
0%57.114 graded
CORE-Bench24 runs
3.52×
0%100.012 graded
Terminal-Bench 4.032 runs
2.73×
0%81.316 graded
Humanity's Last Exam40 runs
2.61×
5%63.219 graded
PPTArena20 runs
2.47×
0%47.010 graded
TUA-Bench20 runs
2.27×
0%76.110 graded
PaperBench6 runs
2.12×(few runs)
0%Not scored
YC-Bench8 runs
2.10×(few runs)
13%Own units
OSWorld36 runs
2.10×
8%86.117 graded
Agents' Last Exam24 runs
2.03×
0%67.112 graded
GPQA Diamond24 runs
1.93×
0%91.712 graded
Sakana ALE-Bench20 runs
1.86×
0%Own units
ProgramBench36 runs
1.82×
22%85.718 graded
DeepSWE28 runs
1.79×
0%92.914 graded
BrowseComp24 runs
1.75×
17%75.012 graded
PostTrainBench8 runs
1.68×(few runs)
0%Not scored
METR public tasks4 runs
1.48×(few runs)
0%Too few graded
AssistantBench16 runs
1.45×
25%16.08 graded

Highest timing error first. ALE-Bench and YC-Bench keep their own units and stay out of the score, as do PaperBench and PostTrainBench.

Read before quoting. 1 run was stopped by AgentTime, so its time is a lower bound. Details

Data and citation