This is one of the (of not THE) single most debilitating and severe issues Cursor has right now. Its been at an absolute minimum two weeks here, if not longer, since these issues were first surfaced (latest version that works for me was 1.6.27, every version after that has this PERSISTENT issue with ZERO terminals invoked by the agent working at all).
You guys are now pushing nightly builds for 1.8.x!!! ALL 1.7.x builds have this issue. Many of the 1.6.x builds have it. MOST of the 1.5.x builds have DIFFERENT terminal issues, as do most of the builds in 1.4 and 1.3, across all platforms. Terminal issues on Windows, which have always been more severe, span all the way back to 1.0 and prior!!
There has not been much communication on this issue. I have seen some blatant misunderstanding ofthe issue by Cursor team members (read a post earlier where a team member was saying that the agent was “just showing the user a command the user could run” which is ABSOLUTELY NOT the case! The panel that appears in the agent, looks different than a normal RUNNING terminal, because it appears the terminal instance IS NOT STARTING, so there are none of the regular ui/buttons surrounding the terminal panel that is normally expected, however it IS INDEED a real, normal terminal panel…its just bugged!)
This issue is clearly affecting many, many people. In addition to my own thread, there are also these threads:
There was an even earlier thread, documenting the frequent terminal stalls, hangs, freezing, etc. that I myself also participated in, starting months ago:
There are also many threads of similar but tangential issues with the termainal hanging in other circumstances (such as after a command DOES run, and completes, usually successfully, the agent does not proceed…I experience this a LOT, even with 1.6.27):
Guys, this is KILLING your product. I am simply unable to move beyond 1.6.27, because terminals beyond that version, are simply dead. They do not work, at all, period, in any way. That is WORSE than what we had before, where terminals sometimes failed to run or the agent sometimes failed to recognize command completion. The problem is now 100% persistent, and has been permanent since 1.6.27. Even the nightly 1.8.x builds, STILL have this issue.
This is 100% utterly debilitating. This utterly blocks all usage of the agent, for anyone doing any serious work with it. I will not be able to move beyond 1.6.27, until this issue is fixed, and you guys seem to be moving on to 1.8.x now….while this game-ending, full-stop issue is NOT FIXED.
The terminal is so critically fundamental to my work, I honestly could care less about any other new features, other QoL improvements, other bug fixes. The only thing I care about when it comes to Cursor: DOES THE TERMINAL WORK? Literally, this is the single driving question I have every day now: Is the terminal GOING TO WORK? Even in 1.6.27, the agent cannot seem to recognize that commands have completed, at least 25-30% of the time. There seems to come a point where every existing terminal instance, becomes unusable, and the agent can no longer execute commands with it. Eventually it starts creating more and more and more terminal instances, and after a while of that, you can have a couple dozen terminal instances (with old instances hanging around, using up memory, and causing other problems.) After a while, the terminal issues mount, and you start getting PTY Host issues, and then ALL your terminal instances, started by the agent or by you, begin having problems, hang crash or disconnect, and the problems just get worse.
IMHHO, there is NOTHING more important right now, than the Cursor dev team, dogpiling on THIS ISSUE, and fixing it once and for all. UTTERLY. DEBILITATING. PRODUCT KILLING. PROJECT ENDING. This issue defines Cursor right now.