Skip to the comparison

Muse control vs Opus 4.8

Opus 4.8 leads on quality: 7.0 points higher; Muse control leads on cost and agent time: 70.4× cheaper and 1.8× faster.

24 tasksData from

Stet score

Muse controlRank 12 of 14

33.295% range 24.3–42.4

Opus 4.8Rank 11 of 14

40.295% range 30.3–50.37.0 points higher

A directional read: their 95% score ranges overlap.

Cost / task

Muse control$0.1070.4× cheaper
Opus 4.8$7.05

Agent time / task

Muse control13.2 min1.8× faster
Opus 4.823.3 min

Task by task

Muse control solved 1 task that Opus 4.8 didn’t, and Opus 4.8 solved 4 that Muse control didn’t. Both solved 9; neither solved 10.

Muse control only 1

  • stet-2450ca2dEquivalent to the merged fix

Opus 4.8 only 4

  • stet-15439c21Passed tests
  • stet-commit-f0caded9Equivalent to the merged fix
  • stet-6f84e978Passed tests
  • 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
TaskMuse controlOpus 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-15439c21FailedPassed testsOpus 4.8 only
stet-66762b4cPassed testsPassed testsBoth
stet-commit-f0caded9FailedEquivalent to the merged fixOpus 4.8 only
stet-commit-5d766ddeEquivalent to the merged fixEquivalent to the merged fixBoth
stet-43493c52Passed testsPassed testsBoth
stet-6f84e978FailedPassed testsOpus 4.8 only
stet-commit-f8ae1177FailedFailedNeither
stet-2450ca2dEquivalent to the merged fixFailedMuse control only
stet-commit-342d0ac0FailedFailedNeither
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
MetricMuse controlOpus 4.8
Rank12 of 1411 of 14
Stet score33.295% range 24.3–42.440.295% range 30.3–50.3
Solved10/248 passed, 2 judged equivalent13/2411 passed, 2 judged equivalent
Passed review5/248/231 not recorded
Matched merged change8/2411/24
Cost / task$0.10$7.05
How cost was recordedestimated from tokensreported by its harness
Agent time / task13.2 min23.3 min
Ran inlocal Dockerlocal 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 Muse control’s 7.

Changes up to 150 lines
Muse controlOpus 4.8
Matched merged change7/119/11
Passed review5/118/11
Cost / task$0.03$1.41
Agent time / task4.3 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 Muse control’s 4.

Small fixes
Muse controlOpus 4.8
Matched merged change4/77/7
Passed review4/77/7
Cost / task$0.03$1.17
Agent time / task4.3 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.

Opus 4.8 matched the merged change more often: 2 of 13 to Muse control’s 1.

Larger changes
Muse controlOpus 4.8
Matched merged change1/132/13
Passed review0/130/121 not recorded
Cost / task$0.16$11.83
Agent time / task20.8 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