{"version":"2.1.267","anchor":"new-consolidated-plugins-effectively-enabled-check-svr","canonical_anchor":"new-consolidated-plugins-effectively-enabled-check-svr","heading":"New consolidated 'plugins effectively enabled' check svr","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-consolidated-plugins-effectively-enabled-check-svr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New consolidated 'plugins effectively enabled' check `svr`\n\nA new internal check consolidates several conditions that decide whether plugins count as effectively enabled\n\n**Unclear.** The finding does not say what `M7e()` checks or what visible effect the consolidation has for users.\n\n**What**\n\nClaude Code now uses a single combined check to decide whether plugins are effectively enabled, folding together several existing conditions: an internal capability check, whether everything is disabled, whether hooks (automated scripts that run on events) are disabled, and whether the setup is management-only. This feeds into the existing security-default calculation.\n\n**Why**\n\nThis is an internal consolidation of logic that previously existed as separate checks. It should not change behavior on its own, but it centralizes how Claude Code decides when plugin-related security defaults apply.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}