Skip to content
Menu

Models2 min read

Claude Fable 5 and Mythos 5: two names, one model, a safety fork.

Anthropic shipped Mythos-class intelligence as Fable (GA, safeguarded) and Mythos (trusted cyber/bio). Same substrate, different stop conditions, $10/$50, then a June access freeze and July 1 restore. Capability and permission are now separate SKUs.

A single circular model engine branches into a mesh shield and a keyed access door. The canonical Prepare crew member inserts a key into the lower door.

What happened?

On 9 June 2026, Anthropic shipped Claude Fable 5 for general use and Claude Mythos 5 for a tight circle of cyber defenders and infrastructure partners (Project Glasswing), with biology access planned under trusted programs later.

They are the same underlying Mythos-class model. The fork is product policy, not a second training run: Fable keeps external classifiers and fallbacks that route some cyber/bio-shaped queries to Opus 4.8; Mythos lifts those safeguards in scoped domains. Anthropic’s naming note is explicit, fabula vs mythos, the story you tell vs the unprotected substrate.

List price: $10 / MTok input, $50 / MTok output for both, under half of Mythos Preview. Capability claims are long-horizon first: Stripe-style multi-month migrations compressed into days, Hebbia finance SOTA, vision-only Pokémon FireRed, file-memory gains on long games, and Mythos-side drug-design / genomics loops with heavy tool use.

Access was not smooth. Public Fable/Mythos access was suspended around 12 June under US export/control pressure, then restored 1 July. That pause is part of the story, not a footnote: the frontier model and the policy layer now ship on the same release train.

Why this is interesting

  • Safety as product SKU: One weights stack, two commercial surfaces. “Safe enough for GA” is no longer only RLHF inside the net; it is a classifier gate with known false positives (Anthropic: under 5% of sessions on average, still non-zero pain for real work).
  • Mythos is the honest cyber story: Glasswing and trusted access admit what GA cannot: peak cyber capability is a governed resource, not a chat default. That collides with defender workflows that need ugly tokens (see ExploitGym / HF).
  • Long-horizon is the pitch: Benchmarks matter; the customer quotes that matter more are multi-day engineering and knowledge jobs. Fable is sold as the model that stays useful when the task stops fitting in one prompt.
  • Price signals scarcity theater: $10/$50 is expensive relative to open 3T-class APIs that followed weeks later, cheap relative to prior Mythos Preview. Capacity staging on subscriptions (included window, then credits) shows demand management is part of the release.
  • Judgment stays outside the model: Choosing Fable vs Mythos, when to accept fallback, when to move work to open weights or VPC, that is operator policy. The model does not choose its own containment level in production; the buyer does.

Bottom line

Fable/Mythos is the clearest Western statement yet that frontier capability and deployment permission are separable products. Same intelligence substrate; different stop conditions. Everything that followed in July, Sol GA, open K3/Qwen pressure, eval breakouts, lands on that fork.

5 sources. Each opens the original page.

Give a small team the reach of a large one

AI agents and intelligent software, connected to your business and supported after launch.