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.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Better error when a plugin hook gets non-object input

You'll notice
Useful2 Signal2
Hooks

Bad input to a plugin hook now produces an error naming the hooks involved.

What

Hooks that plugins attach to interface calls now run through a shared chain runner that checks the event argument is an object first. When it is not, the error names the hooks involved instead of failing opaquely.

Evidence

its input is no object, which the hooks on it

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.251 →