When using Cursor to connect to a server for development via SSH, if you upload a document in the Windows terminal where Cursor is installed for Cursor to analyze, Cursor will not be able to recognize it. You must upload the document to the corresponding SSH server before Cursor can properly recognize it. This is inconvenient and inefficient
Steps to Reproduce
When using Cursor to connect to a server for development via SSH, if you upload a document in the Windows terminal where Cursor is installed for Cursor to analyze, Cursor will not be able to recognize it. You must upload the document to the corresponding SSH server before Cursor can properly recognize it.
Hey, thanks for the report. I can see in the screenshot you attached the 1.html pill with a local path c:\Users\what\Desktop\htmltest\1.html, while your workspace is open on a remote Linux host.
This is expected when using Remote SSH. The agent runs on the remote server and can only read files that actually exist there. When you attach a local Windows file, it gets sent as a link to a local path, which the remote agent can’t resolve.
One important detail: some document types (pdf, md, txt, csv, json, xml, yaml/yml, toml, ini, log) and images are uploaded by content and work fine over SSH. But .html isn’t in that list, so it gets sent as a path the server can’t access.
Workarounds:
Copy the file into the remote workspace (scp/sftp) and attach it from there.
Or paste the file contents directly into the chat.
Or save it as a supported text type like .txt before attaching.
Direct access to local files inside an SSH session is a known limitation we’re tracking. I can’t share an ETA yet, but I’ve passed your report to the team as another signal. Let me know if none of the workarounds work for you.
