{"version":"2.1.295","anchor":"plugin-enabledisableinstall-now-warn-when-settings-file-is","canonical_anchor":"plugin-enabledisableinstall-now-warn-when-settings-file-is","heading":"Plugin commands now warn when the settings file is broken","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-enabledisableinstall-now-warn-when-settings-file-is","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Plugin commands now warn when the settings file is broken\n\nInstalling, enabling or disabling a plugin now warns if the settings file it wrote to will not load and is being ignored\n\n**What**\n\nWhen you install, enable or disable a plugin, Claude Code writes the change to a settings file. A plugin is an add-on package that extends Claude Code. If that file does not load, for example because it contains an error, the command now adds a warning to its message.\n\nThe warning says the file does not load, so Claude Code ignores the whole file, including anything this command wrote there. It asks you to fix the file and run the command again. The same warning appears in the command's JSON output.\n\nThe `plugin validate` command also gains an extra section of checks.\n\n**Why**\n\nBefore this change, a plugin change could be lost without any notice because the settings file was broken. Now you are told, and you can fix it.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}