{"version":"2.1.169","anchor":"refusal-continuation-silent-retry-with-fallback-model-in-dev","canonical_anchor":"refusal-continuation-silent-retry-with-fallback-model-in-dev","heading":"Refusal Continuation \u2014 Silent Retry with Fallback Model [In Development]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169\/e\/refusal-continuation-silent-retry-with-fallback-model-in-dev","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169","markdown":"### Refusal Continuation \u2014 Silent Retry with Fallback Model [In Development]\n\n**What**\n\nWhen the model refuses a request for safety reasons, Claude Code will silently retry with a designated fallback model. If the fallback model responds successfully, the conversation continues as if nothing happened; if the fallback also refuses, the refusal is shown normally.\n\n**Status**\n\nFeature-flagged. Gated by a server-side `refusal_fallback_prompt` feature flag that must be present in the account's beta header list.\n\n**Details**\n\n- A `refusalFallbackModelLatch` tracks which fallback model was activated and what the previous model override was, so the model is restored after the retry turn\n- The detection function `fTK()` returns `false` unless `On8()` (refusal continuation enabled) AND `refusal_fallback_prompt` is absent from the beta list\n- Infrastructure includes latch set\/clear\/update functions and a `refusalFallbackOccurred` flag for telemetry\n\n**Evidence**\n\nGated by server-side flag (search for `\"refusal_fallback_prompt\"`) \u2014 `fTK()` at line ~122285, `refusalFallbackModelLatch` state at line ~2551"}