Unable to access WSL paths in the new agent window

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have tried all nightly versions and official updates of Cursor 3 on Windows 11 using WSL and then I use the new agent window and try to start an agent with a WSL path (that works fine in the regular IDE window) I continually get a toast popup that says Exctension WSL is required to open the remite window, even though it is already installed and working in the regular IDE Window.

It then lets you install and reload and it looks liks something is happening and the window of the agent window refreshes / updates and then the same Extension WSL message is listed as if nothing has happened.

Current version details if that helps but I’ve tested on a few nighglites now and its isolated to the new agent window.

Steps to Reproduce

Open the agent window, open a repo in a WSL path and then I get the message to install and reload the WSL extension.
I click install and reload, the app reloads and then I still cannot access a WSL project path that works fine in the regular IDE window wher I use WSL all the time..

Expected Behavior

Able to access projects in WSL like I can in the regular IDE window

Operating System

Windows 10/11

Version Information

[Window Title]
Cursor

[Main Instruction]
Cursor

[Content]

Version: 3.1.0-pre.5.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 0196591c6cf647fc9ec356e97a3b0f01d74dc2d0
Date: 2026-04-05T01:55:32.858Z (7 hrs ago)
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

[Copy] [OK]

For AI issues: which model did you use?

Not relevant

Additional Information

I need to use WSL on my Windows machine to work on my teams codebase

actually after the window reloads I am now unable to use or even exit out of the agent window anylonger so i have to kil lthe task and start cursor again

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
5

This is a known limitation — the Agent Window (Glass) doesn’t support WSL connections yet. The extension install prompt loops because Glass doesn’t activate the WSL extension after installing it.

Workaround: Use the Editor Window for WSL projects. You can switch to it from the Agent Window via Open Editor Window, or launch Cursor in classic mode:

cursor --classic

In the Editor Window, WSL works as usual.

More discussion in this related thread: Cursor 3: Extension ‘WSL’ is required to open the remote window

The team is aware. No ETA yet, but every report helps with prioritization.

1 Like
6

thanks for resonding, i’ll keep an eye on the other page you referenced.

1 Like
7

I foolishly also clicked on install wsl extension in the agent window while a wsl connected workspace was open in the editor. Now the editor just hangs at Opening remote… and fails to load any tabs. Other workspaces in wsl continue to work fine.

Any idea how to resolve this or even where to look to determine cause? Thanks.

EDIT: Ha OK, I just opened the linked thread from above and dozens having the same issue. I’ll try the steps posted there. Thanks.

8

I have since installed the latest nightly and the WSL issue seems to be resolved