- There is no error displayed. Opening the editor to the affected remote workspace just hangs on the loading actions with
Opening remote….spinners and what not. No tab contents load including editor tabs, file manager, git, extensions, etc. As mentioned by another user here. - Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
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.26200 - Ubuntu 24.04.1 LTS
Tried deleting ~./.cursor-server with no affect.
Running cursor –classic prompted to uninstall ms-vscode-remote.remote-wsl. After clicking on Uninstall & Restart Cursor the editor successfully connected to wsl.
After closing the classic instance, I opened the standard editor and it connected to wsl successfully but prompted that there was an update to install.
I did not click update and instead clicked Close and clicked About→check for updates and no updates were found.
I closed cursor again . Restarted and again was able to connect to wsl as before. Seems all is well again.
EDIT: To clarify, my reported issue isn’t that Agents doesn’t work with wsl. It’s clear from this thread that wsl support hasn’t been implemented yet.
My issue is that after attempting to install wsl extension in Agents, Cursor 2 Editor wsl no longer functioned for the workspace. Same as another user reported above. This post was about how I got the editor working again.

