claude-code - 💡(How to fix) Fix Discover tab shows plugins that are already installed at project scope [1 participants]

TL;DR

The Discover tab in the /plugin section should filter out plugins already installed at the project scope, which can be achieved by modifying the filtering logic to account for project-scoped installations recorded in .claude/settings.json.

Guidance

• Review the filtering logic in the Discover tab to ensure it correctly handles project-scoped plugin installations by checking the enabledPlugins section in .claude/settings.json.
• Verify that the enabledPlugins list in .claude/settings.json is correctly updated when plugins are installed at the project scope.
• Compare the implementation with the inverse issues (#19743, #28739, #14185) to identify potential discrepancies in the filtering logic.
• Consider adding a default filter or sorting mechanism to prioritize uninstalled plugins in the Discover results.

Example

No explicit code example is provided due to the lack of specific implementation details, but the filtering logic might involve checking the enabledPlugins list in .claude/settings.json and excluding matching plugins from the Discover results.

Notes

The solution may require adjustments to the Claude Code CLI or the plugin installation mechanism to ensure correct handling of project-scoped installations. The provided related issues suggest that the filtering logic has been problematic in the past, so careful review and testing are necessary.

Recommendation

Apply a workaround by modifying the filtering logic in the Discover tab to correctly handle project-scoped plugin installations, as upgrading to a fixed version is not explicitly mentioned in the issue. This approach allows for a targeted fix without relying on external updates.