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