Claude Fable 5
Claude Fable 5 is Anthropic's June 2026 generally available model for demanding coding and long-horizon workflows. It remains a distinct served model, while Claude Fable 5.1 is the newer September 2026 release.
Claude Fable 5 is a key decision point for teams comparing Anthropic models on task complexity, model cost, and safety handling because it sits between ultra-high-end frontier usage and mainstream production availability.
Anthropic announced Claude Fable 5 in June 2026 and positioned it as a public model with Mythos-class capabilities under a safer public posture. Official documentation provides the model ID, context/output limits, pricing, platform availability, and a retirement date no earlier than June 9, 2027. Anthropic released Fable 5.1 in September 2026 as a separate successor rather than silently replacing this model ID.
- High-complexity coding and long-horizon codebase tasks.
- AI-assisted planning, architecture proposals, and staged implementation recommendations.
- Document-heavy and multimodal analysis with safety-sensitive output handling.
- Agentic workflows that require predictable refusal or fallback behavior under uncertainty.
Anthropic introduced Claude Fable 5 as a major public model release with official model ID, published pricing, and platform access details. It is presented as a high-capability option for coding, complex task planning, and long-form reasoning.
- Model ID and catalog entry are available through Anthropic API documentation.
- Public pricing is $10 per million input tokens and $50 per million output tokens.
- Release context aligns it with Anthropic Mythos-class capability, while retaining broader public usability.
For users choosing a model for longer autonomous tasks, the behavior expectations differ from simpler chat models: safety checks, refusal paths, and task-depth tradeoffs become part of model selection. Anthropic documents these behaviors and guidance in model and prompting references.
- Practical selection focus: quality versus cost on sustained planning tasks.
- Safety-aware fallback behavior matters for production workflows where correctness must be bounded.
- Vision input support expands use cases beyond text-only analysis.
Use the entity page when readers ask what Claude Fable 5 is, why it matters, and how it compares with adjacent frontier and coding-agent models. Use the model directory entry for structured filters and API-level metadata.
The September 2026 successor with cheaper cache reads and API migration changes.
Anthropic reference model for high-complexity production coding and comparison.
Current Opus-tier model and lower-cost comparison for difficult everyday agentic work.
OpenAI frontier coding model used as a cross-provider benchmark.
Invitation-only Mythos-tier model launched beside Fable 5.
Claude Fable 5 FAQ
Common questions about Claude Fable 5.
Is Claude Fable 5 meant for coding and agent workflows?+
Yes. Anthropic positions Claude Fable 5 for demanding coding, analysis, and long-horizon tasks, especially where quality and long-context handling are important and where safety-sensitive boundaries need to be respected.
How does Claude Fable 5 pricing compare to older Anthropic models?+
Publicly documented pricing for Claude Fable 5 is $10 per million input tokens and $50 per million output tokens. Compare this with your current task mix, token profile, and provider alternatives before choosing it as a default model.
Where can Claude Fable 5 be used?+
Claude Fable 5 is available through Anthropic API and major distribution surfaces. The public model documentation and cloud partner releases indicate deployment on AWS and related model host paths. Confirm regional availability and exact plan permissions in your runtime before production rollout.
Should I treat Claude Fable 5 and Claude Opus the same in workflow design?+
No. Fable 5 is Anthropic's highest-capability generally available tier, while Opus 5 is the lower-cost advanced option for difficult everyday coding and enterprise work. Compare task success, refusal behavior, latency, and total validated-task cost before choosing a default.