Plugins installed with local scope in one project are hidden from marketplace in other projects

Bug Description

A plugin installed with "local" scope in Project A is not visible in the plugin marketplace when working in Project B. This makes it impossible to install the plugin for Project B through the normal marketplace UI.

Expected Behavior

Plugins installed with "local" scope should only be considered "installed" for the specific project they were installed in. The marketplace in other projects should still show the plugin as available for installation.

Actual Behavior

The marketplace appears to treat the plugin as "already installed" globally, hiding it from the marketplace listing in all projects — even ones where it is not installed and not available.

Steps to Reproduce

1. Install a plugin (e.g., frontend-design) with local scope in Project A
2. Open Claude Code in Project B (a different project)
3. Open the plugin marketplace (/plugin)
4. The plugin does not appear in the marketplace, so there is no way to install it for Project B

Environment Details

From installed_plugins.json, the plugin entry looks like:

"frontend-design@claude-plugins-official": [
  {
    "scope": "local",
    "projectPath": "/path/to/project-a",
    "installPath": "...",
    "version": "aa296ec81e8c",
    "installedAt": "2026-01-25T05:17:11.968Z",
    "lastUpdated": "2026-02-21T00:01:35.743Z"
  }
]

Note: scope is "local" and projectPath points to a different project. Despite this, the plugin is hidden from the marketplace in all other projects.

Workaround

Manually editing ~/.claude/plugins/installed_plugins.json to add an entry for the second project.

Platform

• Linux (Ubuntu-based)
• Claude Code CLI