When using Cursor Agent with WSL, commands either fail to execute entirely or complete successfully but the Agent doesn’t detect completion, requiring manual intervention.
Two specific issues occur:
Commands don’t run at all - Agent gets stuck with no terminal started. Only solution is “Move to background” as Skip button is unresponsive.
Commands run but Agent doesn’t detect completion - Commands execute successfully but Agent waits indefinitely, requiring manual “Skip” button press every time.
Steps to Reproduce
Use Cursor v1.1.3 on Windows 11 with WSL setup
Install and use Anysphere WSL extension
Run any Agent command (example: cd /home/dev/GitHub/engels74/tgraph-bot-source && uvx basedpyright tests/test_data_fetcher.py)
Observe either:
Command never starts execution
Command runs but Agent never detects completion
Expected Behavior
Agent commands should execute immediately when triggered
Agent should automatically detect when commands complete and proceed to next steps
No manual intervention should be required
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
I ended up requesting a refund for reasons listed here.
I won’t be updating this thread any longer
The issue is still not fixed as of this date, it’s odd that it’s marked as solved as of v1.2.X while it clearly is not solved. I tried supplying all the information needed in the original thread, and also tried via email (never got an answer).
This is still happening in version 1.3.7. I’m using WSL 2 with Ubuntu 24.04. I can’t work like this. On a good run, I might get 5 or 6 commands to execute in a row. But most of the time, after every 2 or 3 commands, I have to stop, close the terminal (either sending it to the background or using “Open in Terminal” in the latest version), cancel the agent job, and tell it to continue. Sometimes it works for another 2 or 3 commands, but many times I have to cancel it again on the first command. Occasionally, I even have to restart Cursor.
I don’t know if you’re working on a fix, but please—do something. Or at least provide a temporary workaround. This is incredibly frustrating.
Having the same issue here, same symptoms as described above on version 1.4.5.
As workarounds:
Killing the terminal or typing exit in terminal sometimes prods Cursor to continue.
I’ve also added a user rule:
IMPORTANT: If I ever stop a terminal command, do not assume I stopped it because I didn’t want you to run it. Check the output to see if it completed successfully, and if it did, continue as a success.
I’m using Cursor 1.6.23
On Windows 11 with Powershell, the agent is not detecting the command completion and just keep waiting forever.
I have to send commands to state the command has completed.
Sometimes, the agent detects the command output and continues. But most of the time I have to let the agent know the command has completed.
And it is basic commands from PS like echo, for example.
