[FEATURE] Setting to allow disabling managed plugins

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

We have encountered a bifurcation of intent with managed plugins provided via managed-settings.json. In some cases, we use them to enforce rigid standards, and it should not be possible to disable them; in other cases, which are more common in my experience, we use them to provide a set of good defaults for Claude Code, which users may eventually prefer to disable as they develop more targeted capabilities that may clash with the defaults.

I have several company-internal plugins that are useful to deploy to all devs as a set of good defaults, making Claude Code effective in our ecosystem immediately upon install.

However, as devs become experienced with the tooling, they may prefer to disable certain plugins in favour of more custom solutions e.g. replacing a more general company default skill plugin with a custom skill more targeted to their needs. Today, in this scenario, they would be unable to disable the managed plugins which they aim to replace.

Proposed Solution

It would be useful to have a control in the enabledPlugins block of managed-settings.json to specify whether each plugin may be disabled by users.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_