[BUG] Plugin marketplace shows 'installed' for project-scoped plugins from other projects

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?

The plugin marketplace shows a plugin as "installed" when it's only installed at project scope in a different project. However, the /plugin Installed tab correctly does not show the plugin in the current project context.

This creates confusion because the marketplace suggests the plugin is available, but it actually isn't in the current project.

What Should Happen?

The marketplace should only show "installed" status for plugins that are actually available in the current context:

• Plugins installed at user scope (globally available)
• Plugins installed at project scope in the current project

Plugins installed at project scope in other projects should not appear as "installed" in the marketplace when working in a different project.

Steps to Reproduce

1. Open Claude Code in Project A
2. Run /plugin and install a plugin (e.g., superpowers) with project scope
3. Verify the plugin appears in the Installed tab for Project A
4. Open Claude Code in Project B (a different project)
5. Run /plugin → go to Installed tab → plugin is NOT listed (correct behavior)
6. Run /plugin → go to Discover/Marketplace tab → plugin shows as "installed" (incorrect)

Is this a regression?

I don't know

Claude Code Version

2.1.7 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Environment details:

• macOS 26.1 (Build 25B78)
• Running inside tmux 3.5a
• Terminal: tmux-256color
• Shell: zsh

Settings file locations checked:

• User scope (~/.claude/settings.json): plugin NOT present
• Project scope (.claude/settings.json in current project): plugin NOT present
• Plugin is only in the other project's .claude/settings.json

The /plugin Installed tab behavior is correct (respects scope), but the marketplace status indicator seems to check all settings files globally rather than respecting the current scope context.