ScaffoldBench

RunOpus 5.5repeat 2

Single on Rebook onto the earliest available flight and settle the difference

claude-opus-5-5__single__airline-medium__r2

Score

1.000

passed
design ran as designed
Cost
$0.072
Latency
21.0s
setup 0.0s, grading 0.0s
Turns
10
Tool calls
9
Subagents
0
Tokens in / out
47k / 1.5k
41,308 read from cache

Did the design run?

every check held
  • Run completed: heldharness.run-completedThe environment was built, the architecture returned and grading finished, none of them throwing.
  • No API failures: heldharness.apiNo model call failed at the API.
  • Every call ended: heldharness.calls-endedEvery call ended with a result, or was stopped by the run's own limits.
  • No harness tool denied: heldharness.harness-toolsThe sandbox guard never denied a harness tool, nor a tool the session itself offered.
  • Tool servers connected: heldharness.mcp-connectedEvery tool server the harness gave a call was connected when the session started.
  • No foreign tool servers: heldharness.mcp-hermeticNo call loaded a tool server the harness did not give it.
  • Builtin tools: heldharness.builtin-toolsA check recorded with the run.
  • Structured replies arrived: heldharness.structured-outputEvery call that asked for structured output and ran to the end got it.
  • No silent fallbacks: heldharness.not-degradedNo phase fell back on a default (an empty plan, a default winner) instead of its output.
  • Each call was shown the right tools: heldsingle.toolsThe agent was shown exactly the task’s tools, none missing and none extra.

Phases

Main: 0.0s to 21.0s, finished, 9 tool calls, $0.072

Drawn from the phase records: timing and cost per call, no tool calls or messages.

PhaseDurationCostTurnsToolsModel
Main21.0s$0.072109claude-opus-5-5

The call-by-call replay is not published for this run. Traces are large, so the repository keeps 9 of this run set’s 900 and leaves the rest out; the score, phases and final answer on this page come from the committed run record.

Runs you can replay

Record this cell yourself: npm run bench -- run --strategies single --tasks airline-medium --models claude-opus-5-5 --repeats 1

Score breakdown

  • passReservation moved to the earliest flight with an available seat, same cabin
    1.00weight 0.43

    booked on AA204, expected AA204

  • passExactly one fee, the fare difference for the flight actually booked
    1.00weight 0.43

    fare difference owed on the booked flight: 8000 cents

  • passExactly one economy seat moved from the old flight to the new one
    1.00weight 0.14

Penalties

No penalties were applied.

Scorer metadata

tool calls
9
failed tool calls
0
distinct tools
9

Final answer

Dana Whitfield (R2087) is now on AA204, leaving SFO at 09:05 on 2026-08-03 and arriving at ORD. She stays in economy, and she owes $80.00 for the change, which I've charged.

Why AA204: it's the earliest flight that day with an economy seat open.

  • UA88 (06:15) has no economy seats left.
  • AA918 (07:30) is cancelled.
  • AA204 (09:05) has 4 economy seats left.

What she paid for the change:

  • Fare difference: $80.00. The AA204 economy fare is $390.00 and she originally paid $310.00. Under the economy fare rules, a higher new fare is collected in full and no tier is exempt. This is the only entry on her ledger.
  • Change fee: $0. The usual $75.00 fee is waived because she's a gold-tier member.

I only changed R2087. Nothing else was touched.

The session date I was given (2026-10-06) is after this flight. The airline system's own date is 2026-07-28 and the flight still shows as scheduled, so I treated it as an upcoming trip.

Provenance of the numbers on this page

run set
scaffold-or-scale-v1
models
Haiku 4.5, Sonnet 5.5, Opus 5.5
effort
high
repeats
2
fixtures
replay
runs
900 / 900
strategy cost
$354.44
judge cost
$9.19
wall clock
9h 48m
git
fce5807b2d

Cost excludes judge calls, which are tracked separately so a scoring model never flatters or penalises an architecture. Every figure on this site is read from results/ at build time.