Your PostToolUse hooks can send extra context to the classifier that decides permissions in auto mode.
What's wrong with this entry?
PostToolUse 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.
- 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.
- The description states that relaying a genuine user statement may satisfy a consent bar, but never a hard boundary.
- No feature flag on the schema itself.
Host-asserted context shown to the auto-mode permission classifier alongside this tool call's result.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Session context is built lazily and cached per project root
Both mention context
-
v2.1.232
/context returns a structured breakdown of token usage
Both mention context
-
v2.1.232
/context returns machine-readable usage alongside the table
Both mention context