Project Glasswing: why Mythos 5 stays behind closed doors
Claude Mythos 5 did not launch as a public API model. Anthropic positioned it as the restricted sibling of Claude Fable 5: the same underlying model, but with cyber safeguards lifted for vetted defensive users. Access runs through Project Glasswing, the company's program for government, critical-infrastructure, and cyberdefense partners.
The design choice explains the Fable 5 launch. Anthropic wanted to make Mythos-class capability broadly useful for coding, research, and difficult knowledge work, while limiting direct access to the model's strongest cybersecurity behaviors. Fable 5 is the public version of that trade-off: same intelligence class, real-time cyber and bio classifiers, and an opt-in fallback to Opus 4.8 when a session is blocked.
What Project Glasswing is for
Project Glasswing exists for authorized cyberdefense. Anthropic has described it as a collaboration with the US government and infrastructure providers, created after Claude Mythos Preview showed capabilities that the company was unwilling to release to the public. In the program, vetted partners use the model to find and fix high-impact vulnerabilities rather than to expand offensive access.
The predecessor, Claude Mythos Preview, was reported to have helped partners identify more than 10,000 high- and critical-severity zero-day vulnerabilities. That result became the argument for restricted deployment: the model was too useful to leave unused, but too capable to serve without controls.
How Mythos 5 differs from Fable 5
The most important point is that Mythos 5 is not marketed as a larger public model. It is the same underlying system as Claude Fable 5 with some cyber safeguards lifted. For everyday builders, that means Fable 5 already represents the Mythos-class jump: long-horizon agentic work, 1M context, 128K output, always-on adaptive thinking, and the launch benchmark gains over Opus 4.8.
| Capability | Claude Fable 5 | Claude Mythos 5 |
|---|---|---|
| Underlying model | Mythos-class | Mythos-class |
| Public API access | Yes | No |
| Cyber safeguards | Real-time classifiers | Lifted in approved areas |
| Primary users | Developers, teams, enterprises | Vetted cyberdefense partners |
| Best public alternative | Use claude-fable-5 | Not generally available |
What builders should do
Most teams should treat Fable 5 as the available Mythos-class model and design around its safety behavior. If your workload sits near the cyber boundary, enable the fallbacks beta where available, log refusal categories, and keep Opus 4.8 available for workloads requiring zero data retention or predictable safety behavior. If you are doing authorized security research and believe you qualify for restricted access, the relevant route is Anthropic's official Project Glasswing process, not the public Claude API.