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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

/plugin validate inspects hooks modules instead of a declared capabilities list

Use it now
Useful3 Signal3
Plugins

Plugin validation now loads your hooks modules and reports what they hook; the capabilities field is ignored.

/plugin validate
What

Validating a plugin's hooks.json now loads each JavaScript hooks module it names, refuses any path that points outside the plugin directory, and reads the module to report which events it hooks and which plugin APIs it calls. A capabilities field in the file is now reported as ignored and safe to delete.

Details
  • A plugin naming more than one hooks module is reported as refused by the loader.
Evidence

'capabilities' is no longer read

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