agents · review · first seen Nov 10, 10:32 UTC

Anthropic makes Claude Fable 5.2 the Claude Code default

Claude Code v2.1.321 shipped Claude Fable 5.2 as its default Fable model and added settings-file support for remote-control sessions. Builders should check the default and their remote-control startup procedure before relying on either change.

L0 · primary1 source6 claims checked4 min read

What shipped

Claude Fable 5.2, identified in the release notes as claude-fable-5-2, is now the default Fable model in Claude Code. The same entry lists a 1M context and pricing of $8/$40 per Mtok, with cache reads at $0.20/Mtok. Those are the concrete model details available here. The release note does not, by itself, measure how the model performs on a builder’s own tasks. [1][2][3]

The --settings <file> option now applies a settings file to every session started by claude remote-control. There is an operational condition attached: if that file changes, remote-control starts no new sessions until remote-control is restarted. Treat the restart as part of changing the file, not as an optional cleanup step. Otherwise a configuration edit can leave the process unable to start another session. [1][2]

The release also fixes MCP OAuth requests that sent secrets, including refresh tokens, to another host after a server redirect. This is a shipped fix to a specified redirect behavior, not a claim that every MCP OAuth path has been reviewed or that all credential-handling risks are gone. It belongs in the assessment for teams using MCP login, even if their immediate reason for reading this release is the model default. [1][2]

Why it matters if you build

A default is a workflow change because a builder who relies on the default Fable selection now gets Fable 5.2. Check the model used in a representative session before comparing new results with earlier work. The release gives a context figure of 1M, but does not establish that every task will benefit from filling it, or that an existing workflow needs to change its input size. [1][2]

The price line gives builders a number to use when reviewing whether this default fits their budget: $8/$40 per Mtok and $0.20/Mtok for cache reads. Keep those figures distinct. The supplied release excerpt does not spell out what each side of the $8/$40 pair is charged for, nor does it give an example bill. Do not turn the listed rates into a cost estimate without the usage details for your own work. [1]

Remote-control users can now point the process at one settings file for the sessions it starts. That is useful when the same intended settings must apply across those sessions, but the file is not a live-update mechanism. If a process or operator edits it, new sessions stop starting until remote-control is restarted. A practical rollout therefore needs both a deliberate file choice and a restart step when that file changes. [1][2]

How to try it today

1. Start a Claude Code session that uses the default Fable model, and check that it is Fable 5.2.
2. Review the listed 1M context and $8/$40 per Mtok rates, including $0.20/Mtok cache reads, against your intended use.
3. Choose the settings file you want remote-control sessions to use.
4. Start claude remote-control with --settings <file>, then check the settings in a session it starts.
5. If you change that file, restart claude remote-control before expecting it to start another session.

What we checked

Every claim below was walked down the source ladder. The rung is how close the source is to the thing itself; the tense is the source's own.

1. shipped L0 · primary

   Claude Fable 5.2 is now the default Fable model in Claude Code.

   per GitHub releases · anthropics/claude-code (L0)
2. shipped L0 · primary

   Claude Fable 5.2 has a 1M context.

   per GitHub releases · anthropics/claude-code (L0)
3. shipped L0 · primary

   Claude Fable 5.2 costs $8/$40 per Mtok, with $0.20/Mtok cache reads.

   per GitHub releases · anthropics/claude-code (L0)
4. shipped L0 · primary

   The --settings <file> option applies a settings file to every session started by claude remote-control.

   per GitHub releases · anthropics/claude-code (L0)
5. shipped L0 · primary

   If that settings file changes, claude remote-control starts no new sessions until it is restarted.

   per GitHub releases · anthropics/claude-code (L0)
6. shipped L0 · primary

   Claude Code fixes MCP OAuth requests sending secrets such as refresh tokens to another host after a server redirect.

   per GitHub releases · anthropics/claude-code (L0)

What is not confirmed

The supplied release note does not establish task-level quality, latency, or a measured improvement over the previous default. The 1M context figure is a stated limit, not a result from a particular workload. [1][2]

It does not provide a sample bill or identify the two charged categories behind the $8/$40 per Mtok pair in the supplied excerpt. It also does not establish that the MCP OAuth fix covers credential behavior beyond the described redirect case. [1][2]

Who should act, who should wait

Move now if your work depends on Claude Code’s default Fable selection or if you start sessions through claude remote-control. Check the selected model, review the stated rates, and make a settings-file change only with a restart procedure in place. Wait before making claims about performance or a specific bill: neither is established by these release details. If the OAuth redirect case matters to your MCP use, note the shipped fix without treating it as a broader security guarantee. [1][2][3][4][5]

Sources

• v2.1.321 — GitHub releases · anthropics/claude-code L0 · primary