{"version":"2.1.307","anchor":"plugins-policy-enabled-plugins-dependency-closure-and-se","canonical_anchor":"plugins-policy-enabled-plugins-dependency-closure-and-se","heading":"Clearer messages for plugins your organization or --settings keeps on","tier":"notice","area":"Plugins","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/plugins-policy-enabled-plugins-dependency-closure-and-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Clearer messages for plugins your organization or --settings keeps on\n\nChanging a plugin your organization's policy turns on is now refused, and a plugin kept on by `--settings` is shown as still enabled this session\n\n**What**\n\nPlugins are add-ons that give Claude Code extra commands and abilities. Your organization can turn plugins on through policy settings it manages. Claude Code now checks for this and refuses changes to such a plugin, reporting `managed_settings_override`.\n\nIf you disable a plugin that a settings file passed with `--settings` turns on, Claude Code now adds the note \"(still enabled this session: --settings keeps it on)\".\n\n**Why**\n\nIf you try to switch off a plugin that something else keeps on, you are told why it is still running instead of being left to guess.\n\n- Area: Plugins\n- Names: `--settings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}