Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
File linking functionality in Cursor AI’s chat and composer UI frequently fails to correctly resolve file paths, resulting in “The editor could not be opened because the file was not found” errors when clicking on file links.
This occurs:
When trying to preview files before applying changes
When attempting to view diffs
When using the new “page changer” feature
Particularly problematic in SSH sessions
Most severe when using Windows with WSL or SSH into Linux environments
The code generation and application works correctly, but the inability to preview or verify changes through the UI significantly impacts workflow efficiency.
Steps to Reproduce
Open Cursor AI chat or composer
Have AI suggest changes to existing files
Click on any file link in the chat/composer UI to preview changes
Observe “file not found” error
Additional test case:
SSH into remote environment (especially Windows → Linux)
Repeat steps 1-5
Observe more frequent linking failures
Expected Behavior
Clicking file links should open the correct file at the right location
“Skip to affected pages” feature should correctly navigate to modified files
File preview should work consistently across:
Local environments
SSH sessions
Cross-platform SSH connections
Diff preview should be accessible before applying changes
Multiple file changes should be easily previewable through UI links
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.10
VSCode Version: 1.93.1
Commit: ae296fde8115b123d8ce516cdfedf697fc577660
Date: 2025-01-02T09:19:53.599Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Additional Information
Current Impact:
Forces manual file location and navigation
Significantly slows down review process for multi-file changes
Requires maintaining separate file explorer window
Extra cognitive load tracking multiple file changes
Some users have implemented workaround prompts for local directory structure
Known Workarounds:
Manually navigating to affected files
Using custom prompts to improve directory understanding
Keeping separate file explorer open
Noting file paths manually before reviewing changes
Technical Notes:
Issue seems related to path resolution
More prevalent in SSH contexts
Cross-platform path separators may be involved
Directory structure understanding varies between local and SSH contexts
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor