{"version":"2.1.286","anchor":"fast-mode-fallback-notice-using-standard-speed-warning","canonical_anchor":"fast-mode-fallback-notice-using-standard-speed-warning","heading":"Fast mode handles models that reject it, with a notice when it falls back","tier":"notice","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/fast-mode-fallback-notice-using-standard-speed-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Fast mode handles models that reject it, with a notice when it falls back\n\nWhen a model rejects fast mode, Claude Code now uses standard speed for that model for the session and shows a warning\n\n**Unclear.** It is not clear who sees the warning, because two conditions that can skip it are not explained.\n\n**What**\n\nFast mode makes Claude respond faster on models that support it. This release changes what happens when the model in use does not accept it.\n\n- When fast mode is rejected for a fallback model (a model used in place of the one you picked), Claude Code remembers this for the session and uses standard speed for that model. The fast mode state and the labels in the model picker now check this model by model.\n\n- A warning appears straight away: \"Using standard speed on \u00b7 fast mode wasn't available\". Before, the switch to standard speed was not announced.\n\n- In remote sessions, a report that fast mode is off because of `model_not_allowed` is now ignored instead of changing the fast mode state.\n\n- When a controlling program sets `fastMode` to true through `apply_flag_settings` and the model changes too, or the current settings disagree, a fast mode check now runs after the settings are applied. Before, it only replied to the request.\n\n**Why**\n\nIf your model cannot use fast mode, you now see why Claude Code dropped to standard speed, and it stops retrying fast mode for that model during the session.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}