File path degrades in WSL to Windows Format for some reason when running a task that involves launching parallel agents

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

File path degrades for some reason when running a task that involves launching parallel agents

Steps to Reproduce

I’m having it launch a task that runs 5 parallel agents in the background and this occurs

Operating System

Windows 10/11

Version Information

Version: 3.11.6 (user setup)
VS Code Extension API: 1.125.0
Commit: 499321504bbc2649b3148883f7b30fff8426c870
Date: 2026-07-08T21:40:28.046Z
Layout: IDE
Build Type: Stable
Release Track: Nightly
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

image

image
image1135×109 9 KB

image
image1198×283 31.6 KB

image
image1339×355 18.9 KB

This really only happens in this setup. I’m not really sure what’s causing it, but it seems like the model gets a bad workspace path at some point (perhaps when switching from launching the subagent to coming back), and then all future shell commands are degraded. If I stop it, and then send a new message, it tends to get it’s workspace path back correctly.

This is connected to a WSL folder for reference.

6

Hi @cxmplex!

Thanks for the report. If this happens again, can you grab a Request ID and share it here? It will let us dig into what’s going on.