Skip to content
← Back to release · 2.1.257
New features / v2.1.257

Claude Fable 5.1

CHANGELOG · original

Added Claude Fable 5.1 (claude-fable-5-1), now the default Fable model — 1M context, $10/$50 per Mtok with $0.25/Mtok cache reads
Open official changelog ↗

Related documentation

Background on the feature; see the changelog above for this specific change.

Documentation excerpt

Work with Fable

Claude Fable models are the most capable models in Claude Code, suited to tasks larger than a single sitting. They sustain long autonomous sessions, investigate before acting, and verify their work more often than smaller models.

No Fable model is the account-type default on any plan or provider. Select one explicitly:

  • Fable 5.2: run /model fable, or launch with claude --model fable. In Claude apps gateway sessions, run /model claude-fable-5-2 instead.
  • Fable 5.1 or Fable 5: select it by model ID. On the Anthropic API, run /model claude-fable-5-1 or /model claude-fable-5, or launch with claude --model claude-fable-5-1. On other providers, use your provider's model ID or pin it with ANTHROPIC_DEFAULT_FABLE_MODEL.

On Pro, Max, Ultra, Team, and Enterprise plans, a claude-fable-5-1 model saved in your user settings moves to the fable alias:

  • Pro, Max, or Ultra plan: the move happens the first time you run v2.1.321 or later. In the terminal, the startup model line can show (auto-updated) once.
  • Team or Enterprise plan: the move waits for your organization's settings, so it can come at a later startup, or not at all. It applies from the next session, with no (auto-updated) line. To check your model, run /model.

After the move, sessions start at Fable 5.2's default effort unless you've set a level for it. Console accounts, third-party providers, and project, local, or managed settings keep claude-fable-5-1.

Requests that a Fable model's safety classifiers flag, most often in cybersecurity and biology domains, trigger automatic model fallback.

To get the most from Fable:

  • Describe the outcome, not the steps: hand it the result you want and let it plan the path. To keep it working toward that outcome, set a goal.
  • Hand it ambiguous problems: root-cause investigations, outage debugging, and architecture decisions are where the extra investigation and verification pay off.
  • Skip the verification reminders: it verifies its own work with less prompting, so reminders to test or check are usually unnecessary.
  • Size up larger tasks: give it work you would normally break into pieces. It holds long sessions without losing the thread.

[!NOTE]

Fable 5.2 requires Claude Code v2.1.321 or later, and Fable 5.1 requires v2.1.257 or later. If a request for one of them from an older version fails, see Claude Code does not support this model. Run claude update to upgrade. For availability under zero data retention, see Model availability under ZDR.

On the Anthropic API, a Fable model appears in the /model picker unless availableModels or organization model restrictions exclude it. When your organization can't use Fable at all, for example under zero data retention, the row stays in the picker grayed out, with a note on why.

Fable and usage credits

Depending on your plan and seat tier, Fable usage can bill to usage credits instead of drawing on your plan's included limits. When it does, the /model picker shows "Requires usage credits" on the Fable row. To manage usage credits, see Add usage credits to your subscription.

In interactive sessions, Claude Code can show a Fable usage-credits consent prompt. You can continue on Fable using usage credits or switch to your default model. You can also dismiss the prompt:

  • When you select a Fable model with /model, you keep your current model.
  • Mid-session, Claude Code continues the turn on your default model.

After you choose to continue on Fable using usage credits, Claude Code doesn't show the prompt again.

In a session with Remote Control connected, a background session, or an agent team teammate's session, nobody may be at the terminal, so Claude Code holds the mid-session consent prompt for the dialogExpiry deadline, five minutes by default. If nobody has answered by the deadline, Claude Code ends the turn without sending the request and adds a notice to the transcript, which the Remote Control client also shows. Your model selection is unchanged, and Claude Code asks for consent again on your next message.

What you can do while the prompt is waiting depends on the session:

  • With Remote Control connected or in a teammate's session, press any key at the terminal to cancel the deadline, and Claude Code waits for your answer.
  • With Remote Control connected in an interactive terminal session, you can also answer on your connected device, and that answer lasts for that session. Requires Claude Code v2.1.323 or later.
  • In a background session, answer before the deadline.
  • If you send a new message from the remote client before anyone has typed at the terminal, Claude Code ends the turn the same way, and your new message starts the next turn. After someone types at the terminal, Claude Code keeps waiting for the answer and queues your new message behind it.

In a session another application hosts through the Agent SDK, whether the prompt appears is up to that application. If it appears and nobody answers before the same dialogExpiry deadline, Claude Code ends the turn without sending the request.

In non-interactive mode with the -p flag, and in an Agent SDK application that doesn't show the prompt, Claude Code never asks for consent. When a Fable request there would bill to usage credits, Claude Code bills it without asking.

Documentation snapshot · 2026-11-20

Change details