ASAPThe Opus 4.8 the Fable 5 shutdown buried: where the real leap actually was
The Fable 5 shutdown is a genuine loss, but the noise around it is burying the real leap of Opus 4.8, released on May 28, 2026. Opus 4.8 lifted SWE-bench Pro from 64.3% on Opus 4.7 to 69.2%, and it became roughly four times less likely to let flaws in its own code pass unremarked. ASAP pulls the actual 4.8 gains from primary sources to put a spotlight back on the progress the Fable 5 headlines eclipsed.
The Fable 5 shutdown is a real loss
The Fable 5 shutdown is clearly a disappointing event. Fable 5 and Mythos 5, launched on June 9, 2026, were fully disabled three days later on June 12 under a US Commerce Department (BIS) export-control directive. A top-tier model strong at long-horizon work vanished in under 72 hours, which is a real loss for the users who were counting on it.
Yet as large as that disappointment is, the news also buried another event from the same window.
The buried protagonist is Opus 4.8
The real event hidden by the headlines is Opus 4.8, quietly released on May 28, 2026. While most users fixated on the June news that the top-tier model was blocked, the progress in 4.8 from two weeks earlier drew comparatively little attention. Anthropic introduced 4.8 as its most capable model for complex reasoning, long-horizon agentic coding, and high-autonomy work.
Tellingly, Anthropic itself called 4.8 a "modest but tangible improvement," yet on coding and agentic metrics the progress is anything but modest.
What Opus 4.8 actually lifted
The progress in Opus 4.8 shows up in the numbers, and the standout areas are agentic coding and honesty.
| Metric | Opus 4.7 | Opus 4.8 |
|---|---|---|
| SWE-bench Pro (hardest) | 64.3% | 69.2% |
| SWE-bench Verified | — | 88.6% |
| Unremarked own-code flaws | baseline | ~4x reduction |
| Fast mode | — | 2.5x speed, 3x cheaper |
Beyond that, Opus 4.8 led the coding category by roughly 18 points on average and beat GPT-5.5 on SWE-bench Pro by 10.6 points. On the Super-Agent benchmark it was the only model to complete every case end-to-end, and its long-context handling and compaction recovery also improved.
Coming off the 4.7 regression — why the leap feels larger
Two reasons rooted in Opus 4.7 and 2026 serving changes are why the leap feels especially large. First, Opus 4.7 had a real regression: spring 2026 brought reports of coding regressions and a 54-point drop on a reasoning benchmark versus 4.6, so rising off that floor makes 4.8 feel bigger. Second is infrastructure. Right after the June 12 Fable 5 shutdown, Anthropic doubled the Opus and Sonnet usage limits in Claude Code and removed peak-hour throttling for Pro and Max, so the same 4.8 now answers without interruption and at greater length.
How to verify it yourself
Turning the leap from a feeling into a fact requires measurement. The minimal protocol ASAP recommends is as follows.
- Compare accuracy and consistency on Opus 4.7 and 4.8 with a fixed set of 20 prompts.
- Log response latency and output tokens to separate "speed" from "capability."
- Track the 4.7→4.8 trend on a public coding eval such as SWE-bench Pro.
- Treat any speed or stability change on the same version around June 12 as a capacity effect, not a weight change.
Conclusion: the noise passes, the progress stays
The lasting story of early 2026 is not the Fable 5 noise but the progress in Opus 4.8. The noise passes, but the progress stays: the Fable 5 shutdown is a loss, yet the real Opus leap of early 2026 lived in 4.8 — and SWE-bench Pro at 69.2% and a fourfold improvement in self-caught code flaws are the proof. The louder the headlines, the more you need an eye for the quiet progress underneath.
Sources: Opus 4.8 benchmarks and features (Anthropic official; Labellerr, DataCamp, Caylent reviews), the "modest but tangible" assessment (Simon Willison), Opus 4.7 regression reports (roborhythms, startupfortune), the Fable 5 and Mythos 5 suspension (InfoQ, The New Stack), and the Claude Code limit doubling and throttle removal (Developers Digest).