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
userConfignow 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.
Names in the bundleuserConfig
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up userConfig, on Plugins reference.
| `userConfig` | object | User-configurable values prompted at enable time. See [User configuration](#user-configuration) | See below |plugins-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up userConfig, on Plugins reference.