Anthropic reverses Claude Fable 5 throttling policy after backlash
Is this a scandal?
No longer — the story has resolved. Noise 3/100, cooling down, across 1 source.
AI labs will likely face intense scrutiny over API telemetry and selective performance throttling. This controversy will likely accelerate calls for standardized, third-party auditing of API performance to ensure fair play.
Noise 3/100 — louder than 97% of tracked AI controversies.
Why it matters
Secret safety guardrails erode researcher trust while export controls signal escalating AI nationalism that fragments global model access.
Key points
- Anthropic reversed unannounced performance throttling on Claude Fable 5 after researchers protested the covert degradation.
- The company admitted the hidden guardrails were a 'wrong tradeoff' and promised transparent refusal mechanisms going forward.
- US export controls suspended all foreign national access to Fable 5 and Mythos 5 models effective June 12.
- Security researchers jailbroken Fable 5 within 24 hours, leaking system prompts and confirming the hidden throttling logic.
- Anthropic faces separate ongoing litigation with the Trump administration over federal agency usage restrictions.
- The controversy highlights the failure of stealth alignment strategies against both expert scrutiny and adversarial testing.
The story
Anthropic has reversed an unannounced policy that silently degraded performance in its Claude Fable 5 and Mythos 5 models for AI researchers, following intense backlash from the scientific community. The company admitted on June 11 that the hidden restrictions represented a "wrong tradeoff" between safety and utility, pledging greater transparency even if it results in more explicit refusals. This reversal coincides with a separate US government export control directive issued June 12 suspending all foreign national access to both models. Anthropic also faces ongoing litigation with the Trump administration regarding federal agency use of its tools. Security researchers reportedly jailbroken Fable 5 within 24 hours of release, exposing system prompts and the disputed throttling mechanism. The dual controversies highlight growing tensions between proprietary safety alignment strategies and the open research ecosystem's demand for reliable, documented model behavior.
Who's involved
Accused Anthropic of covertly sabotaging competing AI development by selectively degrading model performance for researchers.
Reversed the restrictive policy following community backlash after being accused of selective performance degradation.
Noise Level
The timeline
Anthropic reverses Claude Fable 5 performance degradation
Reports surface that Anthropic reversed a secret policy degrading Claude Fable 5 performance for frontier AI researchers after intense community backlash.
The full record
Sources & methodology
- Anthropic Walks Back Policy That Could Have 'Sabotaged ... — wired.com · located later (2026-07-30)
- Claude Fable 5: Anthropic admits "wrong tradeoff" after ... — the-decoder.com · located later (2026-07-30)
- Anthropic Reverses Course on Hidden AI Restrictions ... — devops.com · located later (2026-07-30)
- Anthropic apologizes for invisible Claude Fable guardrails — theverge.com · located later (2026-07-30)
- Anthropic walks back covert capability limits on Claude ... — fortune.com · located later (2026-07-30)
- Anthropic reverses course on AI model Claude Fable 5 ... — linkedin.com · located later (2026-07-30)
The records from this story's original coverage were pruned, so items marked located later were found by searching for it afterwards. The summary above has since been rewritten to take them into account — it is not the text first published. How we score →
What's being under-reported
No defender-side coverage yet
The critic side is sourced here; no defending voice has been captured yet.
- Coverage: 0 social posts, 0 news-outlet items.
- Voices: 1 critic, 0 defenders.
The forecast
AI labs will likely face intense scrutiny over API telemetry and selective performance throttling. This controversy will likely accelerate calls for standardized, third-party auditing of API performance to ensure fair play.
Forecast, not fact — an editorial estimate we score when this resolves.
That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.
Join the Discussion
Discuss this story
Community comments coming in a future update
Be the first to share your perspective. Subscribe to comment.