We’ve been working hard on the reliably of terminal command execution recently, and I’ve passed this to the team to look into - I’d expect significant improvements here in our upcoming version.
Here for my weekly complaint on cursor agent and terminal bugs. Really hoping you guys finally figure this out for 1.6 as it renders cursor useless for any semi-complex work.
I am working on Windows in WSL terminal with Python venv or docker/docker compose.
Cursor agent (any model) in 50% of the cases cannot recognize the completion of command it is executing via terminal. For example:
```
ubuntu@user:/path/$ docker compose ps
results
ubuntu@user:/path/$
```
At this point the agent is stuck still waiting for a response…
Clicking on skip sometimes helps (after a few times), but many times it is just trying to run the same command again.
It feels like the agent is unable to recognize the command line.
Most of the times it is trying to cd into project internal directory, even though it is already in this directory.
Steps to Reproduce
Any request involving execution of multiple cli commands gets stuck
Expected Behavior
Recognize that a simple immediate command ends, when cli prompt appears.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
How do I permanently tell Cursor to stop running foreground commands that stall the chat, and use the text tools instead? It persists in using foreground commands that never complete, such as: “chmod +x scripts/troubleshoot-production.sh”
Is there something I need to put in a cursor rule or change a setting? This is maddening behavior. I have to cancel all these commands and can never prompt cursor to run the text tools instead.
