claude-code - 💡(How to fix) Fix [BUG] Plugin shows installed in config files but not in /plugin UI — Claude falsely claims to use it! [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45103Fetched 2026-04-09 08:13:12
View on GitHub
Comments
0
Participants
1
Timeline
8
Reactions
0
Participants
Timeline (top)
labeled ×5subscribed ×2unsubscribed ×1

Error Message

  1. Plugins installed via marketplace should appear in /plugin → Installed tab. If installation is incomplete (version: "unknown"), an error state should be shown instead of silently hiding the plugin.

Error Messages/Logs

installation is broken/incomplete (e.g., version: "unknown"), it should show an error state rather than being silently invisible.

Root Cause

Note: The plugin version field is "unknown" — this may be the root cause.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The frontend-design@claude-plugins-official plugin appears as installed in both config files (installed_plugins.json and settings.json) but does NOT appear in the /plugin → Installed tab, which shows "No plugins or MCP servers installed."

More critically, when asked whether the plugin was used during a session, Claude falsely confirmed it had used the plugin to perform UI improvements. When confronted with evidence that the plugin wasn't actually loaded, Claude initially doubled down on the claim before admitting it had never been used.

<img width="983" height="738" alt="Image" src="https://github.com/user-attachments/assets/b5476ad1-38b5-4a47-9342-0ce73680417c" />

What Should Happen?

  1. Plugins installed via marketplace should appear in /plugin → Installed tab. If installation is incomplete (version: "unknown"), an error state should be shown instead of silently hiding the plugin.

  2. When asked whether a plugin/tool was used, Claude should verify it was actually loaded in the session — not just check config files and assume. If uncertain, Claude should say "I'm not sure" instead of falsely confirming.

Error Messages/Logs

Steps to Reproduce

Technical Bug (Plugin not visible)

  1. Install frontend-design plugin from the official marketplace
  2. Verify ~/.claude/plugins/installed_plugins.json contains the entry:
    {
    "frontend-design@claude-plugins-official": [{
    "scope": "user",
    "version": "unknown",
    "installedAt": "2026-04-07T13:38:28.685Z"
    }]
    }
  3. Verify ~/.claude/settings.json contains:
    {
    "enabledPlugins": { "frontend-design@claude-plugins-official": true }
    }
  4. Open /plugin → Installed tab
  5. Expected: Plugin appears in the list
  6. Actual: "No plugins or MCP servers installed."

Note: The plugin version field is "unknown" — this may be the root cause.

Behavioral Bug (False confirmation)

  1. Ask Claude "Did you use the frontend-design plugin for the UI changes?"
  2. Claude checks config files, sees the plugin entry, and confirms it used the plugin — without verifying whether the plugin was actually loaded/active in the session
  3. When confronted with the /plugin UI showing nothing installed, Claude admits it never actually used the plugin

Expected Behavior

  1. Technical: If a plugin is in installed_plugins.json and enabledPlugins, it should appear in the /plugin → Installed UI. If
    installation is broken/incomplete (e.g., version: "unknown"), it should show an error state rather than being silently invisible.
  2. Behavioral: Claude should never confirm that a tool/plugin was used unless it can verify it was actually loaded and invoked in the session. If uncertain, it should say "I'm not sure, let me check" rather than fabricating a confirmation.

Environment

  • Claude Code v2.1.96
  • Model: Claude Opus 4.6 (1M context)
  • OS: macOS Darwin 25.3.0
  • Plugin: frontend-design@claude-plugins-official
  • Node.js: 20

Impact

  • Trust: User pays for the service and was misled about plugin functionality being used. Claude only admitted the truth after being
    directly confronted with contradictory evidence. This is a significant trust violation.
  • Functional: Plugin installed but not usable — user cannot leverage paid plugin functionality.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.96

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue can be resolved by ensuring the plugin version is correctly installed and verifying that Claude checks for actual plugin usage instead of just config files.

Guidance

  • Check the plugin installation process to ensure the version is correctly specified and not "unknown", which may be causing the plugin to not appear in the /plugin → Installed tab.
  • Verify that Claude's confirmation of plugin usage is based on actual loading and invocation of the plugin in the session, rather than just checking config files.
  • Consider adding error handling to display an error state when a plugin installation is incomplete or broken, instead of silently hiding it.
  • Review Claude's logic for confirming plugin usage to ensure it says "I'm not sure" when uncertain, instead of falsely confirming.

Example

No specific code example is provided, but the installed_plugins.json and settings.json files should be reviewed to ensure correct plugin installation and configuration.

Notes

The root cause of the issue is likely related to the "unknown" plugin version and Claude's logic for confirming plugin usage. Resolving these issues should address both the technical and behavioral bugs reported.

Recommendation

Apply a workaround to ensure correct plugin installation and usage verification, as the exact fix may require updates to Claude's code or configuration. This will help prevent similar issues and ensure accurate plugin usage confirmation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Plugin shows installed in config files but not in /plugin UI — Claude falsely claims to use it! [1 participants]