You destroyed Cursor, by breaking up Terminal!

[kinder_grinder]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug: SSH command output not captured in terminal tool

Steps to Reproduce:

1. Use run_terminal_cmd tool to SSH into remote server
2. Run any command via SSH: ssh root@IP "docker ps"
3. Command executes successfully (exit code 0)
4. Output is completely empty - nothing displays

What Works:

• Commands execute successfully on remote server
• Exit codes are correct
• First SSH command in session sometimes shows output (like docker ps worked once showing containers)

What Doesn’t Work:

• Subsequent SSH commands show NO output
• Tried WSL ssh, PowerShell ssh, writing to files, piping - all fail
• Only way to see output: user manually runs command and pastes it

Expected:

• SSH command output should be captured and displayed like regular terminal commands

Impact:

• Cannot debug or fix issues remotely
• User must manually run every command I suggest

Steps to Reproduce

Use run_terminal_cmd tool to SSH into remote server
Run any command via SSH: ssh root@IP “docker ps”
Command executes successfully (exit code 0)
Output is completely empty - nothing displays

Expected Behavior

SSH command output should be captured and displayed like regular terminal commands

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (user setup)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Sonnet 4.5

Additional Information

I am an Ultra subscriber, and I am seriously gonna leave Cursor forever, since you broke something that was working perfectly a month ago, and after dozens of threads that Terminal is broken, you are still not managing to fix it and bring it where it was before.

Honestly disgusting !

Does this stop you from using Cursor

Yes - Cursor is unusable

[kinder_grinder]

When I turn this OFF, it is able to read the output, but then Agents terminal are in read-only mode, and I can’t execute commands, run sudo, type passphrase, cancel processes.

I dont know what is worse.

Just put some man power fully dedicated to Terminal with all the resources you have. I can’t believe that its take so much reports, and time to make something work as it was working before.

[ravirahman]

Does your SSH require a password or other interactive input to connect? If so, it is probably hanging on that – the run terminal command doesn’t support interactivity.

If most of your development is on a remote system, I’d recommend using the Remote SSH plugin to connect, so you can use Cursor as if it’s running on the remote machine:

[kinder_grinder]

I am using both, but in this case, yes, it was a remote server.

My point is that this was working fine before you decided to update and ruin the terminal experience.