Dario Amodei Rejects the Open-Weights Ban Anthropic Never Proposed

Dario Amodei used a public statement this week to correct a claim that keeps circulating about his own company: “Anthropic has never advocated for a ban on open-weights models.” The correction matters because it reframes what Anthropic is actually proposing. Instead of blanket restrictions, Amodei separates two distinct risks — authoritarian governments building more powerful models than the US for military dominance, and any sufficiently powerful model, open or closed, being misused for cyberattacks or biological threats — and argues for three targeted measures instead: tighter chip export controls, cracking down on industrial-scale model distillation, and mandatory safety testing regardless of license. He also pushes back on part of an open letter circulating on the topic, agreeing openness carries real benefits but disputing that it automatically improves safety, citing offense-defense asymmetries in biological risk.

The tension Amodei is navigating shows up concretely elsewhere in the same week’s news. VIDRAFT’s Aether-7B, a fully transparent Korean “sovereign” model released under Apache-2.0 with published data recipes and training logs, is exactly the kind of national open-weights effort his “authoritarian government” framing gestures at — except built by an ally, for research reproducibility, not military dominance. And Hugging Face’s own incident-response writeup makes his “openness carries real benefits” concession concrete rather than abstract: after its July 16 security breach, the company’s frontier commercial-API models refused to help because their safety guardrails couldn’t tell responders from attackers, so the team ran forensic analysis on GLM 5.2, an open-weight model, entirely on its own infrastructure instead.

That’s the actual argument buried under the ban/no-ban framing: openness and closedness both carry asymmetric risks depending on who’s using them and for what. Amodei’s proposed fix — chip controls plus mandatory testing, not weight restrictions — is a bet that the access point worth regulating is compute, not code.