Skip to the comparison

Opus 4.8 vs SWE-2 Max

SWE-2 Max leads on quality: 26.2 points higher; Opus 4.8 leads on agent time: 2.9× faster; SWE-2 Max’s cost wasn’t recorded.

24 tasksData from

Stet score

Opus 4.8Rank 11 of 14

40.295% range 30.3–50.3

SWE-2 MaxRank 1 of 14

66.495% range 56.8–75.426.2 points higher

Their 95% score ranges don’t overlap.

Cost / task

Opus 4.8$7.05
SWE-2 Maxnot recorded

Agent time / task

Opus 4.823.3 min2.9× faster
SWE-2 Max68.3 min

Task by task

Opus 4.8 solved 1 task that SWE-2 Max didn’t, and SWE-2 Max solved 4 that Opus 4.8 didn’t. Both solved 12; neither solved 7.

Opus 4.8 only 1

  • stet-43493c52Passed tests

SWE-2 Max only 4

  • stet-2450ca2dPassed tests
  • stet-commit-342d0ac0Equivalent to the merged fix
  • stet-commit-5e075641Passed tests
  • stet-commit-a8716b88Equivalent 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
TaskOpus 4.8SWE-2 MaxSolved 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-15439c21Passed testsEquivalent to the merged fixBoth
stet-66762b4cPassed testsPassed testsBoth
stet-commit-f0caded9Equivalent to the merged fixPassed testsBoth
stet-commit-5d766ddeEquivalent to the merged fixPassed testsBoth
stet-43493c52Passed testsFailedOpus 4.8 only
stet-6f84e978Passed testsPassed testsBoth
stet-commit-f8ae1177FailedFailedNeither
stet-2450ca2dFailedPassed testsSWE-2 Max only
stet-commit-342d0ac0FailedEquivalent to the merged fixSWE-2 Max only
stet-commit-60a0e6c2Passed testsPassed testsBoth
stet-commit-5e075641FailedPassed testsSWE-2 Max only
stet-commit-2826765eFailedFailedNeither
stet-commit-a8716b88FailedEquivalent to the merged fixSWE-2 Max only
stet-commit-30506f8eFailedFailedNeither
stet-commit-87814583FailedFailedNeither
stet-commit-d2ab0c25FailedFailedNeither
stet-commit-e41c2e2dFailedFailedNeither
stet-commit-e928166fFailedFailedNeither

Side by side

Side by side
MetricOpus 4.8SWE-2 Max
Rank11 of 141 of 14
Stet score40.295% range 30.3–50.366.495% range 56.8–75.4
Solved13/2411 passed, 2 judged equivalent16/2413 passed, 3 judged equivalent
Passed review8/231 not recorded8/24
Matched merged change11/2413/24
Cost / task$7.05not recorded
How cost was recordedreported by its harnessnot recorded
Agent time / task23.3 min68.3 min
Ran inlocal DockerDaytona sandbox

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 4.8 matched the merged change more often: 9 of 11 to SWE-2 Max’s 8.

Changes up to 150 lines
Opus 4.8SWE-2 Max
Matched merged change9/118/11
Passed review8/117/11
Cost / task$1.41not recorded
Agent time / task12.8 min22.1 min

Small fixes

7 tasks

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

Opus 4.8 matched the merged change more often: 7 of 7 to SWE-2 Max’s 5.

Small fixes
Opus 4.8SWE-2 Max
Matched merged change7/75/7
Passed review7/75/7
Cost / task$1.17not recorded
Agent time / task9.7 min21.5 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.

SWE-2 Max matched the merged change more often: 5 of 13 to Opus 4.8’s 2.

Larger changes
Opus 4.8SWE-2 Max
Matched merged change2/135/13
Passed review0/121 not recorded1/13
Cost / task$11.83not recorded
Agent time / task32.2 min107.3 min

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

About this data

  • 24 tasks, each a merged change replayed from the repo as it was just before the merge.
  • Data from .
  • Both setups come from the same leaderboard run of 14 setups: compare-n24-r3b.