StormEval
  1. StormEval
  2. Models
  3. Grok 4.7

Daily test results · Cursor · effort medium

Is Grok 4.7 getting worse?

Building baseline, day 3 of 14

No verdict yet: day 3 of a 14-day baseline.

Runs through
Cursor
Effort
medium
Provider
cursor-cli
Model id
grok-4.7-medium
Tasks
New issues in real code
Updated
2026-10-21 04:41 UTC

Rating over time

Higher is better. The band is one standard error either side. The dashed line is the first day. Movement inside the band means nothing.

Was Grok 4.7 nerfed?

No verdict yet

This is day 3 of the 14-day baseline for Grok 4.7. The baseline began on 4 October 2026. If the model runs every day, the baseline is complete on 18 October 2026 and the first verdict is expected on 19 October 2026.

It is too early to say either way. Until the baseline is complete there is nothing to compare a new day with, and a single day moves by chance.

Rating
1649±200 · one standard error
Change since day 1
−10from 1659 on 4 October 2026
Pass rate, latest graded day
100%latest graded day · 3 graded tasks
Days of data
3since 4 October 2026

What the runs took

Median time per task
7m 59smean 7m 40s · 1 timeout
Output tokens per task
21k– thinking · 2.50M in
Output tokens per second
61median · mean 53
Estimated cost per task
$1.74at API list prices · $4.65 a day

Estimated cost is tokens at API list prices, not money spent. A dash means no list price is set. Graded counts cover 9 tasks over 3 days; time, tokens and cost can also include finished runs excluded from grading.

Time per task

How long each task took. A task not finished in 15 minutes is a fail, and counts as 15 minutes of time spent.

  • Grok 4.7median 7m 59sslowest timed out · pull-request

By task family

Pass rate, mean time and mean output tokens for each kind of problem.

Modelpull-request
Grok 4.789%7m 40s21k

Day by day

DayRatingPassedTimeoutsTime spentMedian timeOutput tokensOutput tokens / sEst. cost
7 Oct1649 ±2003/3019m 33s7m 59s41k55$4.02
5 Oct1392 ±1762/3127m 21s6m 11s42k56$3.22
4 Oct1659 ±2003/3022m 04s8m 32s83k63$6.72

How this is measured

Grok 4.7 gets the same new tasks as every other model. Each task is an issue in a large, working codebase, and the model writes the change that resolves it with its own coding tool, as it would for a pull request. A program runs the tests to check the change. Only one run per task counts toward this model's results.

The model is compared with itself: the last 7 days against its first 14 days. A verdict is only given when the difference is too large to be chance. A task not finished in 15 minutes counts as a fail.

Read the full method

Not a leaderboard. Models run at different effort settings and through different tools.

Other models