Grok 4.7 has moved from a vague early-September estimate to a specific pre-release countdown. Elon Musk said on September 2 that it would arrive in ten days, implying an expected date of approximately September 12, 2026.
Earlier statements described a model with roughly 2.1 trillion parameters, improved token efficiency, somewhat slower serving, and supplemental training using substantial SpaceX company data.
That still does not amount to a complete launch. xAI has not published a Grok 4.7 model card, benchmark suite, final API model ID, context window, supported modalities, or official pricing. For now, Grok 4.6 is the only measurable production baseline.
The Current Release Signal
The September 12 date comes from Musk’s countdown, not from a separate xAI release-calendar announcement.
Source: Elon Musk on X, September 2, 2026
Here is how the public timeline currently looks:
| Date | Public signal | What it tells us |
|---|---|---|
| Late July 2026 | Musk described a roughly 2.1T model, improved token efficiency, and somewhat slower serving. | Expected scale and serving trade-offs. |
| August 12, 2026 | Initial training was described as complete, with supplemental training using substantial SpaceX company data. | A training update, not proof of release readiness. |
| September 2, 2026 | “Grok 4.7 comes out in 10 days.” | The clearest release countdown so far. |
| September 12, 2026 | Date inferred from the ten-day countdown. | Expected target, pending official release and working endpoint. |
I would treat Grok 4.7 as an evaluation candidate until a production request succeeds against an officially documented endpoint.
Confirmed Claims and Missing Specifications
At this point, the model name and countdown are the clearest facts. Most technical details remain either founder-stated or unpublished.
| Specification | Current status | Evidence |
|---|---|---|
| Release timing | Around September 12, inferred from the September 2 countdown | Founder-announced target |
| Model scale | Approximately 2.1T parameters | Founder-stated |
| Initial training | Described as complete by August 12 | Founder-stated |
| Supplemental training | Includes substantial SpaceX company data | Founder-stated |
| Relative quality | Claimed to be significantly better than Grok 4.6 | Unverified claim |
| Token efficiency | Claimed improvement over Grok 4.6 | Unverified claim |
| Serving speed | Expected to be somewhat slower | Founder-stated |
| Context window | Not published | Unknown |
| Input/output modalities | Not published | Unknown |
| Final API model ID | Not confirmed in xAI documentation | Unknown |
| Official pricing | Not published | Unknown |
| Official benchmarks | None published for Grok 4.7 | Unknown |
The roughly 2.1T parameter statement does not tell us how many parameters are active during inference, whether the model uses sparsity or expert routing, or what its effective training compute looks like. Parameter count alone is a poor predictor of production results.
Why the SpaceX Data Claim Is Interesting
The SpaceX company-data statement may matter more than the headline parameter count.
A strong engineering corpus could help with technical reasoning, debugging, design, optimization, and long-running agent tasks. In those areas, data quality, task distribution, and post-training can matter more than raw model size.
This would also fit xAI’s existing training direction. The Grok 4.6 training report describes supplemental training with high-quality engineering data, followed by supervised fine-tuning and reinforcement learning across coding, STEM, web development, kernel optimization, and computer-aided design.
That makes the Grok 4.7 approach plausible, but not proven. The evidence will be in reproducible engineering evaluations, completion rates, latency, and cost per successful task.
Grok 4.6 Is the Baseline to Beat
There are no official Grok 4.7 scores yet, so I would compare any launch claims against the released Grok 4.6 results.
| Official evaluation | Grok 4.6 High | Grok 4.5 High | GPT-5.6 Sol Max | Claude Fable 5 Max |
|---|---|---|---|---|
| AA Intelligence Index | 61 | 56 | 61 | 62 |
| GDPVal-AA v2 | 1753 | 1526 | 1728 | 1741 |
| CursorBench v3.2 | 69.9% | 66.7% | 67.2% | 70.5% |
| DeepSWE v1.1 | 65.9% | 54.0% | 73.0% | 70.0% |
| FrontierCode v1.1 (Extended) | 61.3% | 56.6% | 60.6% | 63.6% |
| Terminal-Bench v3.0 | 26.0% | 15.7% | 34.6% | 34.1% |
Grok 4.6 improves on Grok 4.5 in every row shown. It matches GPT-5.6 Sol on the overall intelligence index, leads this group on GDPVal-AA v2, and slightly exceeds GPT-5.6 Sol on FrontierCode.
The weaker areas are DeepSWE and Terminal-Bench. Those are especially relevant if Grok 4.7 is meant to improve repository-level coding and terminal-based agent work.
A convincing upgrade would preserve Grok 4.6’s knowledge-work results while improving patch acceptance, command-line recovery, and long-running task completion. Becoming competitive with the released Claude Fable 5.1 on coding and agent workflows would be a meaningful target, but that remains a forecast rather than a current benchmark result.
What I Would Measure After Release
Repository-level coding
I would run both versions on the same representative repositories and track:
- Accepted patches
- Passing tests
- Regression rate
- Failed tool calls
- Recovery after command-line errors
A better final answer is not enough if the model produces less reliable changes.
Long-horizon agent work
For multi-stage workflows, record completed tasks, retries, tool failures, human interventions, and recovery behavior. Agent quality should be measured across the whole run, not only by inspecting the final response.
Technical knowledge work
Grok 4.6 already leads the comparison group on GDPVal-AA v2. Grok 4.7 should retain that strength while improving design reviews, research synthesis, debugging, optimization, and other technical workflows.
Token efficiency
A larger model may still be cheaper per successful task if it reaches the correct result in fewer attempts. I would compare input tokens, cached input, output tokens, retries, and total spend for the same accepted outcome.
Latency and throughput
If serving is slower, quality improvements need to justify the delay. Measure time to first token, sustained throughput, complete-task wall time, error rate, and cost under realistic concurrency.
Pricing: What Is Known
Grok 4.7 pricing has not been announced.
For comparison, the published Grok 4.6 standard rate is $2 per 1 million input tokens and $6 per 1 million output tokens below the long-context threshold. xAI lists higher prices for requests above 200,000 prompt tokens.
| Published pricing basis | Input / 1M | Output / 1M | Status |
|---|---|---|---|
| Grok 4.6, prompt below 200K | $2 | $6 | Published |
| Grok 4.6, prompt above 200K | $4 | $12 | Published long-context tier |
| Grok 4.7 | Not announced | Not announced | Confirm after official launch |
The reasonable planning scenarios are price parity, a premium tier because of higher serving costs, or different rates based on context length and speed. None of these is an xAI forecast.
A Practical Pre-Launch Checklist
Before the expected September 12 date, I would:
- Build a fixed evaluation set from real coding, research, engineering, and agent workflows.
- Run it against Grok 4.6.
- Record success rate, retries, tool calls, latency, token usage, and total cost.
- Keep model selection configurable instead of hard-coding a provisional Grok 4.7 ID.
- Monitor the xAI release notes.
- After launch, verify context limits, modalities, reasoning controls, pricing, rate limits, and rollout scope.
- Replay the same tests before moving production traffic.
A unified multi-model API such as CometAPI can be useful when I want to compare providers without changing the integration pattern, but I would still verify the live model ID, returned model version, pricing, and response behavior before migration.
What Needs to Happen for This to Be a Real Launch?
Four things would turn the current countdown into a verifiable product release:
- An official xAI release post
- Documentation for context, modalities, and reasoning controls
- Final API pricing and model identifiers
- Reproducible benchmark or production evaluations
The important question is not whether 2.1T parameters sounds impressive. It is whether Grok 4.7 completes difficult engineering and agent tasks more reliably, with acceptable latency and a better cost per successful outcome than Grok 4.6.
FAQ
When is Grok 4.7 expected to release?
Musk’s September 2 ten-day countdown points to approximately September 12, 2026. That is an inferred target, not a separately published xAI calendar date.
Has Grok 4.7 launched?
It has been publicly teased and announced, but xAI has not yet published a complete official API and model documentation release.
Is it a 2.1 trillion parameter model?
Musk has described Grok 4.7 as roughly 2.1T parameters. xAI has not published architecture details confirming active parameters or routing.
Will it outperform Grok 4.6?
Musk has claimed a substantial improvement, but there is no official Grok 4.7 benchmark table yet. I would treat that claim as unverified until reproducible results are available.
Will it be available through CometAPI?
A Grok 4.7 tracking page exists, but final availability, pricing, identifier, and supported formats should be confirmed after the official launch.
Bottom Line
Grok 4.7 now has a concrete expected date: approximately September 12, 2026. The other major public signals are a roughly 2.1T parameter count, improved token efficiency, somewhat slower serving, and supplemental training involving substantial SpaceX company data.
Those claims are specific, but they are not a model card, benchmark suite, or API contract. I would keep Grok 4.6 as the measurable baseline, prepare evaluations using real workloads, and wait for confirmed documentation and production access before changing deployment or budget decisions.
Top comments (0)