claude-code - 💡(How to fix) Fix Plugin list shows plugins from all project scopes, not just the current project [1 comments, 2 participants]

TL;DR

Filtering or labeling plugins by their scope in the Claude Code plugin list is necessary to resolve the issue of plugins from other projects appearing without clear indication of their origin.

Guidance

• Review the .claude/settings.json files across projects to understand the scope of each enabled plugin.
• Consider modifying the plugin list display to include the project scope or a unique identifier for each plugin entry.
• Investigate the possibility of filtering the plugin list to only show plugins enabled in the current project scope.
• Examine the code responsible for populating the plugin list to determine how it retrieves plugin information and how it can be adjusted to respect project scopes.

Example

No specific code example can be provided without more details on the implementation, but the solution might involve adjusting the query or data processing logic that populates the plugin list, potentially incorporating project scope information.

Notes

The exact implementation details of the plugin list and scope filtering are not provided, so the guidance is focused on general steps towards a solution. Understanding how the .claude/settings.json files are processed and how plugin scopes are currently handled is crucial for a precise fix.

Recommendation

Apply a workaround by modifying the display of the plugin list to clearly indicate the scope of each plugin, as upgrading to a fixed version is not mentioned as an option in the provided context. This approach allows for a more immediate resolution to the issue of unclear plugin origins.