Anthropic legacy frontier model
Claude Fable 5
The first Claude 5 Fable model, built for demanding reasoning and long-horizon agentic work with a 1M-token context window, 128K output, always-on adaptive thinking, and a distinctive refusal-and-fallback integration model.
- Context window
- 1M
- tokens
- Max output
- 128K
- tokens
- Input
- $10.00
- per 1M tokens
- Cache read
- $1.00
- per 1M tokens
- Output
- $50.00
- per 1M tokens
01 / Overview
What Claude Fable 5 Is
Claude Fable 5 is the original model in Anthropic’s Fable tier, introduced for demanding reasoning and long-horizon agentic work that can span many steps, tools, files, and decisions.
The First Claude 5 Model Above the Standard Opus Tier
Anthropic launched Claude Fable 5 on June 9, 2026 as its most capable generally available model at the time. It also introduced the broader Mythos-class tier: Claude Mythos 5 shares the same underlying capabilities and specifications but is available only to approved Project Glasswing customers and does not use Fable’s additional safety classifiers.
Fable 5 was designed for problems that were previously too complex, long-running, or ambiguous for earlier Claude models. Anthropic’s prompting guidance specifically highlights work that may take a person hours, days, or weeks to complete.
The model combines a 1,000,000-token context window, up to 128,000 output tokens, text and image input, always-on adaptive thinking, and tool-oriented agent workflows. Anthropic classifies comparative latency as slower, which matches its role as a premium model for difficult tasks rather than routine low-latency calls.
Today, Fable 5 remains available as an active legacy model. Anthropic recommends considering Fable 5.1 for improved performance, so Fable 5 is especially useful as a production baseline for teams already running it or evaluating what changed between the original and updated Fable generation.
- Released June 9, 2026.
- Built for demanding reasoning and long-horizon agentic work.
- 1M context window and 128K maximum output.
- Text and image input with text output.
- Active legacy model with migration path to Fable 5.1.
- Provider
- Anthropic
- Family
- Claude Fable 5
- Model ID
- claude-fable-5
- Released
- Jun 9, 2026
- Knowledge cutoff
- Jan 2026
- Input modalities
- Text, Image
- Lifecycle
- Active · legacy
02 / Long-horizon agents
Claude Fable 5 for Long-Horizon Agentic Work
Fable 5 was built around sustained autonomy: the ability to remain productive across long sequences of planning, tool use, implementation, verification, and correction rather than only generating a strong single response.
Measure Completion Over Hours, Not Intelligence in One Turn
Anthropic reports several improvements over Claude Opus 4.8 that matter specifically for agents. Fable 5 can sustain goal-directed work over extended runs, retain instructions across complex tasks, and produce first-shot implementations of difficult, well-specified systems more reliably.
It is also stronger at delegation and collaboration. An agent can dispatch parallel subagents, maintain communication with long-running subagents and peers, and coordinate their results back into the parent task.
That changes the evaluation target. For a conventional model, you may score one answer. For Fable 5, you should evaluate an entire trajectory: whether the model chooses useful tools, keeps the original goal intact, recovers from intermediate errors, avoids repetitive loops, and reaches a verifiable completion state.
Long context supports this workflow by keeping source files, plans, prior turns, tool outputs, research notes, and intermediate decisions accessible across the task.
- 01
Multiday autonomy
Sustain goal-directed work across extended runs instead of depending on a human to restart the task after each step.
- 02
First-shot implementation
Handle complex, well-specified builds with fewer iterative correction cycles when the task is within the model’s capability range.
- 03
Subagent delegation
Dispatch and coordinate parallel subagents while maintaining communication and integrating their work into the main trajectory.
- 04
Ambiguous problem solving
Navigate complex, multithreaded requests and determine useful next steps when the path is not fully specified in advance.
03 / Refusals & fallback
Safety Refusals Are Part of the Claude Fable 5 API Contract
One of Fable 5’s most distinctive integration differences is that Anthropic runs additional safety classifiers that can decline requests during input processing or response generation.
Production Integrations Need a Refusal Path
Anthropic’s documentation calls out refusal handling as a headline integration change for Claude Fable 5. A declined request can return stop_reason: "refusal", so applications should not assume every successful HTTP request ends with a normal completion.
The classifiers target areas including offensive cybersecurity, certain biology and life-sciences content, and attempts to extract summarized thinking. Anthropic also notes that benign cybersecurity or beneficial life-sciences requests can trigger these safeguards in some cases.
This means production systems should explicitly handle refusal responses. Depending on the workload, the application may show a refusal to the user, route the request for human review, or retry on another approved Claude model through a configured fallback path.
Billing rules also matter. Mid-stream refusals can bill the input and output already generated. Anthropic introduced fallback-credit behavior to avoid charging prompt-cache cost twice when a declined Fable request is retried on another model.
- 01
Detect refusal
Treat stop_reason: refusal as an explicit outcome instead of parsing it as an ordinary model answer.
- 02
Choose product behavior
Display the refusal, route to review, or retry on an approved fallback model according to the application’s policy.
- 03
Preserve context safely
Keep the prompt and relevant state available for a fallback request without silently changing user intent.
- 04
Measure refusal rate
Track how often legitimate workload classes are declined so model routing and fallback policy can be evaluated empirically.
04 / Vision & enterprise
Vision, Enterprise Workflows, and Deep Code Review
Anthropic positioned Fable 5 as more than a coding agent: it also improved difficult visual interpretation, professional knowledge work, repository-scale debugging, and complex enterprise workflows.
Stronger Inputs Matter When the Task Is Messy
Anthropic’s prompting guide highlights improved interpretation of dense technical images, detailed screenshots, and web applications. The model is trained to use tools such as bash and image cropping when visual inputs are flipped, blurry, noisy, or difficult to inspect directly.
For enterprise work, Fable 5 is intended to stay in scope across financial analysis, spreadsheets, presentations, and document-heavy tasks. That is especially relevant when a workflow requires both reasoning and artifact production rather than a short conversational answer.
The model also improves code review and debugging. Anthropic reports stronger bug-finding recall outside the cybersecurity domains covered by its safety classifiers, including searches across codebases and repository history.
These capabilities are best evaluated with complete tasks. A screenshot benchmark should include the downstream decision. A code-review benchmark should include whether the issue is actionable. A spreadsheet task should verify the resulting numbers, not only the explanation.
- 01
Dense technical vision
Interpret complex screenshots, web applications, diagrams, and noisy visual inputs with tool-assisted inspection where useful.
- 02
Enterprise analysis
Work across financial material, spreadsheets, presentations, and documents while maintaining instructions and scope.
- 03
Repository debugging
Search codebases and repository history to identify defects whose cause spans multiple files or revisions.
- 04
Complex professional output
Produce substantial artifacts and analysis when the task combines research, reasoning, structure, and domain constraints.
05 / Pricing
Claude Fable 5 Pricing
Claude Fable 5 costs $10 per million standard input tokens and $50 per million output tokens, with prompt caching designed to reduce the cost of repeatedly reused long context.
Prompt Caching Is Important for Long Agent Sessions
A long-running agent may repeatedly reuse system instructions, repository context, policy documents, research material, or other stable prefixes. Without caching, those tokens are billed as standard input each time they are processed.
Anthropic prices 5-minute cache writes at $12.50 per million tokens, 1-hour cache writes at $20 per million tokens, and cache reads at $1 per million tokens for Fable 5.
That cache-read rate is one of the clearest economic differences between Fable 5 and Fable 5.1. The newer model keeps the same $10/$50 base pricing but lowers cache reads to $0.25 per million tokens.
Batch API workloads receive a 50% discount on standard input and output. For offline evaluations, large research jobs, or bulk processing that does not require interactive latency, batching can materially change the economics.
- Standard input: $10.00 per 1M tokens.
- Output: $50.00 per 1M tokens.
- 5-minute cache write: $12.50 per 1M tokens.
- 1-hour cache write: $20.00 per 1M tokens.
- Cache read: $1.00 per 1M tokens.
- Batch API: 50% discount on standard input and output.
1M tokens · USD
- Input
- $10.00
- 5m cache write
- $12.50
- 1h cache write
- $20.00
- Cache read
- $1.00
- Output
- $50.00
Example: 20K input + 4K output
- Input cost
- $0.2000
- Output cost
- $0.2000
- Estimated uncached total
- $0.4000
06 / Context
Claude Fable 5 Has a 1M Context Window
Fable 5 provides a 1,000,000-token context window by default and supports up to 128,000 output tokens per request.
Large Context Supports Persistent Working State
The practical value of a million-token window is not simply the ability to paste a very large document into one prompt. Agentic systems accumulate state: source files, tool output, plans, intermediate findings, prior conversation turns, image inputs, instructions, and memory.
Keeping more of that state available can reduce the need for aggressive summarization and context eviction during long tasks. It can also make repository-scale coding and multistep research easier to orchestrate because the model can refer back to earlier evidence without constantly reconstructing it.
Fable 5 also supports unusually long output—up to 128K tokens. That matters for large generated artifacts, code, detailed reports, or task completions where the final deliverable itself is substantial.
Large capacity still needs discipline. More context increases cost and can introduce irrelevant material. Prompt caching, retrieval, context editing, compaction, and explicit state management remain useful even when the technical ceiling is high.
Context window
1,000,000
Max output
128,000
Long-running agent context can include instructions, source code, images, previous turns, tool results, research evidence, memory, and generated output.
07 / Thinking
Adaptive Thinking Is Always On
Claude Fable 5 always uses adaptive thinking. The model decides when and how much internal reasoning to use, while developers can influence computational intensity through the effort parameter.
Fable 5 Changed the Thinking API Contract
Unlike some earlier Claude models, Fable 5 does not allow thinking to be disabled. Passing thinking: {"type": "disabled"} returns a 400 error. Manual extended-thinking budgets with thinking: {"type": "enabled", "budget_tokens": N} are also not supported.
The default effort level is high. Lower effort can be useful for less demanding steps where evaluation shows that full compute is unnecessary.
Raw chain-of-thought content is never returned. Anthropic’s API can provide summarized thinking or omit readable thinking content depending on the thinking.display setting. In multi-turn tool loops, thinking blocks should be passed back unchanged according to Anthropic’s API requirements.
This means migration from older Claude models requires both quality testing and API compatibility testing. A prompt that worked before may still be valid, while the surrounding thinking configuration may need to change.
Routine intermediate step
Use lower effort when the action is straightforward and evaluation shows that additional compute does not improve task completion.
Difficult decision point
Use higher effort for architecture, deep debugging, ambiguous planning, or other moments that can determine the success of the entire agent trajectory.
08 / Fable 5 → 5.1
Migrating From Claude Fable 5 to Fable 5.1
Anthropic keeps Claude Fable 5 available, but its model page now recommends considering Fable 5.1 for improved performance.
Preserve the Baseline Before Upgrading
Fable 5 and Fable 5.1 share the same $10 input and $50 output base rates, the same 1M context window, and the same 128K maximum output. That makes a direct workload comparison especially useful because capacity and headline token pricing are held constant.
The newer model improves long-running agentic coding, multistep research, and complex work with documents, spreadsheets, and slides. It also lowers cache reads from $1 to $0.25 per million tokens, which can significantly change long-session economics.
Migration is not purely additive. Fable 5.1 introduces changes around forced tool selection, thinking-block compatibility, conversation editing, and new beta controls. Existing Fable 5 prompts generally transfer well, but production integrations should replay tool loops, cached sessions, persisted conversations, and refusal handling before switching traffic.
Fable 5 therefore remains useful as a versioned operational baseline: measure the old behavior first, then determine whether Fable 5.1 improves task completion enough to justify migration.
- 01
Keep a Fable 5 baseline
Record quality, agent completion, refusal rate, cache usage, latency, and cost on representative production tasks.
- 02
Compare Fable 5.1
Run the same long-horizon coding, research, vision, and enterprise workloads against the newer model.
- 03
Recalculate cache economics
Fable 5.1 cache reads cost $0.25/MTok instead of $1/MTok, which can materially reduce long-session cost.
- 04
Retest integration semantics
Verify tool choice, thinking blocks, persisted conversations, fallback handling, and any beta features before migrating production traffic.
09 / Capabilities
Claude Fable 5 Capabilities
Fable 5 combines multimodal input, always-on adaptive thinking, tool use, prompt caching, code execution, memory, compaction, and large context for agent-oriented application design.
Built for Stateful Workflows
Anthropic lists support for effort controls, task budgets in beta, the memory tool, code execution, programmatic tool calling, context editing for tool-result clearing, compaction, and vision.
These features are especially relevant to agents because long tasks need active state management. Tool results can accumulate, old context can become less useful, and the application may need to preserve durable memory while compacting transient details.
Fable 5 also uses a tokenizer introduced with Claude Opus 4.7. Anthropic notes that the same text can produce roughly 30% more tokens than on models released before Opus 4.7, depending on content and workload shape. Cost comparisons with older Claude generations should therefore use measured token counts rather than assume prompt lengths translate directly.
- Supported
Text
Accept text input and produce text output.
- Supported
Image input
Interpret screenshots, technical images, documents, web interfaces, and other supported visual inputs.
- Supported
Adaptive thinking
Always-on adaptive reasoning with effort controls instead of manual thinking-token budgets.
- Supported
Tool use
Supports programmatic tool calling and long-running agent workflows.
- Supported
Prompt caching
Cache writes and reads reduce repeated processing of large stable context.
- Supported
Memory and compaction
Supports state-management patterns useful for extended agent trajectories.
- Supported
Code execution
Use executable environments as part of supported agent workflows.
10 / Evaluation
Claude Fable 5 Strengths and Limitations
Claude Fable 5 is best understood as the original premium long-horizon Claude 5 model: powerful for difficult sustained work, but expensive, slower, refusal-aware, and now superseded by Fable 5.1 for new evaluations.
Strengths
Long-horizon autonomy
Designed to remain productive across extended goal-directed tasks that may involve many tools, files, decisions, and subagents.
1M context and 128K output
Large working-state capacity and unusually long output support repository-scale, research-heavy, and artifact-generation workloads.
Strong vision and enterprise work
Improved handling of dense technical images, web applications, financial analysis, spreadsheets, slides, and documents.
Delegation and collaboration
More dependable coordination of parallel subagents and peer agents than earlier Claude generations.
What to consider
Premium pricing
$10 input and $50 output per million tokens make broad routing expensive unless task value justifies the tier.
Slower comparative latency
Anthropic classifies Fable 5 as slower, so it is not designed as the default low-latency model for routine requests.
Safety refusals affect integration design
Applications need explicit refusal handling, fallback behavior, and refusal-rate monitoring for affected workloads.
Fable 5.1 is the recommended successor
Anthropic keeps Fable 5 active as a legacy model but recommends considering Fable 5.1 for improved performance and much cheaper cache reads.
Evaluate the full agent trajectory
Test Claude Fable 5 on difficult long-running work
Measure whether the model can preserve goals, coordinate tools and subagents, interpret difficult visual inputs, recover from failures, and finish demanding tasks without excessive human intervention.
Start FreeFor new deployments, also compare Fable 5.1. Anthropic keeps Fable 5 active as a legacy model but recommends the newer version for improved performance.
Common Questions
What is Claude Fable 5?
Claude Fable 5 is Anthropic’s original Fable-tier model for demanding reasoning and long-horizon agentic work. It was released on June 9, 2026 and introduced the first generally available Claude 5 model above the standard Opus tier.
How much does Claude Fable 5 cost?
Claude Fable 5 costs $10 per 1M standard input tokens and $50 per 1M output tokens. Five-minute cache writes cost $12.50/MTok, one-hour cache writes cost $20/MTok, and cache reads cost $1/MTok.
What is the Claude Fable 5 context window?
Claude Fable 5 has a 1,000,000-token context window by default and supports up to 128,000 output tokens per request.
What is Claude Fable 5’s knowledge cutoff?
Anthropic lists January 2026 as the reliable knowledge cutoff and training-data cutoff for Claude Fable 5.
Does Claude Fable 5 support images?
Yes. Claude Fable 5 accepts text and image input and produces text output. Anthropic highlights improved performance on dense technical images, detailed screenshots, and web applications.
Does Claude Fable 5 use adaptive thinking?
Yes. Adaptive thinking is always on. Thinking cannot be disabled, manual extended-thinking token budgets are not supported, and high is the default effort level.
What does stop_reason refusal mean in Claude Fable 5?
Claude Fable 5 runs additional safety classifiers that can decline a request and return stop_reason: refusal. Applications should treat this as a distinct outcome and can implement approved fallback behavior where appropriate.
How is Claude Fable 5 different from Claude Fable 5.1?
Both models have $10/$50 base pricing, 1M context, 128K output, and always-on adaptive thinking. Fable 5.1 improves long-running coding, multistep research, and office-document workflows and reduces cache-read pricing from $1 to $0.25 per million tokens.
Is Claude Fable 5 still available?
Yes. Anthropic lists Claude Fable 5 as active legacy. It was released June 9, 2026, with retirement not sooner than June 9, 2027, but Anthropic recommends considering Fable 5.1 for improved performance.
What is Claude Mythos 5?
Claude Mythos 5 shares Claude Fable 5’s underlying capabilities, specifications, and pricing but is available only to approved Project Glasswing customers. Unlike Fable 5, Mythos 5 does not include the same additional safety classifiers.
Should I choose Claude Fable 5 for a new application?
For a new evaluation, compare Fable 5.1 as the current successor. Fable 5 remains most relevant for existing integrations, historical benchmarking, compatibility testing, or cases where a team needs to understand behavior before migrating.
Model information
Last updated
Specifications, pricing, thinking behavior, safety classifiers, fallback semantics, capabilities, lifecycle, and migration guidance on this page are based on Anthropic’s official Claude Fable 5 documentation, prompting guide, pricing documentation, release notes, and migration guide.