Skip to the comparison

Grok 4.7 High vs Muse control

Grok 4.7 High leads on quality: 30.0 points higher; Muse control leads on cost and agent time: 57.5× cheaper and 1.4× faster.

24 tasksData from

Stet score

Grok 4.7 HighRank 4 of 14

63.295% range 52.2–73.230.0 points higher

Muse controlRank 12 of 14

33.295% range 24.3–42.4

Their 95% score ranges don’t overlap.

Cost / task

Grok 4.7 High$5.76
Muse control$0.1057.5× cheaper

Agent time / task

Grok 4.7 High18.9 min
Muse control13.2 min1.4× faster

Task by task

Grok 4.7 High solved 4 tasks that Muse control didn’t, and Muse control solved 1 that Grok 4.7 High didn’t. Both solved 9; neither solved 10.

Grok 4.7 High only 4

  • stet-15439c21Passed tests
  • stet-commit-f0caded9Equivalent to the merged fix
  • stet-6f84e978Passed tests
  • stet-commit-f8ae1177Passed tests

Muse control only 1

  • stet-43493c52Passed 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
TaskGrok 4.7 HighMuse controlSolved 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 testsFailedGrok 4.7 High only
stet-66762b4cPassed testsPassed testsBoth
stet-commit-f0caded9Equivalent to the merged fixFailedGrok 4.7 High only
stet-commit-5d766ddeEquivalent to the merged fixEquivalent to the merged fixBoth
stet-43493c52FailedPassed testsMuse control only
stet-6f84e978Passed testsFailedGrok 4.7 High only
stet-commit-f8ae1177Passed testsFailedGrok 4.7 High only
stet-2450ca2dPassed testsEquivalent to the merged fixBoth
stet-commit-342d0ac0FailedFailedNeither
stet-commit-60a0e6c2FailedFailedNeither
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
MetricGrok 4.7 HighMuse control
Rank4 of 1412 of 14
Stet score63.295% range 52.2–73.233.295% range 24.3–42.4
Solved13/2411 passed, 2 judged equivalent10/248 passed, 2 judged equivalent
Passed review9/245/24
Matched merged change9/248/24
Cost / task$5.76$0.10
How cost was recordedestimated from tokensestimated from tokens
Agent time / task18.9 min13.2 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.

Both matched the merged change on 7 of 11.

Grok 4.7 High passed review more often: 7 of 11 to Muse control’s 5.

Changes up to 150 lines
Grok 4.7 HighMuse control
Matched merged change7/117/11
Passed review7/115/11
Cost / task$2.35$0.03
Agent time / task8.8 min4.3 min

Small fixes

7 tasks

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

Both matched the merged change on 4 of 7.

Small fixes
Grok 4.7 HighMuse control
Matched merged change4/74/7
Passed review4/74/7
Cost / task$1.85$0.03
Agent time / task8.1 min4.3 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.

Grok 4.7 High matched the merged change more often: 2 of 13 to Muse control’s 1.

Larger changes
Grok 4.7 HighMuse control
Matched merged change2/131/13
Passed review2/130/13
Cost / task$8.64$0.16
Agent time / task27.5 min20.8 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