{"version":"2.1.221","anchor":"plugin-install-now-tells-you-when-higher-precedence-settings","canonical_anchor":"plugin-install-now-tells-you-when-higher-precedence-settings","heading":"Plugin install now tells you when higher-precedence settings keep it disabled","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/plugin-install-now-tells-you-when-higher-precedence-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Plugin install now tells you when higher-precedence settings keep it disabled\n\nPlugin install now tells you when a higher-priority settings file is what's keeping the plugin disabled.\n\n**What**\n\nAfter a plugin install, Claude Code checks the settings layers above the install scope for `enabledPlugins[id]` set to false and reports that case with its own message.\n\n**Details**\n\n- walks each higher-precedence settings layer rather than only reading the install scope\n- distinguished in the install result from the ordinary \"disabled by default\" outcome, with a distinct message\n\n**Evidence**\n\n`This plugin is disabled in your settings`\n\n- Area: Plugins\n- Names: `enabledPlugins`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}