-
Notifications
You must be signed in to change notification settings - Fork 89
Description
Summary
This is an informational tracking issue to help users who encounter flaky plugin installation when using superpowers-marketplace.
This is NOT a bug in this repository - it's an upstream Claude Code issue. Creating this issue here because:
- No Discussions section available
- Users searching for "superpowers install" issues may find this helpful
- Can serve as a place to collect workarounds and track upstream fixes
The Problem
The superpowers plugin exists in both claude-plugins-official AND superpowers-marketplace. When Claude Code's plugin installer encounters this, it may:
- Match on plugin name only, ignoring the marketplace qualifier
- Report the wrong marketplace in error messages
- Refuse to install even with fully-qualified name
Example error:
❯ /plugin install superpowers@superpowers-marketplace
⎿ Plugin 'superpowers@claude-plugins-official' is already installed. Use '/plugin' to manage
existing plugins.Note: User requested @superpowers-marketplace but error refers to @claude-plugins-official.
This particularly affects users installing plugins on a per-repository basis (project/local scope). The behavior is flaky - sometimes works, sometimes doesn't.
Upstream Issues (Claude Code)
- Problem hypothesis: [BUG] Plugin install matches wrong marketplace when same plugin name exists in multiple marketplaces anthropics/claude-code#20593
- Related scope issues: Bug: Project-scoped plugins incorrectly detected as installed globally anthropics/claude-code#14202
Verified Workaround
Manual editing of ~/.claude/plugins/installed_plugins.json + creating .claude/settings.json with enabledPlugins works:
After restarting Claude Code, the plugin appears correctly in the Installed tab.
Detailed workaround with code snippets: anthropics/claude-code#14202 (comment)
Resolution
Kind suggestion on closing criteria for issue:
- Upstream Claude Code issues are fixed, OR
- A
TROUBLESHOOTING.mdorFAQ.mdis added to this repo with this information
Note: This issue was created to help other users who may encounter this problem. Feel free to add additional workarounds or information in comments.