Persistent terminal issues

[Dan_S1 (Dan S)]

how about you fix the existing terminal bug that makes the product unusable instead of pushing out new features?

[andrewh (Andrew Milich)]

Could you link to the thread you mean?

[Dan_S1 (Dan S)]

There are SO many threads about it…

it killed workflow. completely. had to downgrade to a much earlier version to continue work rate. not impressed

Agent doesn't capture terminal output

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Whenever my agent runs a command i see it running but when the command ends it disappears and the agent cant capture the output. This is a real bottleneck because i can leverage the agent way less.. I use grok code basically always on my macbook m2 with the newest cursor versions but i have been having this error for multiple versions already. But i get the error on all models. Also when i just open a new chat. Steps to…

Agent Terminal not working

I second this. Also on ultra and losing valuable time. A week of loss so far - slow progress and this is not reliable at all. Hard to justify the cost of proceeding. Downgrading to 2.0.77 seems to be marginally better but now I am beset by agent response being super slow across all agents. Cursor could be a great product and, at first, seemed to be full of promise and I have been using it exclusively as I could see the potential but, right now? It’s problem after problem and while I sympathize.…

Unbelievable shoddy pile of garbage terminal handling

2.0.77 seems to work - altho now im back to “Agent terminals are read only” - which is less than ideal but is workable for now. Prefer being able to also interact with agent terminal too but can live with this for now.

Agent cant access the Terminal not working

[image]still its not fix right?

Cursor version 2.1.39 has terminal bug

The only way this continues to work is if I select a really OLD conversation from the archive and have that open a terminal - this then reverts to old behaviour but i then have to keep using an older conversation and watch the “context” - but this can get you going again. Go into the agent conversation archive… select an old one - where it WAS working.. restart that conversation and have it do something simple… it works again… not sure for how long… but this seems to be working for now

Completely wasting tokens

Hey, thanks for the report. This matches a known terminal issue on Windows. Please try in order: Settings Ctrl+Shift+J → Agents → Inline Editing & Terminal → enable Legacy Terminal Tool, then Ctrl+Shift+P → Terminal: Kill All Terminals → fully restart Cursor Details: Agent Terminal not working If there’s still no output, delete the corrupted workspaceStorage state and restart Cursor Guide and warnings: [SOLVED] Terminal Output Not Showing in Agent Mode - Delete workspaceStorage Folder (v…

Scripts run in terminal fail

I would very much appreciate some detailed guidance to resolve this issue. The agent not being able to use the terminal is KILLING my workflow!

[Dan_S1 (Dan S)]

Any news? I had to downgrade to an earlier version. unsure of the status. can I upgrade? should I risk it?
Thanks