Back to feed
Simon Willison·

Initial impressions of Claude Fable 5

Signal
82
Hype
25
In three linesAnthropic releases Claude Fable 5 and Claude Mythos 5 with 1M token context window, 128k max output tokens, January 2026 knowledge cutoff. Fable 5 includes strict safety guardrails; Mythos 5 without safety classifiers. Pricing: $10/M input, $50/M output (2× Opus 4.5-4.8). Willison reports strong performance after 5.5 hours of testing.

## Claude Fable 5 & Mythos 5: What the Numbers Actually Say

### 1. The immediate context

Anthropic is releasing two distinct models simultaneously — Fable 5 and Mythos 5 — with identical capability architectures but opposing deployment philosophies. Fable 5 ships with strict safety classifiers, aggressive enough that Anthropic built an automatic fallback mechanism directly into the API: if a request triggers a refusal, the system can route to an alternative model without developer intervention. Mythos 5 runs without those classifiers. This is an explicit product bifurcation based on user risk profile, not a simple pricing tier.

The January 2026 knowledge cutoff deserves attention: it sits several months ahead of most competing models currently in production, providing a measurable factual advantage on queries about recent events.

### 2. Pricing structure and its implications

$10/M input tokens, $50/M output tokens — exactly double Claude Opus 4.5/4.6/4.7/4.8. For calibration: GPT-4o runs around $2.50/$10, Gemini 1.5 Pro around $1.25/$5 at standard volumes. Fable 5 positions itself at the absolute premium end of the market, alongside GPT-4.5 and OpenAI's o3 offerings.

Key point: no surcharge for long context windows. With 1M tokens of context available, this changes the economic calculus for RAG-free use cases — ingesting an entire codebase or document corpus without vector infrastructure becomes financially predictable. At $10/M input, a full 1M-token context costs $10 per call, which remains high but is linear and transparent.

The 128,000 maximum output tokens are significant: that's 4× the standard output limit of most models (32k). For long code generation, structured reports, or exhaustive synthesis, this higher ceiling reduces the need for prompt chaining.

### 3. The factual knowledge test: a real signal

Simon Willison's test querying his own open source projects illustrates a concrete qualitative difference. Opus 4.8 produces a short list (4 main projects) with an explicit uncertainty disclaimer. Fable 5, on the identical query with the same typo, apparently generates a substantially more exhaustive and dated list — what Willison describes as the "big model smell": a sense of superior knowledge density.

This isn't a synthetic benchmark. It's a factual recall test on a subject where the evaluator is the domain expert. The gap between the two responses points toward a significantly larger trained knowledge capacity in Fable 5.

### 4. Who loses in this configuration

**Existing Opus 4.x users**: migration means an immediate cost doubling. For high-volume pipelines (millions of tokens/day), moving to Fable 5 is non-trivial without demonstrable quality ROI.

**RAG solution providers**: if a 1M-token context model with no surcharge can replace complex retrieval architectures for certain use cases, the value proposition of vector indexing layers shrinks. Not elimination, but scope compression.

**Competitors in the "no guardrails" segment**: Mythos 5 directly attacks the market for uncensored models (Mistral, certain Llama deployments) with frontier-level capabilities. This puts direct pressure on the argument that "open-weight models are necessary for sensitive use cases."

**Anthropic's own safety teams**: the automatic fallback-on-refusal mechanism is an operational concession. It implicitly acknowledges that overly aggressive classifiers degrade developer experience enough to require built-in workaround infrastructure.

Speed is flagged as a weakness by Willison after 5.5 hours of testing — "slow" is his word. For real-time interactive applications, this is a non-trivial architectural constraint. Fable 5 appears optimized for output quality, not latency.

Read source
Your take?
ClaudeAnthropicBenchmarks

Summary generated by Claude — human-verified