Cursor makes terminal commands, either within conversation, or in terminals; they can hang indefinitely.
Terminal commands have often ran successfully; but Cursor doesn’t pick up on that
Seems to occur in longer sessions; but not always.
Have tried a number of workarounds:
rules that tell cursor to dev null or echo at end of a chain of commands (limited success)
I tell cursor that the command is ran successfully; but then Cursor sometimes just runs the command again
I copy and paste the output into cursor (but I’d like to avoid that)
I set up a terminal that is in Cursors context and have it run commands there; can work for a while; but for a limited time usually
fresh Cursor resets, and new conversations; but that also becomes tedious because of loss of context
Steps to Reproduce
Ongoing conversations where I ask Cursor to continue YOLO or imply that it should execute commands auto-run.
Cursor will stall on commands indefinitely.
The “Skip to continue” but tells Cursor the command is rejected (however, perhaps it should more say “Let Cursor know the command is completed and continue”
Expected Behavior
Cursor can run autonomously without any further input from me until it deems that the request has been fulfilled.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
hi @yeshuman and thank you for the bug report. We have launched in 1.4.6 improvements for this, could you add more details so we can analyze the cause?
Which model do you use?
Which terminal are you using? (PowerShell/Console or WSL?)
yes i’ve been asking for a button to do this for a while.. so i can tell it to return the terminal.
For me it’s mostly happening on remote linux (windows client, using ssh to remote linux server). just about any command , especially stuff like pylint or clippy(cargo) or anything which has more than a few lines output, but sometimes even a few lines it doesn’t return
something that is kind of working for me at the moment is saying “command successful; please continue”
In answer to your questions:
mostly Claude Sonnet either MAX or non
Win11 WSL terminals
commands are typically running either python/django based tests or I have a Medusa JS project, so running TS based test files or scripts to do with that env.
sometimes those commands can be as simple as cdchanges; but often they’re to do with running test scripts/routines
Often this occurs later in the conversation history; but then I’m observing that you have context reduction strategies that show something like I’m at 90% of context; but then I think you’re having Cursor crunch down on context and show that I’m in a much lower context threshold, i.e. much lower than 50%. When I see this, I’m encouraged to proceed with the current conversation; instead of starting a new one. I like this feature; but maybe there’s some edge cases with it?
This is beyond frustrating and stops me from using Cursor at time as I just give up. I find that if I hit [Enter] a few times in the terminals it is working in Cursor wakes up like it has a bad case of narcolepsy :). I’ve opened a bug report on this also.