{"version":"2.1.281","anchor":"auto-mode-classifier-treats-plan-mode-as-having-left-the-mod","canonical_anchor":"auto-mode-classifier-treats-plan-mode-as-having-left-the-mod","heading":"Auto-mode classifier treats plan mode as having left the mode unless the host allows it","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/auto-mode-classifier-treats-plan-mode-as-having-left-the-mod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Auto-mode classifier treats plan mode as having left the mode unless the host allows it\n\nThe auto-mode classifier's verdict is now discarded in plan mode unless the host allows it\n\n**Unclear.** The finding does not say which hosts pass the check.\n\n**What**\n\nThe remote tool classifier decides, in auto mode, whether a tool call can go ahead without asking you. Plan mode is the mode where Claude plans work without making changes. The classifier's answer is now thrown away, recorded as \"mode_left\", in one more case: the session is in plan mode and a check tied to the host (the app or environment running Claude Code) fails. Before, this happened only when the mode stopped being eligible or changed.\n\nThe classifier and its eligibility check now receive the host. The message shown when the classifier is unavailable now also receives a retry delay (`retryAfterMs`).\n\n**Why**\n\nIn plan mode on some hosts, the classifier's answer is no longer used, so the call falls back to what happens when there is no verdict."}