View Plan button opens invalid backslash path (\root.cursor\plans) in Remote-SSH (Windows client to Linux server, workspace root /root) – Cursor 2.3.7

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Plan Mode in a Remote-SSH workspace, generated plan files are correctly created on the remote Linux server in the workspace root:
/root/.cursor/plans/<plan_name>.plan.md
However, clicking the View Plan button attempts to open an invalid Windows-style path:
\root.cursor\plans<plan_name>
.plan.md
This results in an error: “The editor could not be opened because the file was not found.”
The issue appears to be a path separator mix-up (backslashes instead of forward slashes) combined with treating the workspace root /root as an absolute root path on the Windows client side.

Steps to Reproduce

Run Cursor on Windows and connect via Remote-SSH to a Linux server.
Open a workspace with root directory /root.
In Plan Mode, generate a new plan (e.g., prompt something that creates a plan).
Confirm the file exists on the remote: ls /root/.cursor/plans/ shows the .plan.md file.
Click the View Plan button in the chat.
Observe the “file not found” error and the invalid \root... path in the editor tab or error message.

Expected Behavior

View Plan should open the correct remote path /root/.cursor/plans/<plan_name>_.plan.md using forward slashes.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.7 (user setup)
VSCode Version: 1.105.1
Commit: 44f52350f2b7b9ee7625cfaade862ff53a016f40
Date: 2025-12-26T20:10:38.803Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

minimax-2.1

For AI issues: add Request ID with privacy disabled

c37f05eb-8ecd-4df7-8644-14b1fb76cc9a

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This is a known issue with Plan Mode when using Remote-SSH. Path handling between a Windows client and a Linux remote can break. The team is aware and working on fixes for Remote-SSH + Plan Mode issues.

Workaround: Open the plan file manually via File > Open File and navigate to /root/.cursor/plans/<plan_name>.plan.md on the remote.

1 Like

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