Subagents in WSL

Support Bug Reports
,
1

I have subagents defined in user directory on my windows drive - works good when working with cursor on windows projects

When subagents launched I had to also define them in user directory in wsl

Now when I am in wsl and go to settings and click on a subagent, it tries to open it but says file not found, but it exists and agent can use it

image
image950×546 8.37 KB

skills can be opened just fine

would it be possible to have one unified .cursor directory for both wsl and windows environment?

4

Hey, thanks for the report. This is a known issue with path resolution for subagents in WSL. The Settings UI tries to open the file using a Windows path even though it’s in the WSL filesystem.

For now, the workaround is to open subagent files manually via the Cursor file explorer or from the WSL terminal:

cursor ~/.cursor/agents/code-explorer.md

About using a single .cursor directory, that’s an interesting request, but it’s technically tricky because Windows and WSL use different filesystems. For now, configs have to be duplicated.

Could you share your Cursor version (Help > About)? Also, what Windows and WSL versions are you on? That’ll help the team prioritize the fix.

5

Version: 2.4.28 (user setup)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045

WSL version: 2.6.1.0

1 Like
6

It is actually not enough to only create .md file in ~/.cursor/agents/. Cursor IDE can see the agents in Settings, but LLMs don’t. As if there is no subagent at all.

image
image1004×271 14.3 KB

You have to create the .md file in Windows filesystem C:\home\YOUR_USERNAME\.cursor\agents\path.

Only then the LLMs in Cursor can see your subagents.

1 Like
8

@Patrik.H Are you also using WSL, or have you found this to be true more generally?

9

@Colin Yes, I’m using WSL.

Version: 2.5.17 (user setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

WSL version: 2.4.13.0

11

Thanks! Was able to tie this to a known issue :pray: