{"version":"2.1.312","anchor":"refusal-fallback-model-selection-adds-a-no-refusal-fallback","canonical_anchor":"refusal-fallback-model-selection-adds-a-no-refusal-fallback","heading":"Two settings now decide whether a refusal can switch to a fallback model","tier":"notice","area":"Elsewhere","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/refusal-fallback-model-selection-adds-a-no-refusal-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Two settings now decide whether a refusal can switch to a fallback model\n\nClaude Code now offers no fallback model after a refusal when one setting is off or a second, opposing setting is on\n\n**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.\n\n**What**\n\nWhen a model refuses a request, Claude Code can switch to a fallback model. It now picks no fallback when either of these holds:\n\n- `refusal_fallback` is off\n\n- `no_refusal_fallback` is on\n\nThe 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.\n\n**Why**\n\nThis changes which models get a fallback after a refusal.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}