{"version":"2.1.301","anchor":"auto-mode-classifier-request-can-now-carry-a-classifierjudg","canonical_anchor":"auto-mode-classifier-request-can-now-carry-a-classifierjudg","heading":"Auto mode safety check can be tagged outside auto mode","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/auto-mode-classifier-request-can-now-carry-a-classifierjudg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Auto mode safety check can be tagged outside auto mode\n\nThe auto mode classifier's requests can now carry an extra tag, and when they do the auto mode value is sent whatever the permission mode\n\n**Unclear.** It is not clear what condition adds the tag or what it changes in how actions are judged.\n\n**What**\n\nIn auto mode, a classifier (a separate model call that judges whether an action is safe to run) checks actions before Claude Code takes them. Its requests can now carry an extra tag when a certain condition is met. When the tag is present, the request is marked with the auto mode value whatever the current permission mode is.\n\nBefore, that value was sent only when `permissionMode` was auto, or plan with auto active and bypass unavailable.\n\n**Why**\n\nThe classifier's requests can now be labelled as auto mode even when you are not in auto mode.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}