Failure to edit subagent definition files

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Cursor GUI fails to edit subagent definition files. The editor reports “The editor could not be opened because the file was not found.” even though the file actually exists.

Details:

The Cursor GUI is running on Windows. The Cursor server is running on Linux (WSL). Thus, the files are created on the Linux side. When I click on the subagent definition item in Cursor Settings>Subagents, it spawns an editor with Windows-style path separators: “\home\user\work\repository.cursor\agents” and says it can’t find the file.

Steps to Reproduce

  1. Launch Cursor on Windows
  2. Connect to WSL
  3. Open a repository
  4. Open Cursor Settings>Rules, Skills, Subagents
  5. Under the Subagents section, click “+ New”
  6. Tell the agent to create a placeholder agent, that you’ll fill in the definition later. The agent will create the definition file, and the Cursor GUI will see the new definition
  7. Click the new subagent definition entry that just appeared in the GUI
  8. An editor will spawn in an error state

Expected Behavior

The editor should open the proper agent definition file.

Operating System

Windows 10/11

Version Information

Version: 2.6.19 (system setup)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

This also affects deletion. When you click the trashcan icon, the Cursor GUI complains, "Failed to delete subagent: Unable to delete nonexistent file “\home\user\work\repository.cursor\agents\blah.md”

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey Sean! Thanks for reporting. This is the same issue that was reported here:

And I’ve added your report to our internal tracking issue.

1 Like

Yes, it’s the same issue as was reported about a month ago. That issue was closed without a resolution, though.

Ticket is still open on our side, and we’ll update relevant threads (like this one, and the other) when there’s news to share!