Cursor Remote SSH session fails when opening large files

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When a large file (~300 MB was enough to cause this for me) is opened, I get a warning that the file has not been loaded due to the file being large. Even if I don’t click “open anyway”, my ssh connection becomes unusably slow, I can’t open new terminals or files, the only solution is killing the remote server and reloading.

Steps to Reproduce

In a Remote SSH session, click on a large file (~300 MB) in the file explorer. This has caused issues consistently

Expected Behavior

Opening the file should not cause my entire remote ssh session to die if I don’t select “open anyway”

Operating System

Linux

Version Information

Version: 2.3.41 (Universal)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z (2 wks ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Hey, thanks for the report.

It looks like this is related to how large files are handled in a Remote SSH session. Even without clicking “Open Anyway”, some kind of preloading seems to happen, and it ends up freezing the connection.

A couple of questions to help us debug:

  • What’s the exact file size, is it around 300 MB or more or less?
  • How much RAM does the remote server have?
  • Does this happen with all large files, or only a specific type like JSON, log, CSV?

For now, a workaround is to avoid clicking on files in the file explorer if you know they’re large.

I’ll pass this to the team. It’s on our radar, and any extra details will help us prioritize it.