{"version":"2.1.288","anchor":"plugin-user-config-substitution-can-leave-unset-keys-li","canonical_anchor":"plugin-user-config-substitution-can-leave-unset-keys-li","heading":"Unset plugin options can now be left as placeholders instead of causing an error","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plugin-user-config-substitution-can-leave-unset-keys-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Unset plugin options can now be left as placeholders instead of causing an error\n\nFilling in a plugin's ${user_config.*} placeholders can now leave an unset option as written instead of always failing; failing is still the default\n\n**Unclear.** It is not clear which parts of Claude Code use the new mode that leaves unset options as placeholders.\n\n**What**\n\nPlugins can declare options, called `userConfig`, that you set yourself, and the plugin refers to them with placeholders written as `${user_config.<name>}`. Before, if Claude Code filled in one of those placeholders and you had not set that option, it always stopped with an error telling you the option isn't set and to open `\/plugin` to configure it.\n\nThe step that fills in placeholders now has a second mode. In that mode an unset option is left as its placeholder text and no error is raised. The default has not changed: unless a part of Claude Code asks for the new mode, an unset option still produces the same error.\n\n**Why**\n\nSome parts of Claude Code only need to show or check a plugin's settings. With this mode they can do that without failing just because you have not filled in every option yet.\n\n- Area: Plugins\n- Names: `userConfig`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}