Command 'remote-wsl.connect' not found

Bug Report
1

image
Have been using WSL fine on cursor for a few months. Came back to the machine today and all of the WSL environments were failing, possibly an update?

The WSl extension is still showing up as being installed+enabled within the WSL environment and the main windows environment.

VSCode still works just fine with WSL, I can access the wsl shell from both cursor and vscode as well.

Things I have tried:
Restarting
Updating cursor to most recent version
Re-installing the wsl extension
Running the ‘fix WSL’ command (seems to have no effect)

The extension files for ms-vscode-remote do exist on 0.81.8, and the entry for it exists in the .cursor/extensions/extensions.json

This happened to me once before and I couldnt resolve so I just didnt use cursor for a few months, Eventually fixed by uninstalling fully including manually deleting hidden cursor cache files then reinstalling a more recent version. (i tried this originally but didnt work until waiting a few months, so possibly update related)

Please let me know if you need more information.

1 Like
2

I got it to work by running cursor from WSL by running the command /mnt/c/Users/<windows username here>/AppData/Local/Programs/cursor/resources/app/bin/cursor /path/to/workspace/directory. This triggered the WSL server install, but on first load it complained that the WSL filesystem backend wasn’t present. I then hit ctrl-shift-p and ran the Extensions: Install Extensions command and saw that some extensions were requiring a window reload. Once I did that it seemed to be working.

Note that you may also need to add /mnt/c/Users/<windows username here>/AppData/Local/Programs/cursor/resources/app/bin to your PATH in WSL via the profile or rc script for your shell of choice if you want to just be able to run cursor . from within WSL.

1 Like