Grok 4.6 scores C- overall on Electricity Bench and clears tier 4 of 5 on real-world issues. Its best suite is spec planning at C. One pass of our task set uses 13% of SuperGrok Plus's weekly limit. Every grade comes from private tasks the agent has not seen, run headless on the subscription you would actually buy.Measured
No longer on the leaderboard. These grades stay published as the record of what this agent scored while it ran.
"Clears" marks the highest rung where every task at it and below was solved. Tier 1: localized single-file bug · tier 3: cause in a different module than the symptom · tier 5: problems that took a human hours. A cleared rung solved every task on it; a partial rung solved some. The headline stops at the last unbroken rung, so a solved tier above a half-solved one counts only as partial.
Clears level 2 of 5 (partial at levels 3, 4 and 5) on Vibe coding v1 - the vaguest report level at which it still fixed every bug, having also cleared every richer level below
12345
What the levels mean
Level 1: a full brief naming the surface and the acceptance · level 3: the report as filed · level 5: a vague vibe report in a non-technical user's words. Context falls as the level rises, so vaguer is harder. A cleared level fixed every bug at it and below; a partial level fixed some. The headline stops at the last unbroken level, so a fix above a half-cleared level counts only as partial.
9 of this suite's tasks were credited rather than run: on a suite that asks the same problem at several levels of detail, solving it from the vaguest description credits the more detailed ones instead of asking again.
11 of 15 tasks solved - grouped by tier, easiest first; hover a square for its time and turns. solved partial not solved
Run on grok-cli grok 1.0.30 (04b7ffed98c6), model grok-4.6 (reasoning-effort high), week 2026-W39.
One run of this suite consumes 3.0% of SuperGrok Plus.
How the plan cost was measured
Measured per suite run (reported-delta); an absolute cost on this plan, not comparable with another agent's plan. Measured on a dedicated subscription.
0 of 4 tasks solved - hover a square for its time and turns. solved partial not solved
Run on grok-cli grok 1.0.30 (04b7ffed98c6), model grok-4.6 (reasoning-effort high), week 2026-W39.
One run of this suite consumes 10.0% of SuperGrok Plus.
How the plan cost was measured
Measured per suite run (reported-delta); an absolute cost on this plan, not comparable with another agent's plan. Measured on a dedicated subscription.
21 of 25 tasks solved (9 credited without running) - each row is one bug, vaguest report first and context growing to the right; hover a square for its time and turns. solved partial not solved credited
Run on grok-cli grok 1.0.30 (04b7ffed98c6), model grok-4.6 (reasoning-effort high), week 2026-W39.
One good solve on this suite consumes under 1% of SuperGrok Plus's weekly limit. The meter reports whole percent and did not move over the run, so this is the resolution's ceiling, not a measured share - at the plan's listed price, at most $0.230 per task.
How the plan cost was measured
Counted over each issue's first solve (5 solves); the walk's failed harder cells and confirmation runs are the benchmark's own search cost and are excluded (full walk: 6.0% over 16 cells). Measured per cell run (reported-delta); an absolute cost on this plan, not comparable with another agent's plan. Measured on a dedicated subscription.
Task outputs from these runs are withheld: publishing them would reveal the private suite. Per-task scores, times and turns are in the chips above.
Trajectory
One point per grading week - a re-run within a week shows only its latest execution. Grades compare only within a suite version, so each version gets its own line; while a suite is being retired both versions run, and the superseded one is dashed. The filled point is the run the scorecard shows today. Click a point or week for plan usage. All agents over time →
Dotted = a new model version took the line over (grok-4.5 → grok-4.6): the points either side were graded by different models. Plan or settings re-registrations join solid.
Weekly heads
Newest week first. Click a row for usage.
Week
Grade
Capability
Clears
Task time
Usage /1w
2026-W39 · v3now
D
47%
tier 4 · p5
7m 10s
3.0% of SuperGrok Plus
2026-W38 · v3
C-
60%
tier 4 · p5
6m 28s
4.0% of SuperGrok Plus
2026-W37 · v3
C-
60%
tier 4 · p5
6m 14s
0.9% of SuperGrok Plus
2026-W36 · v3
C-
60%
tier 4 · p5
12m 47s
1.0% of SuperGrok Plus
2026-W35 · v3
D-
40%
tier 3 · p5
5m 34s
1.0% of SuperGrok Plus
2026-W34 · v3
C-
60%
tier 4 · p5
6m 19s
0.8% of SuperGrok Plus
2026-W33 · v3
C-
58%
tier 1 · p5
6m 45s
4.7% of SuperGrok Plus
2026-W32 · v3
C-
60%
tier 4 · p5
4m 7s
2.4% of SuperGrok Plus
Embed this grade
Put Grok 4.6's current grade in a README or a docs page.
Markdown
[](https://electricitybench.com/models/grok-cli-grok-4-6/)
HTML
<a href="https://electricitybench.com/models/grok-cli-grok-4-6/"><img src="https://electricitybench.com/badge/grok-cli-grok-4-6.svg" alt="Grok 4.6 on Electricity Bench: C-"></a>
Badges update every Monday with the weekly run. GitHub renders them from this URL.
Frequently asked questions
Is Grok 4.6 worth it on SuperGrok Plus?
On our private real-world suite (real-world@v3), Grok 4.6 earned grade D with 47% capability, clearing every problem up to tier 4 of 5 - a cross-cutting problem needing broad codebase orientation and landing some tier 5 problems. It runs on SuperGrok Plus at $100/month (public price as of 2026-09-14). One full suite run consumed 3.0% of the plan's week window. Measured 2026-09-20.
Is Grok 4.6 good for coding?
Grok 4.6 clears tier 4 of our five-tier real-world ladder - every task at that tier and below - where tier 1 is a localized single-file bug and tier 5 is a problem that took a human engineer hours. It solves some but not all tasks up at tier 5. Its capability score on real-world@v3 is 47% (grade D). Last benchmarked 2026-09-20.
How much of SuperGrok Plus does one Grok 4.6 task use?
One full suite run consumed 3.0% of SuperGrok Plus's weekly limit, read off the provider's own meter before and after the run. A benchmark task is a whole multi-turn agent session, not a message, and the share belongs to this plan alone: it is not comparable with another agent's plan. Measured 2026-09-20.
