{"version":"2.1.236","anchor":"posttooluse-hooks-can-pass-context-to-the-auto-mode-permissi","canonical_anchor":"posttooluse-hooks-can-pass-context-to-the-auto-mode-permissi","heading":"PostToolUse hooks can pass context to the auto-mode permission classifier","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/posttooluse-hooks-can-pass-context-to-the-auto-mode-permissi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### PostToolUse hooks can pass context to the auto-mode permission classifier\n\nYour PostToolUse hooks can send extra context to the classifier that decides permissions in auto mode.\n\n**What**\n\nPostToolUse hook responses accept a new optional `classifierContext` string, carried alongside the tool result to the classifier that decides permissions in auto mode. It is capped at 2000 UTF-16 code units shared across all hooks for a single tool call, honored only on synchronous hook responses, and dropped if the paired output rewrite is rejected or superseded. Anyone writing a hook on this build can use it.\n\n**Details**\n\n- Added to both the SDK-facing hook schema and the internal one, so it is documented to hook authors as well as accepted at runtime.\n- The description states that relaying a genuine user statement may satisfy a consent bar, but never a hard boundary.\n- No feature flag on the schema itself.\n\n**Evidence**\n\n`Host-asserted context shown to the auto-mode permission classifier alongside this tool call's result.`\n\n- Area: Hooks\n- Names: `classifierContext`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}