Claude Code v2.1.75 · 13 Mar 2026
Plugin Configurable Options
Entry Kind: in v2.1.75, 13 Mar 26
Changes Section of the release
What
Plugins can now declare user-configurable options in their manifest via a userConfig schema, with typed fields, defaults, and secure storage for sensitive values.
Details
Plugin manifests can include a userConfig block with named options of type string, number, boolean, directory , or file Each option supports title, description , required , default , sensitive, min/max , and multiple fields Option keys must be valid identifiers — they become CLAUDE_PLUGIN_OPTION_<KEY> environment variables in hooks Sensitive values are stored in secure storage (macOS keychain or .credentials.json), non-sensitive values in settings.json Available as ${user_config.KEY } in MCP/LSP server config, hook commands, and (non-sensitive only) skill/agent content Evidence
Plugin options schema and env var injection (search for "CLAUDE_PLUGIN_OPTION_", "User-configurable values this plugin needs")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.75 →
Names in this entry
setting userConfig Installing a plugin can now walk you through configuring it, if the plugin declares options.
setting directory You can now run a hook whenever a directory is added mid-session, including via /add-dir.
setting description Bug reports you file now follow a fixed bullet template instead of free-form prose.
setting required Plugins your administrator requires or auto-installs are now labelled as admin installs.
setting default Subagent nudging behaviour can be picked per model, but the whole feature stays behind a gate.
setting max The bundled Claude API skill docs now target the new Opus, covering thinking defaults, fallbacks and fast mode.
setting settings.json Resumed sessions now carry your settings files along, with plugin registrations stripped out.
setting user_config MCP failures are now sorted into causes like server down, login problem or bad config for reporting.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 1 of 23
Opus 1M Context Window Default
In v2.1.75 Changes release-page order
Next → · 3 of 23
SSH Start Directory Setting