[BUG] /plugin detail view shows errors from wrong marketplace when same plugin name exists in multiple marketplaces

Resolved 💬 4 comments Opened Mar 6, 2026 by kitaekatt Closed Mar 10, 2026

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?

When a plugin with the same name is enabled in two different marketplaces, the /plugin detail view displays errors from the wrong marketplace entry.

Example: bootstrap is enabled in both update03 and plugins-kit marketplaces:

"enabledPlugins": {
    "bootstrap@update03": true,
    "bootstrap@plugins-kit": true,
    "unreal-kit@plugins-kit": true
}

The bootstrap plugin does not exist in plugins-kit, so that entry correctly generates an error. However, when drilling into the detail view for bootstrap @ update03 (which IS valid and working), the UI shows:

bootstrap @ update03
Scope: user
Version: 0.9.0
Status: Enabled

1 error:
  Plugin 'bootstrap' not found in marketplace 'plugins-kit'
  → Plugin may not exist in marketplace 'plugins-kit'

The error belongs to bootstrap@plugins-kit, not bootstrap@update03. The detail view appears to match errors by plugin name only, ignoring the marketplace qualifier.

What Should Happen?

The /plugin detail view for bootstrap@update03 should show no errors (since the plugin exists and works in the update03 marketplace).

The error about plugins-kit should only appear when viewing the bootstrap@plugins-kit entry.

Steps to Reproduce

  1. Add two marketplaces (e.g., update03 and plugins-kit)
  2. Enable a plugin that exists in one marketplace but not the other, using the same plugin name in both enabledPlugins entries:

``json
"enabledPlugins": {
"bootstrap@update03": true,
"bootstrap@plugins-kit": true
}
``

  1. Run /plugin and navigate to the Installed tab
  2. Select bootstrap @ update03
  3. Observe: The detail view shows an error about plugins-kit, which is unrelated to this entry

Related Issues

  • #20593 — Same root cause (plugin name matching ignores marketplace qualifier) but in the install path rather than the detail view

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

Latest

Platform

Anthropic API

Operating System

Windows (MINGW64)

Terminal/Shell

bash

Additional Information

The root cause is likely the same as #20593 — error lookup/display uses plugin name only instead of the full qualified name@marketplace key.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗