You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.307,
ImprovementsSection of the release
What
Plugins 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.
If 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)".
Why
If 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged the axScreenReader setting and CLAUDE_AX_SCREEN_READER in a settings env block to apply only from user, managed or --settings…
