Agents Window uses 'Windows' .cursor settings, where it should use WSL:ubuntu-24.04

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi,
I am using Cursor ver 3.1.10 in Windows environment (unfortunately) however my workspace is saved inside WSL (Ubuntu 24), presicely in ~/cursor-wsl.code-workspace. Also my MCP settings are in my ~/cursor-workdir/.cursor folder that is the first folder in my workspace. Cursor sees it perfectly fine when I open MCP settins in Cursor editor. However, when I switch to Cusor’s ‘Agents Window’ I see that my MCP settings are read from Windows user home/.cursor/mcp.json , this is wrong. I would like to use ‘Agents Window’ also from within WSL. I tried to create a soft link inside WSL file system to point to ~/cursor-workdir/.cursor/mcp.json and have a link in windows user home dir/.cursor/mcp.json. But it didn’t work - when openinig MCP settings in Cursor file was not found, nothing happened, looks like this soft link mcp.json fle is not visible.

For me the ‘Agents Window’ is useless as I can’t use my MCP tools with it as these are defined in WSL , not in Windows.

Regards,

Steps to Reproduce

  1. Open cursor in windows
  2. connect to WSL, use WSL as your default profile
  3. save your workspace file inside WSL
  4. define some MCPs that are linux based and work in WSL well
  5. Open Agents Window
  6. There is no possibility to use WSL there, all MCP settings are gone because MCP settings are now read from Windows User’s home/.cursor/mcp.json file, not from the mcp.json file that sits inside WSL.
  7. In Agents Window , open ‘wsl+ubuntu+24.04’ as the target for the Agent to ‘Run on’. It can be any other WSL
  8. under prompt input window there is a big “+” sign to ‘add Skills, MCPs and more’, press it, select ‘MCP Servers’ → “Open MCP settings”
  9. Press ‘Add Custom MCP’
  10. By default , mcp.json file from within Windows will be opened (I got mine empty)
  11. Select from opnened tree view (WSL files should be showed) the mcp.json that is inside WSL, in my case it is ~/cursor-workdir/.cursor/mcp.json
  12. You will see a message: “ENOPRO: No file system provider found for resource 'vscode-remote://wsl%2Bubuntu-24.04/home/XYZUSER/cursor-workdir/.cursor/mcp.json”

Screenshots / Screen Recordings

curs_enopro.png
curs_enopro.png1281×683 48 KB

Operating System

Windows 10/11

Version Information

Cursor 3.1.10

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.6783

Ubuntu version:
Distributor ID: Ubuntu
Description: Ubuntu 24.04.3 LTS
Release: 24.04
Codename: noble

6.19.9-locietta-WSL2-xanmod1

PRETTY_NAME=“Ubuntu 24.04.3 LTS”
NAME=“Ubuntu”
VERSION_ID=“24.04”
VERSION=“24.04.3 LTS (Noble Numbat)”
VERSION_CODENAME=noble
ID=ubuntu

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hi @rumburakusai,

This is a known limitation. The Agents Window doesn’t support WSL connections yet, which is why it reads MCP settings from the Windows-side path instead of your WSL filesystem, and why you see the ENOPRO error when trying to navigate to your WSL mcp.json.

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

cursor --classic

In the Editor Window, WSL works as usual, including your MCP tools.

The team is actively working on adding WSL support to the Agents Window. You may also find this related thread helpful, with more context and updates from other users: Glass Interface doesn’t work with WSL

9

Hey @rumburakusai,
WSL support in the Agents Window has been addressed and the fix should be available on the nightly release channel. If you’d like to try it out before it hits stable: open Cursor Settings > About and switch the Release Track to Nightly, then restart Cursor. Let me know if that resolves it!

10

thanks, I will wait for regular release, when to expect it?

11

No problem! We don’t have a fixed schedule for when nightly changes roll into stable, but it typically happens within a couple of weeks. I’d recommend keeping an eye on the Cursor Changelog for updates.
If you change your mind in the meantime, the nightly track is there for you.