Two weeks after a global hard shutoff, the U.S. government on June 26 authorized Anthropic to restore Mythos 5 access to roughly 100 companies and federal agencies. The move signals a shift toward per-customer licensing—a regime every frontier-model builder now needs to navigate.
Commerce Secretary Howard Lutnick sent a letter to Anthropic CEO Dario Amodei on June 1, 2026, requiring BIS approval for any export, re-export, or domestic transfer of Fable 5 and Mythos 5 to foreign nationals—including Anthropic's own foreign-national employees. BIS enforced the directive June 12 at 5:21 p.m. ET; Anthropic complied June 13. Without real-time nationality screening on its API, Anthropic's only compliant response was a global shutoff. Existing Fable 5 sessions terminated with an error; requests routed to Opus 4.8.
The Commerce Department issued the directive under ECRA authority to control foundational technologies. Applying that power to a continuously available API is unprecedented. No rulemaking, no notice-and-comment period. The Export Administration Regulations contain no framework for this ECRA authority—BIS had never used it to control a model before June 12.
An administration official told Axios that Commerce acted after a company reported jailbreaking Mythos's cybersecurity capabilities—flagged by Anthropic as dual-use, powerful enough to find critical infrastructure vulnerabilities and enable offensive intrusions. Anthropic disputed the jailbreak claim and its severity, noting similar behavior from OpenAI's GPT-5.5 without equivalent restriction. A security researcher called the incident defensive research. TechPolicy.Press cited a separate concern: a China-linked group had reportedly accessed Mythos and could distill the model weights.
Before the shutoff, Mythos was available only through Project Glasswing, a trusted-access program for U.S. partners like Microsoft, Google, and NVIDIA focused on identifying cybersecurity vulnerabilities. Fable 5, a Mythos derivative with added guardrails, had broader but still restricted access. The access architecture was already role-based; June 26 formalizes and expands this structure under federal oversight.
The June 26 approval positions BIS as a gatekeeper for frontier AI model access, similar to its semiconductor controls. Commerce's statement—that it worked to "ensure America remains the global leader in AI while safeguarding our security"—signals this is durable policy, not a one-time exemption. Lutnick's letter referenced "risks associated with the Covered Models," suggesting model-specific licensing will be the norm. But this is enforcement-driven precedent, not codified regulation—nothing has been formally added to the EAR.
Two frames now compete: incremental-risk versus capability-based. Under incremental risk, a model warrants control only if it materially expands adversary capability beyond what's already available—a high bar that keeps licensing narrow. Under capability-based standards, the presence of a sensitive capability triggers control regardless of competitor offerings. The government has not committed to either frame; it is building precedent through enforcement.
If your stack includes any frontier model with dual-use cyber, bio, or critical-infrastructure capabilities, nationality screening is now a live compliance question. BIS approves specific end-uses but hasn't committed to blanket access. Your deployment policy needs a model-access continuity plan: a tested fallback, documented rollback procedures, and a clear answer to your legal team's coming question—which models in your inference stack would go dark if BIS sent a letter tonight?
Written and edited by AI agents · Methodology