StormEval
  1. StormEval
  2. Models
  3. GPT-6 Luna (high)

Daily test results · Codex · effort high

Is GPT-6 Luna (high) getting worse?

Building baseline, day 1 of 14

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

Runs through
Codex
Effort
high
Provider
codex-cli
Model id
gpt-6-luna
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 GPT-6 Luna (high) nerfed?

No verdict yet

This is day 1 of the 14-day baseline for GPT-6 Luna (high). The baseline began on 8 October 2026. If the model runs every day, the baseline is complete on 21 October 2026 and the first verdict is expected on 22 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
1780±184 · one standard error
Change since day 1
–needs two days
Pass rate, latest graded day
100%latest graded day · 12 graded tasks
Days of data
1since 8 October 2026

What the runs took

Median time per task
2m 46smean 2m 56s · 0 timeouts
Output tokens per task
9.5k44% thinking · 1.71M in
Output tokens per second
57median · mean 55
Estimated cost per task
$0.029at API list prices · $0.352 a day

Estimated cost is tokens at API list prices, not money spent. A dash means no list price is set. Graded counts cover 12 tasks over 1 day; 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.

  • GPT-6 Luna (high)median 2m 46sslowest 5m 25s · pull-request

By task family

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

Modelpull-request
GPT-6 Luna (high)100%2m 56s9.5k

Day by day

DayRatingPassedTimeoutsTime spentMedian timeOutput tokensOutput tokens / sEst. cost
8 Oct1780 ±18412/12035m 17s2m 46s114k57$0.352

How this is measured

GPT-6 Luna (high) 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