Cursor 3: Extension 'WSL' is required to open the remote window

Support Bug Reports
, ,
26

Same issue.

27

Really looking forward to try using Agents Window, WSL support needed.

28

Same issue

29

same

30

Thanks this helped alot

31
  1. There is no error displayed. Opening the editor to the affected remote workspace just hangs on the loading actions with Opening remote…. spinners and what not. No tab contents load including editor tabs, file manager, git, extensions, etc. As mentioned by another user here.
  2. Version: 3.0.16 (user setup)
    VSCode Version: 1.105.1
    Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
    Date: 2026-04-09T05:33:51.767Z
    Layout: editor
    Build Type: Stable
    Release Track: Default
    Electron: 39.8.1
    Chromium: 142.0.7444.265
    Node.js: 22.22.1
    V8: 14.2.231.22-electron.0
    OS: Windows_NT x64 10.0.26200
  3. Ubuntu 24.04.1 LTS

Tried deleting ~./.cursor-server with no affect.

Running cursor –classic prompted to uninstall ms-vscode-remote.remote-wsl. After clicking on Uninstall & Restart Cursor the editor successfully connected to wsl.

2026-04-09_16-33
2026-04-09_16-33350×141 6.2 KB

After closing the classic instance, I opened the standard editor and it connected to wsl successfully but prompted that there was an update to install.

2026-04-09_16-36
2026-04-09_16-36546×121 3.02 KB

I did not click update and instead clicked Close and clicked About→check for updates and no updates were found.

I closed cursor again . Restarted and again was able to connect to wsl as before. Seems all is well again.

EDIT: To clarify, my reported issue isn’t that Agents doesn’t work with wsl. It’s clear from this thread that wsl support hasn’t been implemented yet.

My issue is that after attempting to install wsl extension in Agents, Cursor 2 Editor wsl no longer functioned for the workspace. Same as another user reported above. This post was about how I got the editor working again.

33

Same issue.

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

34

+1, if this were fixed it would make the new agents page a really useful hub for light interaction across all workspaces, whether they’re in windows, wsl or on a server over ssh.

1 Like
35

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello,
I’m stuck in a WSL extension loop in Cursor.

Issue:

  • I click “Install and Reload” on the WSL popup
  • After reload, the same popup appears again
  • AnySphere WSL extension is already installed/enabled

Environment:

  • OS: Windows 11 (10.0.26200)
  • Cursor version: [paste from Help > About]
  • WSL distro: [paste from wsl -l -v]

What I already tried:

  • Reload window
  • Reinstall WSL extension
  • Restart Cursor

Please help me fix the extension/context mismatch or repeated install prompt.
Thanks.

Steps to Reproduce

  • I click “Install and Reload” on the WSL popup
  • After reload, the same popup appears again
  • AnySphere WSL extension is already installed/enabled

Expected Behavior

WSL correctly opening in the agents window introduced with Cursor 3

Operating System

Windows 10/11
Linux

Version Information

ProductVersion: 3.0.16
FileVersion: 3.0.16

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

36

Same issue here. Fixing this would allow my team to use Cursor 3.

1 Like
37

Same
I hope it’s a priority.

1 Like
38

Same issue. I will use Editor Window.

1 Like