I have a workspace in windows wsl. It works well when open the workspace with anysphere wsl externsion. After upgrade to Cursor3, it seems the wsl extension is not loaded correctly. It always prompts install wsl and reload, but after click the button, it reload the window, the wsl extension is still not loaded. It blocked the editor loading. I have to open the editor window first to load the workspace. The agent view does not work.
Steps to Reproduce
I have a workspace in windows wsl. It works well when open the workspace with anysphere wsl externsion. After upgrade to Cursor3, it seems the wsl extension is not loaded correctly. It always prompts install wsl and reload, but after click the button, it reload the window, the wsl extension is still not loaded. It blocked the editor loading. I have to open the editor window first to load the workspace. The agent view does not work.
Hey, this is a known limitation. Agent Window Glass doesn’t support WSL connections yet. The extension installs, but Glass doesn’t activate it, so you end up in an infinite prompt loop.
Workaround: use Editor Window for WSL projects. You can open it from Agent Window via Open Editor Window, or start Cursor in classic mode:
The new agents window promises to be a really nice “hub” for light interaction with a bunch of different workspaces from one place, whether they’re on my local machine, a server that I ssh into or wherever.
But without WSL working, it’s sadly not usable for this kind of workflow for myself and my team in it’s current state yet.
Hey @sy_hu,
WSL support in the Agents Window has been addressed and the fix should be available on the nightly release channel. If you’d like to try it out before it hits stable: open Cursor Settings > About and switch the Release Track to Nightly, then restart Cursor. Let me know if that resolves it!
Hey @nerdimite, thanks for testing on nightly and flagging this. I can see the screenshot. The Local tab is open, the header says No Local Changes, and the center says Failed to load changes. It looks like the SCM and diff panel still doesn’t fully work with a WSL host after we enabled WSL support in Glass.
So I can pass this to the team with the right context, can you send:
The exact nightly version Cursor Settings > About and copy the full line that includes the commit.
Logs from DevTools: Help > Toggle Developer Tools > Console then reload the window with the WSL project open and paste any errors that show up while Local Changes is loading. Lines mentioning Diff, git, or spawn are the most useful.
Check this too: if you open the same project in an Editor Window classic does the Source Control diff show normally? This helps us separate the WSL transport issue from the SCM layer in Glass.
I’ll log this as a separate issue since the main WSL ticket we fixed for connecting is already closed. I can’t promise an ETA, but a report with logs will speed up debugging a lot.
Hey, thanks for the update and the screenshot. I can see that in Glass on the WSL host, the panel shows “No uncommitted changes on your local branch” with a “View Changes to main” button, but you actually have uncommitted changes in the workspace. Branch vs main works, but local doesn’t. Got it.
For DevTools for the Agents Window, do this:
Focus the Agents Window, just click into it.
Open the Command Palette with Ctrl+Shift+P.
Find and run Developer: Toggle Developer Tools.
Then:
Go to the Console tab and clear it
Reload the window via Command Palette → Developer: Reload Window
Open the WSL project and go to the Local Changes tab, wait until you see “Failed to load” or “No uncommitted changes”
Copy any Console errors, especially lines that include Diff, git, spawn, wsl, ENOENT
A couple quick questions to narrow this down:
In the WSL workspace at the time of the screenshot, did you really have uncommitted changes, like git status in the WSL terminal shows modified or untracked files?
If you open the same project in the Editor Window classic via cursor --classic or from the Agents Window, does the Source Control panel show local changes correctly there?
This will help us tell if this is a WSL transport issue for SCM in Glass, or something else, like Glass not refreshing the git state cache.
