{"version":"2.1.281","anchor":"auto-mode-new-harnesssynthesized-fast-path-skips-the-clas","canonical_anchor":"auto-mode-new-harnesssynthesized-fast-path-skips-the-clas","heading":"Auto mode: new 'harnessSynthesized' fast path skips the classifier","tier":"notice","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/auto-mode-new-harnesssynthesized-fast-path-skips-the-clas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Auto mode: new 'harnessSynthesized' fast path skips the classifier\n\nIn auto mode, tool calls that Claude Code generates itself now skip the classifier and are allowed\n\n**What**\n\nIn auto mode, a classifier (a model that judges whether an action is safe) usually checks each tool call, meaning each action Claude takes such as running a command or editing a file. Tool calls that Claude Code generates itself for a specific tool, for example ones marked `synthesizedBy: \"observer-gate\"`, now skip that check and are allowed. The recorded reason starts with `harness-synthesized:`.\n\nThis happens only when both modes involved allow auto approval and no safety check has flagged the call. The existing shortcut for plugin-originated calls now shares the same underlying code.\n\n**Why**\n\nActions Claude Code starts on its own no longer wait for a classifier verdict. Any call that a safety check has flagged still goes through the normal checks.\n\n- Flag `tengu_structured_creek`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}