{"version":"2.1.321","anchor":"plugin-enable-check-changes-default-for-some-plugins","canonical_anchor":"plugin-enable-check-changes-default-for-some-plugins","heading":"Some plugins can now start enabled when an extra condition holds","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/plugin-enable-check-changes-default-for-some-plugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Some plugins can now start enabled when an extra condition holds\n\nSome plugins with no saved on or off choice can now count as enabled when a further condition is met\n\n**Unclear.** It is not clear which plugins this affects or what the two extra checks test.\n\n**What**\n\nWhen you have not turned a plugin on or off yourself, Claude Code decides a default. That default can now be enabled in more cases: a plugin that was previously off by default can now count as enabled when two further checks pass. A choice you have made yourself still wins.\n\n**Why**\n\nThis could change which plugins are on without you having switched them on.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}