Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Plugin cache not refreshed when version number is unchanged after uninstall/install [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#45542•Fetched 2026-04-09 08:02:58
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
wish0728wish0728
Participants
github-actions[bot]github-actions[bot]wish0728wish0728
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

Fix Action

Workaround

Manually sync the cache from the marketplace source:

rm -rf ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills
cp -R ~/.claude/plugins/marketplaces/<marketplace>/plugins/<plugin>/skills ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills

Code Example

rm -rf ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills
cp -R ~/.claude/plugins/marketplaces/<marketplace>/plugins/<plugin>/skills ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills
RAW_BUFFERClick to expand / collapse

Bug Description

When a plugin's source files are updated in the marketplace repo (new git commits merged) but the version number in plugin.json remains the same, both /plugin update and /plugin uninstall followed by /plugin install fail to refresh the cached plugin files.

Steps to Reproduce

  1. Install a plugin from a marketplace: /plugin install performance-review@buzzvil-plugins (version 1.0.0)
  2. Push new commits to the marketplace repo (e.g., update skill files, fix YAML parsing, add features)
  3. The marketplace local repo fetches the latest commits successfully
  4. Run /plugin update performance-review@buzzvil-plugins — outputs "already at the latest version (1.0.0)"
  5. Run /plugin uninstall then /plugin install — cache files are still stale

Expected Behavior

Plugin cache should be refreshed when the git commit SHA has changed, even if the version string remains the same. Either:

  • /plugin update should compare git commit SHAs (not just version strings)
  • /plugin install (after uninstall) should always copy fresh files from the marketplace source

Actual Behavior

  • /plugin update only compares version strings, so same version = "already up to date"
  • /plugin install after uninstall does not overwrite the cached files
  • installed_plugins.json retains the old gitCommitSha even after reinstall

Evidence

Marketplace source (latest) vs Cache (stale):

  • Source SKILL.md: 39,002 bytes
  • Cache SKILL.md: 34,966 bytes

The marketplace local repo has the latest commit (0285b86), but the cache still has files from the older commit (13453e5).

Workaround

Manually sync the cache from the marketplace source:

rm -rf ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills
cp -R ~/.claude/plugins/marketplaces/<marketplace>/plugins/<plugin>/skills ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills

Environment

  • Claude Code version: 2.1.97
  • OS: macOS (Darwin 25.3.0)

extent analysis

TL;DR

Update the plugin cache by comparing git commit SHAs instead of just version strings to ensure freshness.

Guidance

  • Modify the /plugin update command to compare git commit SHAs in addition to version strings to detect changes in the marketplace repo.
  • Consider adding a flag to the /plugin install command to force a refresh of the cached files from the marketplace source.
  • Verify the fix by checking the installed_plugins.json file for the updated gitCommitSha after running the modified /plugin update or /plugin install command.
  • Test the workaround provided in the issue by manually syncing the cache from the marketplace source and verify that the cache files are updated correctly.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a change in the logic of the /plugin update and /plugin install commands.

Notes

The provided workaround can be used as a temporary solution, but a permanent fix would require modifying the plugin update and install logic to compare git commit SHAs.

Recommendation

Apply the workaround by manually syncing the cache from the marketplace source until a permanent fix is implemented that updates the /plugin update and /plugin install commands to compare git commit SHAs.

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…
#tokenizer error#prompt formatting#chain error#conversation history#tool integration

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 Plugin cache not refreshed when version number is unchanged after uninstall/install [1 comments, 2 participants]