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

Where does the bug appear (feature/product)?

  • Cursor IDE

  • Cursor CLI

  • Background Agent (GitHub, Slack, Web, Linear)

  • BugBot

  • Somewhere else…


Describe the Bug
Agent Window repeatedly complaining about missing WSL extension, install and reload button doesn’t seem to help. The WSL extension from Anysphere is installed in the editor extensions, but perhaps that’s not what it’s referring to? The editor window is able to read and manipulate the WSL project just fine.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. Opened a WSL repo in Cursor 3

  2. Opened the new Agent Window

  3. Changed the Select Project dropdown from Home to “wsl+ubuntu” and selected a project

  4. Get a pop-up in the bottom right saying “Extension ‘WSL’ is required to open the remote window. Do you want to install the extension?” with an “Install and Reload” button

  5. Clicked the button

  6. It reloaded the agent window, but continues to show the same pop-up in the corner

  7. Chat does not work (cannot reference files, agent times out with “The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.”)


Expected Behavior
It should either work or install whatever it’s missing and then work.


Screenshots / Screen Recordings


Operating System

  • Windows 10/11

  • MacOS

  • Linux


Version Information

  • For Cursor IDE: Menu → About Cursor → Copy

  • For Cursor CLI: Run agent about in your terminal

IDE:
Version: 3.0.4 (user setup)
VSCode Version: 1.105.1
Commit: 63715ffc1807793ce209e935e5c3ab9b79fddc80
Date: 2026-04-02T09:36:23.265Z
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.22631

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable

  • Sometimes - I can sometimes use Cursor

  • No - Cursor works, but with this issue

18 Likes

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

yeah it shows me popup to install wsl in the new agents window, i click install (multiple times), restart, try again, nothing happens, works good in editor window

2 Likes

is there a way to go back to the old view so we can continue working with the wsl while this bug is fixed?

Same issue. Would love to try new agents mode , but for now will work in editor mode until issue is resolved

1 Like

Upvoting, having the same issue.

Version: 3.0.9 (user setup)
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
Layout: editor
Build Type: Stable
Release Track: Nightly
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

Hey, this is a known limitation. Agent Window (Glass) doesn’t support WSL connections yet. The extension installs, but Glass doesn’t activate it, so you get a looped prompt.

Workaround: use Editor Window for WSL projects. You can open it from Agent Window via Open Editor Window, or start Cursor in classic mode:

cursor --classic

In Editor Window, WSL works as usual.

This same bug is being discussed here: Glass Interface doesn't work with WSL

The team is aware. No timelines yet, but reporting it helps with prioritization. Let me know if you have any other questions.

4 Likes

Same issue.
Version: 3.0.9 (system setup)
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
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

@deanrie Even with classic I cant still connect wsl to cursor. I have tried to uninstall and reinstall, delete cursor-server, restarted pc but still didnt work.

1 Like

The same issue

Same issue.

Same issue.

Same issue.

Same issue

Same issue.

same issue

Hey @Abdussamad_Bello If --classic also doesn’t work, it’s most likely a separate issue from Glass or the Agent Window.

Can you clarify:

  1. What error do you see in the Editor Window or classic mode? A screenshot or the exact error text would help.
  2. Your Cursor version: Help > About Cursor > Copy
  3. Which WSL distro are you using?

Also try:

  • Delete the ~/.cursor-server folder inside WSL. You mentioned you tried, but just in case: run rm -rf ~/.cursor-server in the WSL terminal
  • Open Cursor without extensions: cursor --classic --disable-extensions, then connect to WSL

Let me know what you get and we’ll dig in.

Same issue – Screenshot from opening a workspace file on WSL 2:

When running cursor –classicon the same code-workspace file (with or without disable-extensions:

image
The remote never opens. I have removed the cursor-server folder and the same issues persist.

Version: 3.1.0-pre.11.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: d4716cbb846c02f4e90fc58203398326a956ee70
Date: 2026-04-06T05:59:57.723Z
Layout: glass
Build Type: Stable
Release Track: Nightly
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.22631

$ wsl --version
WSL version: 2.6.3.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.71
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.6199
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:        24.04
Codename:       noble

Edit:
My issue specifically was tied to opening a code-workspace file and having Cursor assume an incorrect WSL distribution – opening a single folder in classic mode works and selects the correct distribution

Bump

That will be such a well-welcomed feature since codex doesn’t work with WSL. I wanted to give a try to agent window today but was disappointed that I cannot connect to WSL.