Cursor on WSL2 keeps randomly opening a new non-remote window in cwd

Bug Reports
1

Since switching out the original WSL extension with the new in-house cursor WSL extension a couple days ago, I’ve had a few problems, such as noticeably higher memory usage at times and the inability to automatically open cursor in WSL if it is launched from a WSL terminal. But the worst problem is that when using a WSL/remote cursor window sometimes a new window will automatically open in the same WSL directory I’m currently using but in a native Windows (non-WSL) instance.

This just started happening after switching out the original WSL extension for the cursor one. I can’t find any log to indicate what is going on but maybe I am looking in the wrong places. One of the triggers for the window to open is when a model in the chat generates a terminal command, but it seems to happen at other random times as well.

I am now unable to revert back because installing the Microsoft extension just causes the cursor one to install. Please at the very least make the old one installable again?

3

I was able to figure out a way to uninstall the cursor WSL extension and install the old ms-vscode-remote WSL extension (which fixed the issue). Hoping these issues can be fixed so I can switch back over to the in-house versions.

5

Hi @mmstroik, thanks for raising these issues. We are working on a fix for the launcher when using the anysphere extension. As a workaround, if you install the vscode one (but keep it disabled) and install and enable the anysphere extension, then the launcher should work. I will let you know when the update is out, so you wont need to have the vscode remote wsl extension installed anymore.

1 Like
6

Thanks!