Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

The 'switch models on flag' setting becomes an explicit choice, with a prompt to set it

The model-refusal fallback setting is now an explicit 'switch automatically' vs 'ask each time' choice, promptable interactively, with new telemetry

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaTelemetrywhat it touches
KindInternal Changesin v2.1.269,
Group of 4 Under the hood

The model-refusal fallback setting is now an explicit 'switch automatically' vs 'ask each time' choice, promptable interactively, with new telemetry

What

  • 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.
  • 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.
  • Changing this setting now fires a tengu_refusal_fallback_setting_changed telemetry event and persists the change to user settings.
  • New telemetry events were registered: tengu_refusal_fallback_preference_prompt, plus tengu_policy_limits_cache_state_at_first_prompt and tengu_policy_limits_fetch.

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.

See this entry in the whole of v2.1.269 →

Feedback