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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

A bad plugin config no longer takes the plugin down

You'll notice
Useful3 Signal2
Plugins

A plugin with bad config now loads on defaults instead of failing, when enabled from trusted settings.

userConfig
What

If a plugin's options do not match the userConfig its plugin.json declares, and the plugin was enabled purely from trusted settings, it now loads on its default values with an error logged instead of failing. Plugins enabled any other way still throw as before.

Details
  • Asking a plugin for options when its manifest declares no userConfig now logs a warning once per plugin, and every option reads as absent.
Evidence

options requested but its manifest declares no userConfig; every option reads as absent

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