Paul Graham on AI in 2031: If Models Improve on Fable Like Fable Improved on GPT-3
Paul Graham's July 2026 X post imagines 2031 models leapfrogging Fable the way Fable leapfrogged GPT-3. We unpack the thought experiment, skeptical replies, GPT-5.6 benchmarks, S-curve debates, and what to plan for.
On July 7, 2026, Paul Graham posted a one-line thought experiment that hit X's trending news card — 173 posts, widespread quote-tweets, and a familiar split between awe and skepticism:
"Imagine what it will be like if 5 years from now models have improved on Fable as much as Fable has improved on GPT3."
He was quoting Jared Friedman (@snowmaker, YC partner): "Fable is so insanely good. Deserves the hype."
The post is not a forecast. It is scenario planning by analogy — if the last leap was that large, the next leap might be incomprehensible. The replies are where the useful argument lives: power users who are disappointed at $200–500/day spend, researchers who think two years not five, economists who want cheaper Fable not god-model 2031, and philosophers asking what "as much improvement" even measures.
This post unpacks the thread for builders — without treating PG as a prophet or the skeptics as Luddites.
TL;DR — the debate in one table
Camp
Representative reply
Core claim
PG / Friedman
"Imagine 2031…" / "insanely good"
Another GPT-3→Fable-class discontinuity is imaginable
Power-user skeptic
0xSero (3 weeks on Fable)
Too expensive, downgrades, still hits walls; Opus+GPT-5.5 more reliable for ML
Paying subscriber skeptic
CryptoKaleo ($200/mo Max)
GPT-5.5 x-high ≥ Fable Max on accuracy — disappointment at price
Accelerations
Derya Unutmaz
2 years, not 5, for comparable progress
Recursive boost
Kevin Bryan
AI helps build better AI — baseline should exceed historical rate
Karpathy's English-as-programming arc is the same story in developer language: GPT-3 made prompts interesting; Fable-class models made repos the runtime.
The leap is not "smarter autocomplete." It is autonomous knowledge work — planning, tool use, verification, iteration — at a quality tier that changes what a solo founder or small team can ship in a week.
Rough calendar math: ~6 years from GPT-3 (May 2020) to Fable 5's broad availability (2026). PG's 5-year forward frame lands around 2031.
Why the hype thread met disappointed power users
Trending news amplifies the peak experience. Heavy-user replies document the distribution:
0xSero — three weeks in
After tinkering with Fable for three weeks, the poster listed five bullets:
Too expensive for what it delivers
Too prone to downgrading (model routing / tier surprises)
Still hitting walls on hard tasks
Still a marvel of engineering
Best model to talk to — but maybe shiny-object syndrome; Opus + GPT-5.5 advisor completed ML work more reliably in Claude Code
Bottom line: "Would be nice to have but I'm not spending $500+ in a day."
CryptoKaleo — $200/mo Anthropic Max
Another Max subscriber ran Fable on Max effort for days and found GPT-5.5 x-high as accurate or more capable — frustration that pre-release hype did not match sustained billing reality.
explainx.ai read: These are not contradictions of Jared Friedman's YC-founder use case. They are routing and economics failures for specific workflows — exactly why multi-model stacks (Fable plan → GPT debug → GLM loops) went viral the same week.
The bull case — faster than five years
Derya Unutmaz: two years, conservative
"We will see as much advancement in 2 years. There will be more AI progress in the next two years than in the past 5 years, and that's being conservative."
The 2031 surprise might be Fable-class at GPT-3 prices, not god-tier at Fable prices.
The caution case — S-curves and definitions
Jeff Huber: where on the S-curve?
"very unclear where on the S curve we lie..."
Scaling-law era assumed smooth log-linear gains. Agent-era gains are lumpy — tool ecosystems, context length, scaffolding, and safety classifiers matter as much as pretraining FLOPs. You can be mid-curve on benchmarks and early-curve on reliability.
Stefan Schubert: what counts as "the same improvement"?
"we don't quite know what 'as much improvement as GPT3->Fable' means in practice"
Will 2031 beat Fable on all of these, or only on raw reasoning while economics commoditize? PG's sentence does not specify — planners must.
GPT-5.6 — the near-term datapoint in the thread
am.will cited an early benchmark placing GPT-5.6 ~12% above Fable 5 (benhylak thread — the quoted post was unavailable at capture time; treat as unverified until reproduced).
Official published splits today look more task-dependent than a clean 12% universal lead:
Near-term story: gap closing on agentic terminals; Fable still dominant on several coding leaderboards. That is not yet a second GPT-3→Fable discontinuity — it is frontier convergence.
Three scenarios for 2031 (if you are planning orgs)
Scenario A — PG literal (another discontinuity)
2031 models make Fable feel like GPT-3 feels today: multi-day autonomous projects, negligible human touch on routine software, new science workflows. Implication: hire for orchestration and verification; shrink pure execution headcount in commoditized tiers.
Scenario B — Petersen commodity (same tier, 100× cheaper)
Intelligence plateaus near 2028 Fable-class; price and latency collapse via open weights and efficient MoE. Implication: competitive advantage is distribution and domain data — not model access. Matches AI bubble maturation thesis.
Scenario C — Huber S-curve (lumpy slowdown)
Benchmark gains continue; reliability and economics frustrate daily drivers — echoing July skeptics. Implication: multi-model routing and eval investment beat frontier fanboyism. Mental health and agent burnout stay relevant.
explainx.ai default for builders: plan A-level capabilities on B-level economics while building defenses for C-level friction.
What to do this quarter (not 2031)
Paul Graham's post is a morale and imagination tool for founders. Operationally, the July thread suggests:
Run your own eval — Fable vs GPT-5.5 x-high vs GLM-5.2 Max on your repo (Kilo-style planning tests are templates, not gospel).
Cap daily spend — skeptics citing $500/day are not outliers on Max loops.
Model-agnostic harness — Claude Code, OpenCode, Pi, Cline; swap backends as pricing shifts.
Separate plan vs loop models — the muratcan stack pattern from the GLM adoption thread.
Watch GPT-5.6 GA — if 12% gains reproduce broadly, revisit Fable-only contracts; if not, commodity open weights win loops.
Thread summaries and benchmark deltas reflect July 7, 2026 X discourse. Paul Graham's post is speculation, not a product roadmap from Anthropic or OpenAI. Verify model scores and pricing on your workloads before budget or hiring decisions.
