The Agent terminal doesnt output any of the server-side stuff, nor the agent can effectively read any of the outputs coming from its commands. In chat, it’s possible to see the server output preview after the agent commands, but not in the terminal, when opening it from the chat preview.
The terminal doesnt hold e.g. ssh sessions even after successful login.
Also, make the cursor terminal interactive again, like it used be, it’s pretty useless like this (no possibility of inputting own commands).
Also I wonder if Cursor is ever tested in Windows…
This bug has been persisting since v.2.0
As others have said, Cursor isnt going in the right direction and alternatives are surfacing every day now… Please stop pushing new features, and start fixing all the bugs that paying customers have been reporting for months.
Thank you
Steps to Reproduce
Have the chat run any command on a server in chat, open cursor terminal to see that no output from server is shown.
Even after successful ssh login from chat, the terminal doesnt hold the session.
TEST.ON.WINDOWS.
Expected Behavior
Cursor agent terminal shows server output like it used to and holds a ssh session.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Using the Legacy Terminal Tool partially fixes the issues. Now it holds SSH session and output is shown in terminal, however the agent doesnt recognize the output/execute command, and I always have to cancel to get the Agent to proceed with tasks (I need a custom rule to tell it to consider the command correctly executed when a command is cancelled… which is problematic at times and is only a workaround, not a solution).
About interactivity… it used to be interactive and great, not sure why Cursor team decided to remove that, did someone asked for it specifically? because all I’ve seen is people complaining about removing that possiblity.
Please dont remove things just cause, unless users ask for it.
When will a permanent patch fix this terminal issue? it’s been over 2 months now… prioritize this instead of stuff like live web dev which isnt really a priority considering the amount of bugs currently still open.
Thanks for the update. It’s good to hear the Legacy Terminal Tool helps somewhat with showing output and keeping SSH sessions alive.
The issue where the agent doesn’t recognize command output is a known problem, and the team is working on a fix. There’s a detailed thread with discussion and workarounds here: Agent Terminal not working
To help the engineers, could you please share:
The Request ID from a specific command where the agent gets stuck (chat menu > Copy Request ID)
Which terminal profile you’re using (PowerShell, CMD, WSL, Git Bash)
A screenshot or video of the moment when the agent stops recognizing output
Logs from Help > Toggle Developer Tools > Console (captured while it’s stuck)
About interactivity: the agent terminal is intentionally non-interactive so the agent can run autonomously. That’s a design choice, but the team is working on improvements.