{"version":"2.1.288","anchor":"auto-mode-classifier-floor-no-longer-depends-on-canautoclass","canonical_anchor":"auto-mode-classifier-floor-no-longer-depends-on-canautoclass","heading":"Auto mode's classifier floor applies even when the classifier cannot run","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/auto-mode-classifier-floor-no-longer-depends-on-canautoclass","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Auto mode's classifier floor applies even when the classifier cannot run\n\nAuto mode's classifier floor can now take effect even when the automatic checker cannot run, which it could not before\n\n**Unclear.** It is not clear what the classifier floor does to a tool call when the classifier cannot run.\n\n**What**\n\nIn auto mode, an automatic checker called a classifier decides whether Claude may take an action. A minimum level of this checking, the classifier floor, used to apply only when the classifier was able to run. That requirement is gone. The floor now applies whenever its own conditions are met, including when `chromeClassifierFloorEnabled` is on.\n\n**Why**\n\nBecause the floor now applies even when the classifier cannot run, some tool calls (actions Claude asks Claude Code to take) may be handled differently in auto mode.\n\n- Area: Auto Mode\n- Names: `chromeClassifierFloorEnabled`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}