Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Hook schema failures now print the exact field, a template, and which tool failed

You'll notice
Useful4 Signal2
Hooks

A bad hook response now shows the exact failing field, the output and a template.

What

A hook whose JSON does not match the expected shape now gets a full diagnostic instead of a bare rejection: the specific failing field and message, the offending output, and targeted hints.

Details
  • Union errors are walked to the most specific branch; the first problem prints as path: message with remaining issues as a bulleted list.
  • A PermissionRequest decision gets the allow/deny shape appended; a legacy top-level decision gets an explanation of approve|block versus hookSpecificOutput.permissionDecision.
  • A companion helper prints a field-by-field template of every accepted output type: PreToolUse, PermissionRequest, UserPromptSubmit, PostToolUse, PostToolBatch, Stop and SubagentStop.
  • Failures are recorded per tool-use ID, capped at 8 entries, so the failing tool's name is prefixed in the status line.
  • No gate found; appears to apply to all hooks.
Evidence

Hook JSON output validation failed —

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.

See this entry in the whole of v2.1.248 →