claude-code - 💡(How to fix) Fix Plugin uninstall does not fully clean up across all scopes [1 participants]

TL;DR

The issue can be mitigated by modifying the /plugin uninstall command to remove the plugin from all scopes or by prompting the user to select which scope to uninstall from.

Guidance

• The current implementation of /plugin uninstall only removes the plugin from one scope, leaving behind enabledPlugins entries in other settings files.
• To verify the issue, check the enabledPlugins entries in both ~/.claude/settings.json and .claude/settings.local.json after running /plugin uninstall.
• A potential workaround is to modify the uninstall command to accept an optional --scope parameter, allowing users to specify which scope to uninstall from.
• The enabledPlugins entries should be updated accordingly to reflect the uninstallation.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The solution may require modifications to the Claude Code CLI and its underlying settings management system. The exact implementation details are not provided in the issue.

Recommendation

Apply workaround: Modify the /plugin uninstall command to accept an optional --scope parameter or prompt the user to select which scope to uninstall from, to ensure that the plugin is properly removed from all scopes. This approach allows for a more flexible and user-friendly uninstallation process.