[BUG] /plugin command doesnt appear to handle enable/disable at project level

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Per the docs, one can enable/disable plugins at both the user and project levels. However, the /plugin command seems to have no notion of this. Enabling or disabling a plugin is always applied to my ~/.claude/settings.json. I _can_ manually manipulate the enabledPlugins prop in my project level settings files to get this working. Also, of course currently the cli doesn't support anything beyond validate for the plugin subcommand, so there's no workaround there either.

What Should Happen?

enable/disable of plugins should have the 'scoping' options

Error Messages/Logs

Steps to Reproduce

1. Configure a marketplace
2. Install a plugin

• OR -

1. Enable/disable a currently installed plugin

In neither case can you apply the change to the project

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.0.14

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

IntelliJ IDEA terminal

Additional Information

_No response_