cd /news/ai-safety/anthropic-walks-back-policy-that-cou… · home topics ai-safety article
[ARTICLE · art-24297] src=simonwillison.net ↗ pub= topic=ai-safety verified=true sentiment=· neutral

Anthropic Walks Back Policy That Could Have ‘Sabotaged’ AI Researchers Using Claude

Anthropic reversed a policy that would have allowed its Claude AI model to silently limit effectiveness for researchers working on frontier AI development, following widespread backlash. The company acknowledged it made "the wrong tradeoff" by implementing invisible safeguards that could have sabotaged users without their knowledge. Anthropic is now making those safeguards visible, with flagged requests falling back to a less capable model and providing clear refusal reasons.

read1 min publishedJun 11, 2026

Anthropic Walks Back Policy That Could Have ‘Sabotaged’ AI Researchers Using Claude “We’re changing Fable 5’s safeguards for frontier LLM development to make them visible.” Anthropic said in a statement to WIRED. “We made the wrong tradeoff and we apologize for not getting the balance right.”

There's been a huge outcry about Anthropic's policy, tucked away in their system card, that Claude Fable/Mythos would identify "requests targeting frontier LLM development" and "limit effectiveness" without notifying the user.

It's good news that they're dropping the invisible aspect of this. It would be a whole lot better of they dropped this category of refusals entirely.

Update: More details from @ClaudeDevs on Twitter: We’re rolling out changes to make Fable 5’s safeguards for frontier LLM development visible.

Starting this week, flagged requests will visibly fall back to Opus 4.8—the same as our safeguards for cyber and bio. You will see this every time it happens. On the API, any flagged requests will return a reason for their refusal (coming to server-side fallback in the next few days).

We wanted to deploy Fable 5 to our users quickly and safely. Visible safeguards can be probed, so they have to be robust, which takes time to get right. Invisible safeguards can be targeted more narrowly, allowing us to ship quickly with very few false positives. We went with invisible safeguards for this reason—and that was the wrong tradeoff. You should have visibility into the safeguards we have in place, and why. We’re sorry for not getting the balance right.

Via [@zeffmax](https://twitter.com/zeffmax/status/2064910040503627917)

Tags: [ai](https://simonwillison.net/tags/ai), [generative-ai](https://simonwillison.net/tags/generative-ai), [llms](https://simonwillison.net/tags/llms), [anthropic](https://simonwillison.net/tags/anthropic), [claude](https://simonwillison.net/tags/claude), [ai-ethics](https://simonwillison.net/tags/ai-ethics), [claude-mythos](https://simonwillison.net/tags/claude-mythos)
── more in #ai-safety 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/anthropic-walks-back…] indexed:0 read:1min 2026-06-11 ·