Skip to main content
Anthropic implements advanced security measures for AI safety while the U.S. Commerce Department approves Fable 5’s commercia

Editorial illustration for Anthropic adds security measure; Commerce Dept clears Fable 5 for release

Anthropic adds security measure; Commerce Dept clears...

Anthropic adds security measure; Commerce Dept clears Fable 5 for release

2 min read

The Trump administration lifted export controls on Anthropic’s Claude Fable 5 after the company agreed to add a new guardrail. The safeguard blocks any user who tries to unlock certain restricted capabilities and automatically reroutes the request to the less‑advanced Opus 4.8 model. Before the change, only queries about sensitive cybersecurity and biology were sent to Opus 4.8; now the guardrail also covers a behavior highlighted in an Amazon research paper.

In that paper, users discovered they could sidestep a restriction on Fable 5 by asking the model to fix code rather than flag security flaws. While most cybersecurity experts don’t see the workaround as a major threat, the administration’s concern sparked a showdown that briefly took the model offline. Commerce Secretary Howard Lutnick’s letter announcing the removal of the restrictions notes that Anthropic “has agreed to proactively detect and address security risks posed by the models.” The added measure gives the government a clearer line of defense while letting Anthropic keep Fable 5 in service.

Still, while Anthropic has resolved its impasse with the Commerce Department, defense secretary Pete Hegseth has told advisers there is no clear path to lift his February 28 order designating the company a supply chain risk, according to a person briefed on the matter.

Why this matters

We see Anthropic’s latest concession as a practical reminder that regulatory pressure still shapes model releases. By extending a guardrail that redirects blocked queries to the older Opus 4.8, the company has satisfied the Commerce Department’s current safety criteria, at least according to the Center for AI Standards and Innovation. Does this approach actually curb misuse, or merely shift it onto a less capable system?

The notification to users that their request is blocked is a tangible step, yet the underlying capability’s still present in Claude Fable 5. For developers, the move signals that export‑control compliance may require built‑in throttles rather than post‑hoc patches. Founders should note that clearance can be granted when safeguards are deemed “sufficiently robust for now,” implying that future revisions could reopen the debate.

Researchers must watch how the reduced‑performance fallback performs in practice; if it proves ineffective, the guardrail could be bypassed with creative prompting. Unclear whether this model will set a lasting precedent or become a temporary compromise while broader policy discussions continue.

Further Reading