summree
Claude Fable 5 Is NERFED?! After Export Ban? The Truth...
Anthropic
WorldofAI

Claude Fable 5 Is NERFED?! After Export Ban? The Truth...

⏱ 12 min video · 2 min read6 Jul 2026
TL;DR
Claude 4 Fable 5 (Claude's flagship model) was temporarily suspended due to US government export restrictions, then redeployed by Anthropic with stricter safety classifiers. This video investigates whether the re-released model has been genuinely nerfed or whether benchmark score drops are artifacts of the new safety system routing requests to Claude Opus 4.8 instead.
Key points
1
Anthropic's Apex Sway benchmark shows the July re-release of Claude Fable 5 scored 54.8% vs 65.5% in June — roughly a 10-point drop — but observability scores fell hardest, from 69.67% to 50.33%.
2
The new safety classifier automatically reroutes flagged requests to Claude Opus 4.8, meaning some benchmarks may be inadvertently measuring Opus 4.8 rather than Fable 5 itself, artificially deflating scores.
3
Chatbot Arena collected thousands of votes across text, vision, documents, code, and agent evaluations and concluded scores are largely consistent before and after redeployment, with only a ~20-point drop in front-end coding within statistical confidence intervals.
4
Anthropic acknowledged the stricter classifier intentionally over-flags benign coding and debugging tasks to maintain safety margins around cybersecurity-related requests, and the classifier is wording-sensitive — neutral phrasing is less likely to trigger a reroute.
5
Starting July 7, 2026, Fable 5 will no longer be included in Anthropic paid plans and will switch to a credit-usage billing system.
Actionable insights
When running benchmarks on Fable 5, explicitly verify that the safety classifier has not triggered a fallback to Opus 4.8, or your results will measure the wrong model.
Structure prompts in neutral, natural coding language rather than explicitly mentioning vulnerability scanning or cybersecurity tasks to reduce the chance of triggering the safety reroute.
Use markdown files for plans and preferences to give Fable 5 proper context and reduce unnecessary usage consumption caused by safety-triggered fallbacks mid-project.
Treat community benchmark claims of massive regression with skepticism unless the benchmark provider confirms it isolated Fable 5 responses from Opus 4.8 fallbacks.
Budget for credit-based usage of Fable 5 from July 7, 2026 onward, as paid plan subsidies are being removed.
Notable quotes

The bigger story isn't Fable 5 got destroyed — it's that Anthropic added a much stricter safety layer and distinguishing between actual model capability and safety triggered fallbacks is going to be incredibly important when interpreting different sorts of benchmark results moving forward.

People claim that it has been nerfed but they don't know how to actually work around all these safeguards.

It basically breaks up your project from starting off with Fable 5 and then it makes you route it to the Opus 4.8 to actually accomplish the next bit of your task.

Worth watching?
⏭️
Worth watching the full video?
The key findings — benchmark methodology flaws, the safety classifier rerouting issue, and the billing change — are all captured here; skip the video unless you want the creator's personal workflow commentary.
Topics
AI & TechAnthropic

Explore more summaries on these topics →

Saved you some time? The creator still deserves a like.

Watch on YouTube →
More like this

Want this for your own channels?

Add the channels you follow. Every new video summarised and in your inbox the moment it drops. From £4/month.

Try it free