Skip to the comparison

Haiku 5.5 low vs Opus 5

Opus 5 leads on quality: 23.8 points higher; Haiku 5.5 low leads on cost and agent time: 27.0× cheaper and 2.3× faster.

24 tasksData from

Stet score

Haiku 5.5 lowRank 10 of 14

41.395% range 34.8–47.8

Opus 5Rank 3 of 14

65.195% range 54.8–74.923.8 points higher

Their 95% score ranges don’t overlap.

Cost / task

Haiku 5.5 low$0.2527.0× cheaper
Opus 5$6.78

Agent time / task

Haiku 5.5 low9.9 min2.3× faster
Opus 523.2 min

Task by task

Haiku 5.5 low solved 0 tasks that Opus 5 didn’t, and Opus 5 solved 3 that Haiku 5.5 low didn’t. Both solved 11; neither solved 10.

Haiku 5.5 low only 0

Opus 5 only 3

  • stet-6f84e978Passed tests
  • stet-2450ca2dPassed tests
  • stet-commit-2826765eEquivalent to the merged fix

A task counts as solved when its tests passed or a judge found the fix equivalent to the merged change, as in the leaderboard’s Solved column. Stet score also weighs code quality, so it can order the two differently.

All 24 compared tasks
Task by task
TaskHaiku 5.5 lowOpus 5Solved by
stet-3169aefaPassed testsPassed testsBoth
stet-89dfbc27Passed testsPassed testsBoth
stet-b28f4fe7Passed testsPassed testsBoth
stet-232b50baPassed testsPassed testsBoth
stet-5276aa3fPassed testsPassed testsBoth
stet-commit-bbbbae09Passed testsPassed testsBoth
stet-15439c21Equivalent to the merged fixPassed testsBoth
stet-66762b4cEquivalent to the merged fixPassed testsBoth
stet-commit-f0caded9Equivalent to the merged fixPassed testsBoth
stet-commit-5d766ddeEquivalent to the merged fixEquivalent to the merged fixBoth
stet-43493c52Passed testsPassed testsBoth
stet-6f84e978FailedPassed testsOpus 5 only
stet-commit-f8ae1177FailedFailedNeither
stet-2450ca2dFailedPassed testsOpus 5 only
stet-commit-342d0ac0FailedFailedNeither
stet-commit-60a0e6c2FailedFailedNeither
stet-commit-5e075641FailedFailedNeither
stet-commit-2826765eFailedEquivalent to the merged fixOpus 5 only
stet-commit-a8716b88FailedFailedNeither
stet-commit-30506f8eFailedFailedNeither
stet-commit-87814583FailedFailedNeither
stet-commit-d2ab0c25FailedFailedNeither
stet-commit-e41c2e2dFailedFailedNeither
stet-commit-e928166fFailedFailedNeither

Side by side

Side by side
MetricHaiku 5.5 lowOpus 5
Rank10 of 143 of 14
Stet score41.395% range 34.8–47.865.195% range 54.8–74.9
Solved11/247 passed, 4 judged equivalent14/2412 passed, 2 judged equivalent
Passed review8/249/231 not recorded
Matched merged change9/2413/24
Cost / task$0.25$6.78
How cost was recordedreported by its harnessreported by its harness
Agent time / task9.9 min23.2 min
Ran inDaytona sandboxsandbox not recorded

Where each setup is the better choice

The leaderboard’s readings on groups of tasks. Each group holds fewer tasks than the overall standings, so treat these as leads to test on your repo.

Changes up to 150 lines

11 tasks

11 tasks whose merged change was 2–149 lines in 1–2 files. The 7 small fixes below are among them.

Opus 5 matched the merged change more often: 10 of 11 to Haiku 5.5 low’s 7.

Changes up to 150 lines
Haiku 5.5 lowOpus 5
Matched merged change7/1110/11
Passed review7/119/101 not recorded
Cost / task$0.02$1.50
Agent time / task2.8 min18.4 min

Small fixes

7 tasks

7 tasks whose instructions start with “Fix”. Their merged changes were 4–29 lines in 1–2 files.

Opus 5 matched the merged change more often: 7 of 7 to Haiku 5.5 low’s 5.

Small fixes
Haiku 5.5 lowOpus 5
Matched merged change5/77/7
Passed review5/77/7
Cost / task$0.01$0.99
Agent time / task2.7 min15.9 min

Larger changes

13 tasks

13 tasks whose merged change ran over 150 lines or more than 3 files: 113–1,420 lines in 2–19 files.

Opus 5 matched the merged change more often: 3 of 13 to Haiku 5.5 low’s 2.

Larger changes
Haiku 5.5 lowOpus 5
Matched merged change2/133/13
Passed review1/130/13
Cost / task$0.45$11.24
Agent time / task15.9 min27.2 min

From the leaderboard’s routing advice

  • Small fix: use Opus 5.
  • Subagents: use Haiku 5.5 low.

See which setup wins on your repo

Stet replays your merged PRs, scores quality above pass/fail, and delivers comparison reports through your agent.

Run it on your repo