When SSHed into remote debian box, suddenly terminal commands not working

[gavinc]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When asking for the model to perfom actions involving terminal, running on windows but sshed into a debian box, the terminal is not executing at all. Just hangs there. This is NEW behaviour.

Testing locally, windows is able to have terminal actions.

Testing directly on the linux server with a local cursor install and running back to the windows box via xserver - works.

just going via ssh into the same box is no longer working (had been fine since january).

Steps to Reproduce

connect to ssh host per usual, try anythign that makes terminal actions happen

Expected Behavior

terminal actions happen as normal

Operating System

Windows 10/11
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.14 (user setup)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:41:40.820Z
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?

Auto and Grok

Does this stop you from using Cursor

Yes - Cursor is unusable

[ravirahman]

Hi @gavinc, does the terminal work in Cursor over SSH if you execute the command manually (outside of the agent)?

[gavinc]

Yeah it does

also, the failed request that just hung:
Request ID: bb098e0b-f81d-4f6a-b270-baf3d36087fb
{“error”:“ERROR_USER_ABORTED_REQUEST”,“details”:{“title”:“User aborted request.”,“detail”:“Tool call ended before result was received”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
ConnectError: [aborted] Error
at xyl.$endAiConnectTransportReportError (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4910:338991)
at Qvr._doInvokeHandler (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:487:36019)
at Qvr._invokeHandler (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:487:35761)
at Qvr._receiveRequest (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:487:34526)
at Qvr._receiveOneMessage (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:487:33348)
at BCt.value (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:487:31442)
at ye._deliver (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at ye.fire (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at Wot.fire (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4895:12154)
at MessagePort. (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7028:18292)

[gavinc]

And now it’s working again