Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I have a workspace (so a file like “xxx.code-workspace”) with four folders, like:
"folders": [{ path": "t1" }, { "path": "t2" }, { "path": "t3" }, { "path": "t4" }
In chat, when the agent emits a code reference to a file in the second folder or subsequent folder. The link is not clickable. A similar reference to a file in the first folder works fine - if I click on it, the file opens in the Editor window.
Talking to the agent about it, it says it emits code references like
and it thinks when I click on it, Cursor will try to find t1/t2/include/foo.h.
The agent then generated an absolute path reference, and said, “try clicking that” and it did in fact work. So the agent and I think that file references in the chat need to be absolute paths. (Or I guess the appropriate ../../ would be ok too)
Steps to Reproduce
Open a multi-root workspace with 2+ folders. In chat, get the agent to emit a code reference to a file in the second folder using a relative path. The link is not clickable. Same reference to a file in the first folder works fine.
Expected Behavior
In a multifolder workspace, cursor chat file references should be clickable no matter which folder they are in. By clickable, I mean when I click on the reference, the file appears in the editor window.
Operating System
Windows 10/11
Version Information
Version: 2.4.31 (user setup)
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
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.26100
For AI issues: which model did you use?
My issue is independent of model, I checked.
Additional Information
I’m using the Remote SSH extension, so the workspace and folders are all on a linux system.
Does this stop you from using Cursor
No - Cursor works, but with this issue