Desktop app sessions keep loading old plugin version after 'claude plugin update'
Status Fixed / completed
Reported on v2.1.214
Maintainer reply None cached
Activity 1 comment · opened Aug 3, 2026 · closed Aug 3, 2026
Environment
- Claude desktop app 1.24012.9 (macOS, Darwin 24.6.0)
- Claude Code CLI 2.1.214
- Plugin installed at user scope from a marketplace with a local-directory source
Steps to reproduce
- Install plugin
foov0.1.0 from a directory-source marketplace (claude plugin marketplace add <checkout>+claude plugin install foo@<marketplace>). Its skills load in desktop app sessions. - Add a new skill to the plugin in the checkout and bump
plugin.jsonto 0.2.0. - Run
claude plugin update foo@<marketplace>— reports success ("updated from 0.1.0 to 0.2.0"). - Verify on disk:
~/.claude/plugins/cache/<marketplace>/foo/0.2.0/exists and contains both skillsinstalled_plugins.jsonentry points at the 0.2.0installPathenabledPluginsin~/.claude/settings.jsonhasfoo@<marketplace>: true
- Fully quit the desktop app (Cmd+Q), reopen, start a new conversation.
Expected
The session loads the plugin's 0.2.0 skills (including the newly added one).
Actual
Sessions keep loading the 0.1.0 skill set — the new skill never appears. /reload-skills in-session rescans and reports "no changes". /reload-plugins is not available in the desktop app, so there is no in-session way to force plugin re-resolution.
Notes
- Skill discovery itself is fine: symlinking the new skill directory into
~/.claude/skills/makes it appear after/reload-skills. The stale part is plugin version resolution at desktop session init — it appears to keep using the orphaned 0.1.0 cache directory rather than the installPath recorded ininstalled_plugins.json. - Not yet verified whether terminal CLI sessions resolve 0.2.0 correctly (desktop-only observation).
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗