Plugins from third-party marketplaces don't appear in /plugin list

Status Closed — not planned
Maintainer reply None cached
Activity 10 comments · opened Jan 7, 2026 · closed Mar 17, 2026

Bug Description

Plugins installed from third-party marketplaces (non-official) don't appear in the /plugin list command output, even though they are correctly installed and registered in installed_plugins.json.

Steps to Reproduce

  1. Add a third-party marketplace (e.g., claude-code-workflows from wshobson/agents)
  2. Install a plugin from that marketplace: /plugin install git-pr-workflows@claude-code-workflows
  3. Run /plugin or /plugin list to view installed plugins
  4. The plugin doesn't appear in the list
  5. Try to install again: /plugin install git-pr-workflows@claude-code-workflows
  6. Get message: "Plugin 'git-pr-workflows@claude-code-workflows' is already installed"

Expected Behavior

All installed plugins should appear in the /plugin list, regardless of which marketplace they came from.

Actual Behavior

  • The install command correctly recognizes the plugin is already installed
  • The plugin files exist in ~/.claude/plugins/cache/
  • The plugin is registered in ~/.claude/plugins/installed_plugins.json
  • But the list command shows nothing (or only official plugins)

Environment

  • OS: Windows 11
  • Claude Code Version: Latest (as of 2025-01-07)

Additional Context

The installed_plugins.json shows plugins with "isLocal": true flag. This might be causing the filtering issue:

"git-pr-workflows@claude-code-workflows": [
  {
    "scope": "user",
    "installPath": "C:\Users\Omar\.claude\plugins\cache\claude-code-workflows\git-pr-workflows\1.2.1",
    "version": "1.2.1",
    "installedAt": "2026-01-03T15:52:03.936Z",
    "lastUpdated": "2026-01-03T15:52:03.936Z",
    "isLocal": true
  }
]

The known_marketplaces.json correctly shows both marketplaces:

  • claude-plugins-official (from anthropics/claude-plugins-official)
  • claude-code-workflows (from wshobson/agents)

🤖 Generated with Claude Code

View original on GitHub ↗

10 Comments

OmarAbdo · 9 months ago

Update: Plugins Not Loading (More Severe Than Display Bug)

After testing, the plugins from third-party marketplaces are not functional - they fail to load entirely, not just display.

Test Results

Attempted to invoke skills provided by the installed plugin:

/git-workflow --no-push
→ Error: Unknown skill: git-workflow

/git-pr-workflows:git-workflow  
→ Error: Unknown skill: git-pr-workflows:git-workflow

/pr-enhance
→ Error: Unknown skill: pr-enhance

Plugin Structure Verified

The plugin files are correctly installed:

~/.claude/plugins/cache/claude-code-workflows/git-pr-workflows/1.2.1/
├── agents/
│   └── code-reviewer.md
└── commands/
    ├── git-workflow.md
    ├── onboard.md
    └── pr-enhance.md

Summary

  1. ✅ Plugin files exist on disk
  2. ✅ Plugin registered in installed_plugins.json
  3. ✅ Install command recognizes plugin as installed
  4. ❌ Plugin doesn't appear in /plugin list
  5. ❌ Plugin skills/commands are not loaded and cannot be invoked

This suggests Claude Code is not loading plugins from third-party marketplaces at runtime, making them completely non-functional.

🤖 Generated with Claude Code

github-actions[bot] · 9 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/14815

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

noah-foltz · 9 months ago

I'm getting this with ralph-wiggum on latest as well which is an official plugin.

claude plugin install ralph-wiggum@claude-plugins-official
Installing plugin "ralph-wiggum@claude-plugins-official"...
✘ Failed to install plugin "ralph-wiggum@claude-plugins-official": Plugin "ralph-wiggum" not found in marketplace "claude-plugins-official"

I also already have it installed, but its errored out with the same doesn't exist message in Claude Code's plugin interface.

OmarAbdo · 9 months ago

I'm suspecting the settings.json file for claude (on a user level) I recreated it with the same content expect with more permissions, and then this bug started to show

yzavyas · 9 months ago

Same workaround applies: use a SessionStart hook with type: command to inject plugin discovery context at session start.

Example: https://github.com/yzavyas/claude-1337/blob/main/plugins/core-1337/hooks/session-start.sh

github-actions[bot] · 8 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

dylanb · 8 months ago

We've spent considerable time troubleshooting this with multiple structure variations, and the marketplace successfully adds every time, but plugins are never discoverable.

We tried

  1. Relative path source ("source": "./plugins/dequelabs")
  • Result: Marketplace adds successfully, plugin not found
  1. External GitHub source

"source": {
"source": "github",
"repo": "dequelabs/dequelabs-claude-plugin"
}

  • Result: marketplace adds successfully but plugin still not found
  1. Different plugin naming
  • Tried matching marketplace name ("dequelabs")
  • Tried different name to avoid conflicts ("dequelabs-plugin")
  • Result: No difference
  1. Verified plugin structure matches official marketplace
  • Compared with code-review plugin from official marketplace
  • Structure and file formats match
  • Result: Still not discoverable

attaching the final version with full code to help with debugging

dequelabs-marketplace-bug-report.zip

github-actions[bot] · 7 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

OmarAbdo · 7 months ago

There were 2 installations for claude code on my machine and one of them had that bug. I removed both and installed the latest version and then everything worked as expected

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.