Glass Interface doesn't work with WSL

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The new Glass interface isn’t working with WSL even though the regular IDE works and the extension for WSL works as usual. I know this in Alpha, so just bringing this up so you ensure its well tested in WSL before stable release.

Steps to Reproduce

Try to use any project within WSL and it will show a pop up saying install wsl extension and reload but it doesn’t really work per se.

Expected Behavior

It should work.

Screenshots / Screen Recordings

Screenshot 2026-03-20 140020.png

Operating System

Windows 10/11

Version Information

Version: 2.7.0-pre.96.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: c6712eb06f4e47a06a31f4d7adf484bfcbf61cc0
Date: 2026-03-19T17:53:17.088Z
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

8 Likes

Hey, thanks for the report. This is a known issue. Glass doesn’t fully support remote connections yet like WSL and SSH. The team is aware, and your report helps us prioritize it.

For now, the workaround is to start Cursor in classic mode:

cursor --classic

This opens the standard UI where WSL works as usual.

You can also try File > New Window from Glass. That also opens the classic IDE.

Let me know if anything else comes up.

1 Like

Yeah yeah normal IDE works as usual, I just noticed this on glass so reported it and glad that it’s a known issue and being worked on. There are some other bugs on Glass which I have listed on the topic Glass Alpha Bugs List / Feedback - Ideas / Feedback - Cursor - Community Forum as a running list while I continue to use glass (currently using normally with windows as I am just orchestrating agents today so its fine that wsl isnt working for now)

1 Like

This is so frustrating.

Why are Win + WSL users constantly treated like the poor cousins?

We get it, you guys use Macs… but come on.

/rant

5 Likes

Same problem with

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

i try with –classic and works again but i have to wait to use the Glass version

Same here, on latest version, WSL + glass still goes into WSL extension install loop. Can’t use existing chats, or start new chats (just hangs at planning), even if I ignore the WSL extension prompt.

Version: 3.0.12 (system setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For those patiently watching this thread, It looks like as of one of the last 1-2 updates, WSL now seems to be functional for me, with the new Glass view. Only issues I’ve seen so far are with the “Changes” tab not rendering anything – stating “Failed to load changes”.

Version where things started working for me:

Version: 3.1.15 (system setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: glass
Build Type: Stable