Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.312entry #60

Claude Code v2.1.312 ·

Two settings now decide whether a refusal can switch to a fallback model

Claude Code now offers no fallback model after a refusal when one setting is off or a second, opposing setting is on

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

Unclear It is not clear how refusal_fallback and no_refusal_fallback are set for a given account, so who keeps the fallback is unknown.

What

When a model refuses a request, Claude Code can switch to a fallback model. It now picks no fallback when either of these holds:

  • refusal_fallback is off
  • no_refusal_fallback is on

The older route through an allow list also has an extra condition, and one account category that used to be recognised for this choice has been removed.

Why

This changes which models get a fallback after a refusal.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear how `refusal_fallback` and `no_refusal_fallback` are set for a given account, so who keeps the fallback is unknown.

See this entry in the whole of v2.1.312 →

Feedback