[Bug] Plugin marketplace discovery broken after update to v2.0.62
Resolved 💬 16 comments Opened Dec 9, 2025 by CPaulBeroe Closed Feb 14, 2026
💡 Likely answer: A maintainer (whyuan-cc, contributor)
responded on this thread — see the highlighted reply below.
Bug Description
- Title: "Plugin system broken - /plugin shows 'cannot find any marketplace' after working previously"
- Include: Windows, version 2.0.62, local marketplace was working, suddenly stopped\
\
Hey there is a new release of /plugins it looks like (changes in UI) and it completely stopped working for me which causes major headaches. It does not find the marketplace and hence my workflow distributing mcps to different plugins to save context is dead right now...
Environment Info
- Platform: win32
- Terminal: cursor
- Version: 2.0.62
- Feedback ID: 94026250-4cab-4fe3-a37d-08723ad12344
Errors
[{"error":"Error: Plugin path not found: C:\\Users\\Christian.paul\\Desktop\\figma-bilateral\\.claude\\plugins\\front-heavy-dev\n at o55 (file:///C:/Users/Christian.paul/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1564:6171)\n at r55 (file:///C:/Users/Christian.paul/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1564:5721)\n at async file:///C:/Users/Christian.paul/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1564:14571","timestamp":"2025-12-09T13:37:35.471Z"},{"error":"Error: Request was aborted.\n at Gj.makeRequest (file:///C:/Users/Christian.paul/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1283:3940)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-12-09T13:39:39.689Z"},{"error":"Error: Command failed: C:\\Users\\Christian.paul\\AppData\\Roaming\\npm\\node_modules\\@anthropic-ai\\claude-code\\vendor\\ripgrep\\x64-win32\\rg.exe --files --glob **/.claude/plugins/installed_plugins.json --sort=modified --no-ignore --hidden C:\\Users\\Christian.paul\n\n at genericNodeError (node:internal/errors:983:15)\n at wrappedFn (node:internal/errors:537:14)\n at ChildProcess.exithandler (node:child_process:417:12)\n at ChildProcess.emit (node:events:519:28)\n at ChildProcess.emit (node:domain:489:12)\n at maybeClose (node:internal/child_process:1101:16)\n at ChildProcess._handle.onexit (node:internal/child_process:304:5)","timestamp":"2025-12-09T13:42:48.015Z"}]
16 Comments
---
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
---
Thanks for reporting. Based on my analysis of the error logs, this appears to be a configuration/state mismatch issue
The error Plugin path not found: C:\Users\Christian.paul\Desktop\figma-bilateral\.claude\plugins\front-heavy-dev indicates that:
You have a local directory marketplace registered at C:\Users\Christian.paul\Desktop\figma-bilateral\.claude\plugins
Could you explain if front-heavy-dev is the marketplace or plugin name?
How to fix: Reset and reconfigure
@whyuan-cc Thank you for responding, but the suggested workaround does not address the actual problem.
After extensive debugging over 3 days (including multiple crashes caused by Claude Code's own repair attempts), I managed to get the marketplace re-added via
/plugin marketplace add. That part now works.However, the moment I enable any plugin that contains MCPs, Claude Code crashes on startup with this error:
Error: ENOENT: no such file or directory, mkdir 'C:\Users\Christian.paul\AppData\Local\claude-cli-nodejs\Cache\C--Users-Christian-paul-Desktop-figma-bilateral\mcp-logs-plugin:full-on-dev:playwright'
The problem: Claude Code constructs MCP log directory names using colons (
plugin:pluginname:mcpname).Colons are illegal characters in Windows file paths (reserved for drive letters like
C:).This is not a configuration issue on my end. My
.mcp.jsonfiles contain no colons:```json
{
"mcpServers": {
"playwright": { ... },
"linear": { ... }
}
}
Claude Code internally adds the colons when constructing the log path.
Impact
My entire workflow is broken. Before v2.0.62, I had 8 plugins organizing ~20 MCPs by task type (dev, research, data, etc.). This allowed me to:
This workflow worked perfectly until Sunday. Now it's completely non-functional on Windows.
Or am I getting something wrong here?
Root Cause
The plugin system appears to have been developed/tested only on macOS/Linux where colons in paths are allowed. Windows requires a different delimiter (e.g., - or _).
I'm filing a separate issue for this specific bug. But I wanted to flag here that the original issue (#13471) is only partially resolved - marketplace discovery may work now, but plugins with MCPs remain completely broken on Windows.
Crash History
For context, here's what happened trying to fix this:
I have detailed incident documentation if helpful.
Apologize for breaking your usage. Thanks for providing the details. Let me investigate and fix this.
Odd, today I'm seeing broken plugins in worktrees too??
@ariccio thanks for reporting. Could you please share more details on what are broken, preferably with logs? Are you also on Windows?
(I'm not sure if this is only in worktrees)
I have several anthropic plugins installed at project level, and now the agents they come with are no longer available. The
Errorstab in/agentssays:claude itself did some debugging, and said something about a corrupted cache?
Extra odd. I asked claude to debug it again so I could share the error it found earlier... and now it's working. No idea what happened, I didn't approve any requests to run anything destructive.
did you restart Claude Code?
@CPaulBeroe we merged a couple of PRs to fix Windows specific issues. Please let us know if tomorrow's build works for you. Thanks
Will do!
The issue is fixed, thank you so much @whyuan-cc !
Here's what I've been seeing consistently. I need to run /plugins and update each marketplace, then relaunch claude code.
The key thing is that it happens every time I create a new worktree, claude instances launched in the worktree never have proper plugin configs until I update the marketplaces.
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.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.