Skip to the comparison

GPT 6 Sol medium vs Opus 4.8

GPT 6 Sol medium leads on quality, cost and agent time: 17.4 points higher, 2.3× cheaper and 1.5× faster.

24 tasksData from

Stet score

GPT 6 Sol mediumRank 7 of 14

57.695% range 49.5–65.717.4 points higher

Opus 4.8Rank 11 of 14

40.295% range 30.3–50.3

A directional read: their 95% score ranges overlap.

Cost / task

GPT 6 Sol medium$3.012.3× cheaper
Opus 4.8$7.05

Agent time / task

GPT 6 Sol medium15.4 min1.5× faster
Opus 4.823.3 min

Task by task

GPT 6 Sol medium solved 2 tasks that Opus 4.8 didn’t, and Opus 4.8 solved 1 that GPT 6 Sol medium didn’t. Both solved 12; neither solved 9.

GPT 6 Sol medium only 2

  • stet-commit-f8ae1177Passed tests
  • stet-commit-342d0ac0Equivalent to the merged fix

Opus 4.8 only 1

  • stet-commit-60a0e6c2Passed tests

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
TaskGPT 6 Sol mediumOpus 4.8Solved 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 testsPassed testsBoth
stet-66762b4cPassed testsPassed testsBoth
stet-commit-f0caded9Equivalent to the merged fixEquivalent to the merged fixBoth
stet-commit-5d766ddeEquivalent to the merged fixEquivalent to the merged fixBoth
stet-43493c52Passed testsPassed testsBoth
stet-6f84e978Passed testsPassed testsBoth
stet-commit-f8ae1177Passed testsFailedGPT 6 Sol medium only
stet-2450ca2dFailedFailedNeither
stet-commit-342d0ac0Equivalent to the merged fixFailedGPT 6 Sol medium only
stet-commit-60a0e6c2FailedPassed testsOpus 4.8 only
stet-commit-5e075641FailedFailedNeither
stet-commit-2826765eFailedFailedNeither
stet-commit-a8716b88FailedFailedNeither
stet-commit-30506f8eFailedFailedNeither
stet-commit-87814583FailedFailedNeither
stet-commit-d2ab0c25FailedFailedNeither
stet-commit-e41c2e2dFailedFailedNeither
stet-commit-e928166fFailedFailedNeither

Side by side

Side by side
MetricGPT 6 Sol mediumOpus 4.8
Rank7 of 1411 of 14
Stet score57.695% range 49.5–65.740.295% range 30.3–50.3
Solved14/2411 passed, 3 judged equivalent13/2411 passed, 2 judged equivalent
Passed review8/248/231 not recorded
Matched merged change10/2411/24
Cost / task$3.01$7.05
How cost was recordedestimated from tokensreported by its harness
Agent time / task15.4 min23.3 min
Ran inDaytona sandboxlocal Docker

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 GPT 6 Sol medium’s 6.

Changes up to 150 lines
GPT 6 Sol mediumOpus 4.8
Matched merged change6/119/11
Passed review6/118/11
Cost / task$0.75$1.41
Agent time / task6.6 min12.8 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 GPT 6 Sol medium’s 5.

Small fixes
GPT 6 Sol mediumOpus 4.8
Matched merged change5/77/7
Passed review5/77/7
Cost / task$0.60$1.17
Agent time / task5.4 min9.7 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.

GPT 6 Sol medium matched the merged change more often: 4 of 13 to Opus 4.8’s 2.

Larger changes
GPT 6 Sol mediumOpus 4.8
Matched merged change4/132/13
Passed review2/130/121 not recorded
Cost / task$4.92$11.83
Agent time / task22.9 min32.2 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