A post by @synthwavedd reports that the imminent Claude Code 2.1.257 release adds Claude Fable 5.1 and Claude Mythos 5.1 to its model catalog. The accompanying screenshot appears to show the change from Claude Code 2.1.252 to 2.1.257, along with new model identifiers, aliases, context limits, and output settings.

Original post on X

Load the post to view it as published on X. X may receive connection data.

View the original post on X ↗

Because the post describes an imminent release, these details should be treated as a reported preview rather than an independently confirmed general-availability announcement.

What Claude Code 2.1.257 reportedly adds

The reported update centers on two model-catalog entries:

  • `claude-fable-5-1`, identified as Fable 5.1

  • `claude-mythos-5-1`, identified as Mythos 5.1

The screenshot lists a June 2026 knowledge cutoff, a 1 million-token context window, and output limits of 64,000 tokens by default and 128,000 tokens maximum for the new entries. Those figures describe the catalog information shown in the screenshot; the post itself does not provide independent performance results or explain how the models compare with earlier versions.

Fable 5.1 receives the main alias change

The reported update changes the `fable` alias so that it resolves to Fable 5.1. The screenshot also shows a migration from the earlier `fable5` alias to `fable`, while the gateway remains associated with `claude-fable-5`.

For Claude Code users, alias changes can matter because a short model name may resolve to a different underlying model after an update. Projects or workflows that need a stable model target may therefore need to use an explicit identifier rather than relying on the unqualified alias.

The screenshot says Fable 5.1 appears in the `/model` picker as “Fable 5.1” and uses the identifier `fable51`, with usage credits required. These are reported configuration details, not a statement about the model’s pricing or availability beyond what is shown.

Provider and capability details in the release screenshot

The screenshot lists provider-specific identifiers for Fable 5.1 across Bedrock, Mantle, and Vertex:

  • Bedrock: `us.anthropic.claude-fable-5-1`

  • Mantle: `anthropic.claude-fable-5-1`

  • Vertex: `claude-fable-5-1`

  • Vertex environment value: `VERTEX_REGION_CLAUDE_FABLE_5_1`

It also shows a `mid_conv_tool_change` capability flag for Fable 5.1, and a `fable_5_1_prompt_bundle` flag associated with the new model configuration. The screenshot says Mythos 5.1 retains `fable_5_mitigations` and does not use a `refusal_fallback` setting.

The same image displays a new model-identity system prompt beginning with “This iteration of Claude is Claude Fable 5.1.” That suggests the update includes model-specific identity changes in addition to the catalog entries, although the full prompt and its practical effect are not provided in the post.

What the reported change means for Claude Code users

The most immediate practical impact is model selection. If Claude Code 2.1.257 ships with the configuration shown, users may see Fable 5.1 and Mythos 5.1 in the model picker and may be able to address Fable 5.1 through the updated `fable` alias.

The reported 1 million-token context window and higher maximum output limit could make the new entries relevant to unusually large coding tasks, long repository discussions, or generated outputs that exceed conventional response limits. Those are potential use cases implied by the listed limits, not demonstrated capabilities or benchmark results.

Teams integrating Claude Code through multiple providers may also need to review model identifiers. The provider-specific names shown for Fable 5.1 indicate that selecting the model may depend on the deployment path rather than on a single universal identifier.

For now, the announcement is best understood as a release preview: it identifies the models and configuration changes expected in Claude Code 2.1.257, but it does not establish final availability, performance, or service terms.