{"version":"2.1.322","anchor":"fast-mode-toggle-resolves-the-target-model-and-passes-it-to","canonical_anchor":"fast-mode-toggle-resolves-the-target-model-and-passes-it-to","heading":"Turning fast mode on now uses the fast mode model when saving settings","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322\/e\/fast-mode-toggle-resolves-the-target-model-and-passes-it-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322","markdown":"### Turning fast mode on now uses the fast mode model when saving settings\n\nTurning fast mode on now looks up the model fast mode will run on and uses it when saving the setting\n\n**Unclear.** What this changes for someone turning fast mode on is not clear.\n\n**What**\n\nWhen you turn fast mode on, Claude Code now looks up which model fast mode will run on. It uses that model when it saves your settings and in a related step that runs at the same moment. Before, it used the main model of the conversation and did not pass a model when saving. If applying the change fails, the message is \"Fast mode was not changed: applying it failed\".\n\n**Why**\n\nThis may fix cases where the model shown and the model fast mode actually runs on did not match.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}