{"version":"2.1.307","anchor":"plugin-enabledisable-managed-settings-check-replaced-and-f","canonical_anchor":"plugin-enabledisable-managed-settings-check-replaced-and-f","heading":"Enabling and disabling plugins checks more settings before acting","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/plugin-enabledisable-managed-settings-check-replaced-and-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Enabling and disabling plugins checks more settings before acting\n\nTurning a plugin on or off now treats a plugin enabled through command-line flag settings as already on, and the disable message carries extra text\n\n**What**\n\nA plugin is an add-on that extends Claude Code. Three things change when you enable or disable one from the command line:\n\n- Organization-managed settings: the check for whether your organization's settings already control the plugin now goes through a shared check rather than being done separately here.\n\n- Already enabled: when you ask to enable a plugin, Claude Code now also counts it as enabled if it was switched on through settings passed with a command-line flag, and reports that nothing needs doing.\n\n- Success message: the message shown after a plugin is disabled now has extra text added to the end.\n\n**Why**\n\nIf you use Claude Code from the command line, the messages you see when enabling or disabling plugins may differ from before.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}