{"version":"2.1.314","anchor":"fast-mode-settings-preserved-in-a-managed-settings-filter","canonical_anchor":"fast-mode-settings-preserved-in-a-managed-settings-filter","heading":"Fast mode opt-out and per-session opt-in now survive a settings filter","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/fast-mode-settings-preserved-in-a-managed-settings-filter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Fast mode opt-out and per-session opt-in now survive a settings filter\n\nA settings filter that used to drop `fastMode` and `fastModePerSessionOptIn` now keeps `fastMode` when off and `fastModePerSessionOptIn` when on\n\n**Unclear.** It is not stated which settings source or mode this filter applies to, so it is unclear which setups are affected.\n\n**What**\n\nClaude Code runs some settings through a filter in a restricted situation, keeping only certain values. That filter now keeps two fast mode settings that it used to drop:\n\n- `fastMode`, when it is set to false (fast mode turned off)\n\n- `fastModePerSessionOptIn`, when it is set to true (people must turn fast mode on in each session)\n\n**Why**\n\nIn the situation where this filter applies, turning fast mode off or requiring a per-session opt-in now takes effect instead of being lost.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}