search

getcursor / cursor

The AI Code Editor
https://cursor.com
25.36k stars 1.58k forks source link

Can no longer connect to WSL workspaces via Cursor (vanilla VS Code works fine) #1457

Open shaunhegarty opened 6 months ago

shaunhegarty commented 6 months ago

1) If you can, please include a screenshot of your problem I can no longer connect to WSL via Cursor. image VS Code can connect just fine. image

2) Please include the name of your operating system Windows 10 + WSL2 3) If you can, steps to reproduce are super helpful N/A

I've been loading up projects in VS Code and the Cursor without issue until a couple of days ago. Things I've tried:

Other info: Cursor versions image image

VS Code versions image image

sbscan commented 6 months ago

same, tried almost everything.

andrasat commented 5 months ago

Same here, also tried uninstall/install the extension back and running Shell Command: Fix WSL Install but still won't work. I hope this screenshot can help someone to find the issue. I'm using Ubuntu for the WSL2

Screenshot 2024-05-30 161835

sbscan commented 5 months ago

Today I tried, now works. Perhaps they've changed the files which remotely install.

andrasat commented 5 months ago

Today it also worked for me, but I have to uninstall and delete every cursor related folder inside Users/{user}/AppData

sbscan commented 5 months ago

Today it also worked for me, but I have to uninstall and delete every cursor related folder inside Users/{user}/AppData

I didn't do anything, just worked. My two windows desktop, one windows laptop and one mac book. Perhaps the remote downloaded files changed.

shaunhegarty commented 5 months ago

I've updated to the latest version (0.35.0 at the time of writing.) No change

I've tried deleting Cursor folders from %Appdata%. No change

Repeated above but with a fresh install No change

Repeated above but also remove ~/.cursor-server folders inside WSL No change

Repeated above but with a fresh install and without copying settings+extensions from VS Code Strangely, no change. The extensions from before were still installed, even though I had elected to start from scratch.

Repeated all above after deleting this folder: Users/{user}/.cursor Success! This time it was I was able to install the WSL and remote development extensions, and then I successfully connected to WSL again.

What now? I'm going to leave this issue open in the hopes that this problematic user experience will at least be acknowledged before it is closed. Thankfully I was able to get refunded my subscription while the application remained unusable.

pluma4345 commented 1 month ago

When I tried to open a WSL workspace in Cursor, the log showed a message saying that the WSL extension is only supported in Microsoft versions of VSCode. However I remembered that when I had previously closed VSCode it had downloaded an update, which usually means the WSL headless VSCode server also needs to update on the next launch.

After starting VSCode and waiting for it to launch in WSL, I was able to open the WSL workspace in Cursor again. Even after closing VSCode, I was able to work in Cursor as usual and exist and reopen Cursor without encountering the problem again.

So the trick might be to have VSCode update and launch the WSL server and then let Cursor take over from there. I'm not sure if this might be MS intentionally interfering with Cursor (and other forks).