[Bug] Windows backslash paths in chat/agent links fail to open (Unable to resolve resource)

[Takeshi_Honda (Take)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Environment

• Cursor 3.7.42 (5702c9cfca656d8710fad58402fe37f14345e3a0, x64)
• Windows 10.0.26200
• Workspace: D:\00.PG
  Summary
  When Agent or chat shows Windows absolute paths with backslashes (e.g. D:\00.PG\RentServer\docs\patent\01_invention_disclosure_for_attorney.ja.md), clicking the link does not open the file. The path seems misparsed as a URI scheme (D:) with encoded backslashes (%5C), e.g. “Unable to resolve resource d:%5C00.PG%5C…”.

Steps to Reproduce

1. Open workspace D:\00.PG on Windows.
2. Agent references a file with a D:... backslash path in chat.
3. Click the link.
4. File does not open in editor.
   Expected: Clicking the link opens the file (like Explorer or Ctrl+P).
   Actual: Link fails; user must use Ctrl+P or open manually.
   Workarounds

• Workspace-relative paths (RentServer/docs/…)
• Forward slashes (D:/00.PG/…)
• Ctrl+P
  Related threads
• Unable to resolve resource
• Unable to open file linked in chat

Operating System

Windows 10/11

Version Information

Version: 3.7.42 (user setup)
VS Code Extension API: 1.105.1
Commit: 5702c9cfca656d8710fad58402fe37f14345e3a0
Date: 2026-06-15T19:39:42.738Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

ALL models

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Tom_Coustols]

hey @Takeshi_Honda, unfortunately, this is a known issue in windows being actively checked.. you can see the main thread in there :

Unable to open file linked in chat

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug The agent produced a chat response with a link to a file it had just created. I clicked on the link and got the error title=“Unable to open ‘’” message="Unable to resolve resource “”. Steps to Reproduce Have agent create a local file and provide a link to that file in the chat (I didn’t prompt it to do that, it just did). Click on link to view file. Error. Expected Behavior No error, file opens to be viewed. Screensh…

Since the issue is from more than a month, I have ping the team about it

[mohitjain (Mohit)]

Hey @Takeshi_Honda, thanks for the clear write-up - and @Tom_Coustols is right, this is a known one we’re already tracking.

On Windows, drive-letter paths like D:\... in chat/agent links get misread, which is exactly why clicking them throws “Unable to resolve resource”. The workarounds you already found are the right ones:

• Forward slashes: D:/00.PG/...
• Workspace-relative paths: RentServer/docs/...
• Ctrl+P to open the file directly

I’ve added your report to what we’re tracking so it counts toward prioritization. I’ll post back here once there’s an update.