search

getcursor / cursor

The AI-powered code editor
https://cursor.sh
20.57k stars 1.38k forks source link

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

Open shaunhegarty opened 1 month ago

shaunhegarty commented 1 month 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 1 month ago

same, tried almost everything.

andrasat commented 1 month 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 1 month ago

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

andrasat commented 1 month ago

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

sbscan commented 1 month 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 3 weeks 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.