claude-code - 💡(How to fix) Fix Plugin update flow on Claude Code Desktop fails to detect newer versions [1 comments, 2 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#54276Fetched 2026-04-29 06:31:40
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1

Claude Code Desktop's "Update" button stays greyed out with the tooltip "On latest version" even when the marketplace has published a newer plugin version. All three documented Desktop-accessible update paths fail. The only working refresh requires a terminal, which non-technical users do not have access to.

Root Cause

claude plugin marketplace update <marketplace-name> from a terminal force-pulls the on-disk marketplace clone, after which an uninstall + reinstall through Desktop's Customize panel installs the new version (because the clone is now fresh).

Fix Action

Fix / Workaround

Working workaround (terminal only)

RAW_BUFFERClick to expand / collapse

Summary

Claude Code Desktop's "Update" button stays greyed out with the tooltip "On latest version" even when the marketplace has published a newer plugin version. All three documented Desktop-accessible update paths fail. The only working refresh requires a terminal, which non-technical users do not have access to.

Environment

  • Claude Code Desktop v2.1.121
  • macOS Darwin 25.4.0
  • Test plugin: nfrith/als
  • Marketplace source: { "source": "git", "url": "https://github.com/nfrith/als.git" }

Reproduction

  1. In Desktop, add a marketplace and install a plugin. Note the version in Customize → <plugin>.
  2. As the plugin author, bump plugin.json version (e.g. 0.1.10.1.2), commit, push to the marketplace's default branch.
  3. In Desktop, open Customize → <plugin> and observe the Update button.

Expected

Update button activates. Clicking installs the new version.

Actual

Button stays greyed with tooltip "On latest version". The platform never observes the new version.

Additional Desktop-side paths tested — all fail

ActionResult
Click UpdateGreyed; "On latest version"
Quit Desktop, reopenStill on cached version
Enable autoUpdate: true on the marketplace via CLI, restart DesktopStill on cached version
Uninstall → close Desktop → reopen → remove marketplace → re-add marketplace → reinstall pluginStill installs the old version — Desktop's "re-add marketplace" reuses the existing on-disk clone at ~/.claude/plugins/marketplaces/<name>/ rather than fresh-cloning from origin

Version-strategy permutations tested — all fail

Per the version resolution docs:

  • version in plugin.json only, pre-release format (0.1.0-beta.280.1.0-beta.32) — fails
  • version in plugin.json only, clean semver (0.1.10.1.2) — fails
  • version in marketplace.json only (0.1.0-beta.310.1.0-beta.32) — fails
  • No version anywhere (commit-SHA path, with ref: stable git-tag pin moved forward) — fails

In all cases, Desktop reports "On latest version".

Working workaround (terminal only)

claude plugin marketplace update <marketplace-name> from a terminal force-pulls the on-disk marketplace clone, after which an uninstall + reinstall through Desktop's Customize panel installs the new version (because the clone is now fresh).

Impact

Non-technical users on Claude Code Desktop have no working path to receive plugin updates. Plugin authors cannot ship fixes or new features to existing Desktop installs without instructing every user to open a terminal.

extent analysis

TL;DR

The issue can be temporarily worked around by using the terminal command claude plugin marketplace update <marketplace-name> to force-update the marketplace, followed by uninstalling and reinstalling the plugin through the Desktop interface.

Guidance

  • The problem seems to stem from the Desktop application not properly updating its local clone of the marketplace, leading to it not recognizing new plugin versions.
  • To verify if the workaround is effective, check the plugin version in Customize → <plugin> after running the terminal command and reinstalling the plugin.
  • The autoUpdate: true setting on the marketplace does not seem to be effective in this case, suggesting a potential issue with the automatic update mechanism.
  • Further investigation into the version resolution and release channels documentation may provide insight into why the different version-strategy permutations tested all failed.

Example

No code snippet is provided as the issue seems to be related to the application's behavior rather than a specific code error.

Notes

The provided workaround requires terminal access, which may not be feasible for non-technical users. A more permanent solution would involve fixing the automatic update mechanism within the Desktop application.

Recommendation

Apply the workaround using the terminal command, as it is the only known method to force-update the marketplace and allow plugin updates. This is not a permanent solution but provides a temporary way to update plugins until the underlying issue is resolved.

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