{"version":"2.1.284","anchor":"boolean-plugin-config-values-validated","canonical_anchor":"boolean-plugin-config-values-validated","heading":"Plugin true\/false settings that cannot be read are now left out","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/boolean-plugin-config-values-validated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugin true\/false settings that cannot be read are now left out\n\nA plugin setting that should be true or false is now dropped if its value cannot be read as one, instead of being forced into one\n\n**Unclear.** Exactly which texts are accepted as true or false is not known.\n\n**What**\n\nPlugins add features to Claude Code and can have settings you fill in. For a setting that should be true or false, Claude Code now reads only the first line of the value you gave. If that value cannot be understood as true or false, the setting is left out. Before, any text was forced into true or false.\n\n**Why**\n\nA mistyped value no longer quietly becomes true or false. The setting is simply missing, so the plugin's own handling of an absent value applies.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}