Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Reading a new release v2.1.280 Building the pages · 4/6 1043 findings $36.88 so far
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

TierNothing to try yethow much it should matter to you
Useful4my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaModel Configwhat it touches
KindIn Developmentin v2.1.269,
Group of 4 Nothing to try yet Notable

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.

Read from
Names in the bundle/config
Feature flag
tengu_jazzy_goblet Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.269: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Telemetry and egress touched a line naming /config after this was published. With `disableEssentialTelemetry`, `disableNonessentialTelemetry`, `disableNonessentialServices`, and `disableAutoUpdates` all set to `true`, the desktop application makes **no outbound connections to Anthropic-operated hosts at runtime**. … third-party/claude-desktop/telemetry see the edit
Confirmed since Anthropic's documentation has since written up /config, on Deploy with Enterprise Admin Console. | An estimated cost in US dollars for each conversation and model. The app calculates the estimate on the device, at Anthropic list prices or at the rates you set under **Models** on the **Connection** page, and labels which it used (`list… third-party/claude-desktop/admin-console see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /config, on Deploy with Enterprise Admin Console.
The name it cites is new in this buildNew in this build: tengu_jazzy_goblet

See this entry in the whole of v2.1.269 →