Grok 4.7’s Token Use and the Claims Around Its Release

Theo compares Elon Musk’s earlier predictions for Grok 4.7 with selected benchmark results and token counts.

TBTheo Browne登壇者 · T3
チャンネル
Theo - t3․gg
公開日
2026年9月24日
動画
0:31
読了時間
1 分
スライド
1
原文
英語
YouTube で開く
スクロールすると動画は右下に小さくなって再生を続けます。字幕は閲覧言語に合わせて切り替わります。
閲覧言語2 言語で読めます
この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。
要約

30 秒でわかる

Theo Browne challenges Elon Musk’s prediction that Grok 4.7 would outperform 4.6 and use tokens more efficiently. He cites selected benchmark comparisons and a per-task token count, but the short video does not provide enough methodology to establish a universal performance or cost comparison.

  1. 1The predictionTheo recalls Musk’s claim that the new model would exceed existing models.
  2. 2The efficiency claimHe challenges the prediction that Grok 4.7 would use tokens more efficiently than 4.6.
  3. 3A selected comparisonHe cites about 38,000 tokens per task for 4.6 x-high and 81,000 for 4.7, without detailing the full test conditions.

ポイント

  1. Musk had predicted that Grok 4.7 would improve on 4.6 and have better token efficiency.
  2. Theo says 4.7 scored lower than 4.6 on some benchmarks and used more tokens per task in a comparison he cites.
  3. A token-count comparison alone does not establish cost or performance across all workloads.
全文

チャプターごとに整えた全文を読む

文字起こしのみ
01

Grok 4.7 expectations and results

Theo compares the expectations set before release with selected results. He argues that the token-use figures do not match the earlier efficiency prediction.

Elon Musk had been promoting Grok 4.7 for more than a month, saying it would exceed current models. I find it striking that, in the benchmarks I cite, it scores below Grok 4.6 on several tests. That is a comparison of selected benchmarks, not a claim that 4.7 is worse on every task.

Musk’s prediction before release
スライド 1 / 1Musk’s prediction before releaseThe displayed post predicts better token efficiency and slower serving for Grok 4.7.

Musk also predicted that 4.7 would be better in every way except serving speed and would use tokens more efficiently. I dispute that prediction: I cite about 38,000 tokens per task for Grok 4.6 at x-high and 81,000 for 4.7. I describe this as roughly twice the cost, but the short does not give enough pricing or test details to establish a general cost ratio or intent to mislead.

同じチャンネルの記事

スライド 5 枚38:47EN
Theo - t3․gg· 2026年10月28日Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.コーディングエージェントエージェント工学AI cost & performance+2
スライド 5 枚36:07EN
Theo - t3․gg· 2026年10月27日Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performanceコーディングエージェントInference+1
スライド 5 枚30:37EN
Theo - t3․gg· 2026年10月26日Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skillsコーディングエージェントCode review & verification+2
スライド 2 枚0:43EN
Theo - t3․gg· 2026年10月23日Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
スライド 6 枚29:22EN
Theo - t3․gg· 2026年10月22日Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
スライド 4 枚31:13EN
Theo - t3․gg· 2026年10月20日Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.コーディングエージェントDeveloper productivityHuman-AI Collaboration+1