Can't connect to WSL (Ubuntu) from Cursor version 1.x

Bug Reports
5

Thanks for your reply, I resolved it.

Problem:
Connecting to WSL from Cursor fails. It appears the built-in WSL setup process is broken.

Workaround:
I was able to resolve the issue by manually installing the WSL extension and the remote server.

Steps to Reproduce Workaround:

  1. Uninstall the WSL extension from Cursor.

  2. Manually install the WSL extension from VSIX file: ms-vscode-remote.remote-wsl-0.88.3-web.vsix.

  3. In a WSL terminal, run the following commands to remove the old server and install a specific version manually:

    cd ~
rm -rf ~/.cursor-server
curl -L "https://cursor.blob.core.windows.net/remote-releases/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/vscode-reh-linux-x64.tar.gz" -o "cursor-server.tar.gz"
COMMIT_ID="5b19bac7a947f54e4caa3eb7e4c5fbf832389850" && mkdir -p ~/.cursor-server/bin/$COMMIT_ID
tar -xzf ~/cursor-server.tar.gz -C ~/.cursor-server/bin/$COMMIT_ID/ --strip-components=1
ldd ~/.cursor-server/bin/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/node
~/.cursor-server/bin/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/bin/cursor-server --accept-server-license-terms

  4. After the script finishes, return to Cursor and connect to WSL using the “Distro” option.

Result:
The connection is now successful.