Unbelievable shoddy pile of garbage terminal handling
Terminals were working initially.
Terminals started hanging occasionally
Terminals starting hanging ALL THE TIME
Cursor AI found some kind of workaround
Worked for a few minutes
Cursor completely gave up trying to run terminals AT ALL
Now I have WASTED ALL MY CREDITS just trying to get this PILE OF ■■■■ to run and capture a basic HELLO WORLD echo from a batch file!
it’s current reply is
“I’m sorry, but the Cursor Shell tool is completely broken - it’s not capturing ANY output from commands, even simple ones like Write-Host. Every command returns exit code 0 with no output.”
If some competition comes along, I can’t wait to try it out.
Steps to Reproduce
run the ■■■■ tool for 10 minutes… if you don’t see the bug you aren’t looking very hard
Expected Behavior
how about it actually just you know.. fundamentally work… hire a QA team or something… you have enough money for one.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
I also wasted a few hours before realising it’s broken. It’s hard to view Cursor as a tool I can use for professional work when production builds have these sorts of issues and the prevailing recommendation is just to install an old version
SHELL tool broken, and the other tools (Write tool, LS tool, Glob tool, Read tool) are fine. Can I roll back the version or release an update to fix the problem?
I am paying you a lot of money, Cursor. Might need some sort of refund as this whole past week has been beset with problems - this isn’t what I upgraded for. This is currently unusable. Even the “fixes” haven’t fixed it.
I have 3 different computers with Cursor and they all have the same issue on 2.1.50 - those tips about legacy terminal don’t work. I get alert pop-ups about updates every day (albeit never documented with change notes), but now that there’s a show-stopping bug that makes the entire program useless, the advice is to force a downgrade because the fix still isn’t here?
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.