Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When using Cursor with Remote-SSH, generating large AI outputs (e.g. multi-step plans, in “Plan” mode) becomes extremely slow. The Cursor status bar shows very low SSH throughput (~1–2 kB/s) during generation. The same operation performed locally (no Remote-SSH) is fast and streams normally.
This occurs even with the latest Cursor-supported Remote-SSH extension and does not appear to be related to EC2 performance, repo size, or indexing.
Steps to Reproduce
1. Open a repository locally in Cursor (no Remote-SSH).
2. Ask Cursor to generate a large plan (e.g. multi-step refactor, test suite, architecture plan).
3. Observe:
• Fast, smooth streaming.
4. Now open the same repository via Cursor Remote-SSH.
5. Ask Cursor to generate the same plan.
6. Observe:
• Output is extremely slow or stalls.
• Cursor status bar shows SSH throughput around:
SSH: ~1–2 kB/s ↑ / ↓
Expected Behavior
• Plan generation speed over Remote-SSH should be comparable to local Cursor usage, or at least not degrade to kB/s throughput.
• Large AI outputs should stream smoothly regardless of Remote-SSH.
Screenshots / Screen Recordings
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
• Cursor version: 2.3.15
• OS: macOS (Apple Silicon)
• Remote host: AWS EC2 (Linux)
• Remote-SSH extension:
• Identifier: anysphere.remote-ssh
• Version: 1.0.36
• Last updated: 2026-01-01
• Network: Stable broadband (local Cursor usage is fast)
Additional Information
• This is not:
• EC2 CPU / RAM / disk related
• Repo size related
• Cursor indexing related
• The issue appears to be a Cursor Remote-SSH transport limitation for high-volume AI streaming.
• Current workaround:
• Generate plans locally in Cursor
• Commit them as .md
• Pull on remote
• Use Remote-SSH only for implementation
Impact
This significantly affects workflows that rely on:
• architecture planning
• test generation
• large refactors
• design docs
It forces users into a split local/remote workflow even when they want to stay fully remote.
Does this stop you from using Cursor
No - Cursor works, but with this issue
