Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Fable 5.1 model choices are moved to the fable alias at startup

If your saved model is Fable 5.1, Claude Code switches it to the fable alias, with a delayed move for team and enterprise organisations

You'll notice Improvements
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ModelsArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release
What

When Claude Code starts, it now checks your saved model setting. If it is claude-fable-5-1 or claude-fable-5-1[1m], Claude Code changes it to the fable alias. An alias is a short name that always points to the current Fable model rather than one fixed version. A similar startup step used to do this for claude-fable-5.

The move is skipped when:

  • you use a third-party provider, set either through environment variables or through how you sign in
  • the fable alias is not allowed for you

Team and enterprise organisations get a second, delayed move. It waits until the organisation is entitled to the fable alias, gives up after 14 days, and does nothing at all after 15 December 2026. This delayed move is on by default in the code unless it is switched off remotely.

Why

If you pinned Fable 5.1 on purpose, your choice is changed without a prompt and will follow the alias from then on. Check your model setting if you want to stay on a specific version.

Read from
Names in the bundlefableclaude-fable-5-1
Feature flag
tengu_amber_thistle Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.321: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.321. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up claude-fable-5-1, on claude-prompting-best-practices. 7. **Pass thinking blocks back unchanged and keep history append-only:** Append each assistant turn exactly as the API returned it, thinking blocks included. On Claude Fable 5.2, Claude Mythos 5.2, Claude Fable 5.1, Claude Mythos 5.1, Clau… build-with-claude/prompt-engineering/claude-prompting-best-practices see the edit
Confirmed since Anthropic's documentation has since written up fable, on compaction-threshold. | Beta | Claude API, [Claude Platform on AWS](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws) | [Claude Fable 5.2](https://platform.claude.com/docs/en/models/fable-5-2/overview), [Claude Mythos 5.2](https://pl… build-with-claude/compaction-threshold see the edit
Added since A small documentation edit on claude-tag touched a line naming fable after this was published. <template data-mint="manifest">{"docsConfig":{"theme":"mint","$schema":"https://mintlify.com/docs.json","name":"Claude.ai Documentation","colors":{"primary":"#0E0E0E","light":"#D4A27F","dark":"#0E0E0E"},"logo":{"light":"https://mintcdn.com… claude-tag see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesA small documentation edit on claude-tag touched a line naming fable after this was published.
The name it cites is new in this buildNew in this build: tengu_amber_thistle

See this entry in the whole of v2.1.321 →

Feedback