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

Bad hook matchers are reported against the event they belong to

You'll notice
Useful3 Signal1
Hooks

Bad hook matchers now produce an error naming the event they belong to.

What

Hook configuration validation now checks each matcher with rules specific to the event it is attached to, and the resulting error names that event instead of failing generically.

Details
  • Event rules live in a lookup table keyed by event name; a tool.call entry is read from it.
Evidence

SITE_RULES

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 →