Plugin install now tells you when a higher-priority settings file is what's keeping the plugin disabled.
What's wrong with this entry?
After a plugin install, Claude Code checks the settings layers above the install scope for enabledPlugins[id] set to false and reports that case with its own message.
- walks each higher-precedence settings layer rather than only reading the install scope
- distinguished in the install result from the ordinary "disabled by default" outcome, with a distinct message
This plugin is disabled in your settings
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Skills discovery skips disabled plugins
Both mention enabled
-
v2.1.228
Gateway can admit Claude Enterprise callers without its own login (customer-routed inference)
Both mention enabled
-
v2.1.228
Self-hosted gateway can admit callers with Anthropic-issued JWTs
Both mention enabled