I am using Cursor 2.3.41. I use remote SSH extension to connect to my remote host. I was able to talk to Agent and ask him to run various shell commands but at some moment it got stuck , looks like request is pending and is not finishing. How to reset it? I tried many different things like Cursor restart, removal stopping all cursor processes on remote host, removing .cursor-server and .cursor folders on a remote host. Nothing worked.
When I create new workspace and start new ssh connection to the same host, the agent can run terminal commands. I donât want to lose my chat history that is I would like to keep using my current workspace. Besides, I donât want to recreate new workspace every day due to this issue. How to resolve?
I am using 3 folders included/imported into my workspace.
Steps to Reproduce
Use Remote SSH extension to connect to remote host
Work with Agent , ask him to run different commands , give him different tasks related with the files located on remote host
At some point in time it will got stuck, it may take a 1 day or longer. Not sure how to reproduce it.
Expected Behavior
Agent is able to be restarted and we can resent the connection to make agent been able to run cli commands on a remote host again.
I noticed this happens when one of the commands fails. I switched to legacy terminal, I started a new workspace and I run couple of prompts , then I got this:
âAuto-Ran command: tail| grepâ
then next one:
âCancelled command: tailâ
but I am pretty sure I havenât pressed cancel myself.
Still investigating but is it possible this may have something to do with grep and the fact it returns exit code 1 on a mismatch? With exit code 1 all goes âka-boomâ ?
If that doesnât help, or if it happens again, weâll need a few details:
The Request ID from the stuck command (top-right of the chat > Copy Request ID)
The exact command that got stuck
Logs from Help > Toggle Developer Tools > Console (a screenshot of any errors helps)
Your note about seeing âAuto-Ran command: tail| grepâ and then âCancelled command: tailâ is really helpful. It looks like a bug in how failed commands are handled. Let me know if Legacy Terminal fixes it or if it keeps happening.
Right now my Cursor got a downgrade (via automatic updates) to a lower version: 2.4.21. Hence the environment I have now is different. I am reverting back to Legacy mode, I will observer and let you know. Please keep investigating on the issue as the Agent using and running commands in terminal seems not reliable at all and it is affecting not only my productivity but all users who uses the Cursor app and pay quite big money for it every month. Hence the expectation is to have this fixed.. And I fully udnerstand the frustration of other people, because when this happens and Cursor hungs on the command in the chat.. then this just stopped working and we are not having the functionality we paid for any more.
I see you tried Legacy Terminal after my last reply, but you didnât say if it helped or not. Can you confirm:
Is the Legacy Terminal Tool still enabled? (Cursor Settings > Agents > Legacy Terminal Tool)
Did the issue happen again after switching?
If yes, Iâll need details from the last time it froze:
Request ID (top right of the chat > Copy Request ID)
A screenshot of the Console with errors (Help > Toggle Developer Tools > Console)
The exact command it got stuck on
Your theory about grep returning exit code 1 is interesting, it really could be a trigger. The command is logged, but without the details above itâs hard to dig further.
On release notes:
There arenât any official public release notes. There is a changelog at Changelog ¡ Cursor
Let me know how it goes with Legacy Terminal, thatâll help narrow this down.
Glad Legacy Terminal helped. Thatâs exactly what we needed.
About switching back, I donât know if the bug in the new terminal has been fixed yet. If Legacy Terminal is stable for you, Iâd recommend staying on it for now. You can test the new terminal, but if it starts freezing again, switch back to Legacy right away.
If you try the new terminal and see the freezing again, please share:
Request ID (top-right of the chat > Copy Request ID)
Console logs (Help > Toggle Developer Tools > Console), screenshot with any errors
Thanks , I will stay with Legacy Terminal for a few weeks until the situation gets more stable. Where can we see the differences between Legacy and New? What are the advantages of using New Terminal?
About switching to the new terminal, I canât confirm the bug is fully fixed. Since the Legacy Terminal is stable, itâs better to stick with it for now.
If you want to test the new terminal, you can try it, but switch back to Legacy at the first signs of freezing.
The new terminal was supposed to improve command output handling and agent integration, but based on forum reports, it still has stability issues, especially over remote SSH.
