Unable to resolve resource

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Unable to open files from chat on Windows – “Unable to resolve resource” with percent-encoded path

Steps to Reproduce

After a recent Cursor update, clicking almost any file link in the chat/Agent panel fails to open the file and shows this error:

  • Primary message: Unable to open '<filename>.py' (or whatever file was clicked)
  • Detail: Unable to resolve resource c:%5Cdev%5Cai-fin-advisor%5Csrc%5Ccore%5Ctext_utils.py

Decoded, the path is: c:\dev\ai-fin-advisor\src\core\text_utils.py

The file exists on disk and opens normally from the Explorer sidebar or via Ctrl+P. The issue only happens when opening files from links in the chat window.

Expected Behavior

Environment

  • OS: Windows 10 (build 10.0.26200)
  • Workspace path: c:\dev\ai-fin-advisor
  • Repro: Open a chat, get a response that references a file (e.g. text_utils.py), click the file link → error dialog
    Path resolution for chat file links appears to use a percent-encoded URI (%5C for backslashes). The resolver then fails to match this to the actual workspace file on Windows, so “Unable to resolve resource” is shown even though the file exists.

Similar reports: File Linking Issues in Chat/Composer UI, Can’t Chat with Codebase on Windows (different path but same “Unable to resolve resource” on Windows).

Operating System

Windows 10/11

Version Information

Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. This is a known Windows-specific bug. File links in the chat panel use percent-encoded paths (for example, %5C for backslashes), and the resource resolver can’t match them to the real files on disk.

The team is aware of the issue.

As a temporary workaround, you can use Ctrl+P to quickly open any file mentioned in the chat by name.

Let me know if you run into anything else.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.