{"version":"2.1.269","anchor":"switch-models-on-flag-setting-changed-from-boolean-toggle","canonical_anchor":"switch-models-on-flag-setting-changed-from-boolean-toggle","heading":"The 'switch models on flag' setting becomes an explicit choice, with a prompt to set it","tier":"use","area":"Model Config","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/switch-models-on-flag-setting-changed-from-boolean-toggle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### The 'switch models on flag' setting becomes an explicit choice, with a prompt to set it\n\nThe model-refusal fallback setting is now an explicit 'switch automatically' vs 'ask each time' choice, promptable interactively, with new telemetry\n\n**What**\n\n- The `\/config` setting `switchModelsOnFlag` (whether Claude Code automatically switches to a fallback model when the current model refuses\/flags a request) is now an explicit enum of 'switch automatically' or 'ask each time', rather than a plain boolean, though it still accepts true\/false\/on\/off\/yes\/no from the CLI or config files.\n\n- When a model refuses or flags a request and Claude Code wants to switch to a fallback model, it can now ask interactively with a question like \"Switch to ... and keep going whenever this happens?\", offering to switch automatically or pause, and remembers the choice.\n\n- Changing this setting now fires a `tengu_refusal_fallback_setting_changed` telemetry event and persists the change to user settings.\n\n- New telemetry events were registered: `tengu_refusal_fallback_preference_prompt`, plus `tengu_policy_limits_cache_state_at_first_prompt` and `tengu_policy_limits_fetch`.\n\n**Why** This gives users more explicit control over automatic model fallback on refusal, letting them decide in the moment (and remember the choice) rather than relying on a single fixed setting.\n\n- Area: Model Config\n- Names: `switchModelsOnFlag`, `\/config`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}