{"version":"2.1.285","anchor":"plugin-enabledisable-errors-carry-more-structured-data","canonical_anchor":"plugin-enabledisable-errors-carry-more-structured-data","heading":"Plugin enable and disable errors now say more about what blocked them","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/plugin-enabledisable-errors-carry-more-structured-data","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Plugin enable and disable errors now say more about what blocked them\n\nFailed plugin enable or disable results now carry the governing scope, whether to disable first, and related dependencies\n\n**Unclear.** What the new step run before enabling or disabling does is not known.\n\n**What**\n\nPlugins are add-ons that extend Claude Code. When enabling or disabling one fails, the result used to hold only an error code and a message. It now also includes:\n\n- `governingScope`, which settings level controls the plugin\n\n- `disableFirst`, whether something must be disabled first\n\n- `dependencies`, the plugins involved\n\nEnabling and disabling also run a new step beforehand, and disabling now looks up the plugin's canonical id (its one official name).\n\n**Why**\n\nPrograms that manage plugins can react to a failure, for example by disabling a dependency first, instead of only showing a message.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}