Project-scope marketplace plugin install fails with "Workspace collection is not available" (3.13.25, Remote-WSL)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Environment

Cursor 3.13.25 (stable)
Windows 11 + WSL2 via Remote-WSL (anysphere.remote-wsl)
Individual / Elite account
Client metadata still shows layout: unifiedAgent (including after a cursor --classic attempt)
Summary
Installing a marketplace plugin with Project scope fails immediately. User scope works. Manually enabling plugins in .cursor/settings.json also works after reload.

Exact error

Failed to install marketplace plugin
Error: Workspace collection is not available
at Object.createWorkspaceReference (workbench.desktop.main.js)
… installPluginToProject …
Toast: Failed to install Figma, please try again or reload the window.

Expected
Project-scope install should enable the plugin for the open folder workspace.

Actual
installPluginToProject calls createWorkspaceReference on an empty/stub workspace collection that always throws.

Related context

[resolveAuthority(wsl,1)] NoResolverFound:
No remote extension installed to resolve wsl.
Also saw Extension Host UNRESPONSIVE in the same session.

Ask
When a folder workspace is open, Project install should use a real workspace collection, or fall back to the settings.json write path that doesn’t need createWorkspaceReference.

Steps to Reproduce

Repro

Open a WSL remote folder workspace
Marketplace → install any plugin (e.g. Figma) with Project scope
Confirm → failure toast + stack above
Already tried

Editor window (not Agents-only) — fails
Full quit + cursor --classic — still fails; metadata still unifiedAgent
Reload — fails
User-scope — works
Manual .cursor/settings.json plugins entry — works

Operating System

Windows 10/11

Version Information

Cursor 3.13.25

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The level of detail and the stack trace were super helpful.

We reproduced it. Project-scope install does crash on createWorkspaceReference, and it’s not related to your setup or WSL. It also happens in a regular local folder. I’ve passed this to the team and we’re tracking it. I can’t share a timeline yet, but I’ll post an update here once I have one.

For now, there are two working workarounds, and you already found both. Confirming these are the right options:

  • Install the plugin in User scope
  • Or add the plugin manually in .cursor/settings.json, then reload the window

Let me know if anything else comes up.

7

Wednesday, August 19, 2026 at 17:06 CEST same error here but I just tried using “/add-plugin” inside a conversation with an agent and it worked instantly. Hope this helps!