Hey, thanks for the detailed report. This is a known type of issue. Agent terminal commands can hang on remote setups, especially with chained connections like SSH + a K8s container.
A few things to try:
-
Enable Legacy Terminal Tool: Cursor Settings
Ctrl+Shift+J> Agents > Inline Editing & Terminal > turn on Legacy Terminal Tool. Then runCtrl+Shift+P> Terminal: Kill All Terminals and fully restart Cursor. -
Check shell availability in the container: In a similar setup, we’ve seen the agent fail with spawn zsh ENOENT because the container only has bash. Open Developer Tools Help > Toggle Developer Tools > Console while the command hangs and check for errors like that. If you see zsh ENOENT, set the terminal profile explicitly: Settings > search terminal.integrated.defaultProfile.linux > set to bash in the Remote scope.
-
Check DevTools for errors: When the agent hangs on Waiting for output, open Help > Toggle Developer Tools > Console and share any red errors here. That’ll help narrow down the root cause.
The team is aware of this type of SSH and remote terminal hanging issue. Your report with the K8s container setup helps with prioritization since the double hop SSH + container is a less common path.
Related threads with similar symptoms:
- Cursor forever wait for command on remote ubuntu
- Remote SSH agent terminal broken on Ubuntu 22.04 GCP host: PTY not found / remoteTerminalBackend already registered
Let me know how it goes with the Legacy Terminal Tool, and share the DevTools output if it still happens.