Yes, sometimes it does not detect the end of command execution, and sometimes it does not even run the command, just gets stuck forever
2 Likes
Hi, can anyone confirm if you are seeing this issue and not on Windows or are not using Powershell?
I’ve passed this to the team already, but if we can track down the environment that this occurs in, we should be able to fix this pretty quickly!
1 Like
I also see this on windows in WSL. However I am using NixOS in WSL. I never reported the issue because I don’t suppose anyone would care about an issue with NixOS WSL. But I hope it helps diagnose the issue
2 Likes
In linux mint cinnamon, i’m not sure if it’s the same issue, but it does seem to get stuck with complex terminal situations where the terminal expects you to use arrow keys or whatever to select an “ok” “button”. Also when it needs sudo it is not always obvious that it is waiting for a password. A setting somewhere to always force the system password field to pop up would be a cool option.
sometimes when it wants the complex terminal inputs it isn’t easy to see enough of the output to know what it wants without pushing the terminal to background.
I always use Auto so it might be a gemini tool call issue, it might be something else entirely. Idk. Hope something here helps.
1 Like
That’s good to know! I will pass this to the team 
Related topic that describes this and related problems fully (Windows)
You should check it out @danperks
Same issue here
Have you found any fix? I have tried “teaching” it what to do in those situations and hiw to detect them, but it seems like it is easier to just ask it to try a different method.
Switch to Git Bash as the default terminal. Ctrl+P > Terminal: something about default terminal > Pick gitbash > tell the agent in cursor you switched - it should adapt the commands from there and they’ll complete most of the time.
Thanks!
Does that mean this is a known or even expected behavior on Windows/ Powershell (where I am seeing this constantly)? If so, what’s the recommended solution or workaround?
OS: Windows 11
terminal: powershell
Cursor version: 1.2.4
can confirm I have the same issue here, not for all commands, but pretty regularly, i literally have to be in front of the monitor clicking “Skip” otherwise it hangs indefinitely every 2/3 commands. Very annoying.
1 Like
Same story here too. I tried in Windows 11, Ubuntu (WSL) and MacOs.
As soon as you need something a bit more serious … it starts.
Tried with project rules to remind it to use timeouts and it’s constantly forgetting about them. Tried setting up the default terminal to all the types there are, it’s not working.
This is a big issue.
Has anyone seen any official answer on the topic?
1 Like
Me too! I have never understood any cursor version in the last 6 months or so, when it comes to commands, on Windows - it seems utterly SNAFU to me, and has never gotten better. Besides the annoying “skip” thing, I see dozens of blank lines and random “junk” nearly always comes at the end of every command:
I use 3 different machines - windows 10 and two windows 11 - it’s the same mess on them all.
1 Like
Haven’t heard anything official but sometimes you can get it to make and use python scripts to do some of those things with less errors.
With me it started to occur with the last update.
Version: 1.3.9 (user setup)
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:19:30.453Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
I work on windows 10 using Drupal in WSL2. Cursor doesn’t seem to detect the end of a command anymore and keeps on spinning.
Same issue here. I really like how Terminal is implemented in the newer versions, but because of this bug, I have to re-install the older version (1.2.4) to get it working.
Version: 1.3.9 (user setup)
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:19:30.453Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26120
Running the development in WSL2.
Please fix the detection of the completed command.
1 Like
It still does not wait until “npm install” is finished
Can get around it by telling cursor to always use is_background_False for all tool calls. Best as a rule or memory until fixed. Only seems to be an issue with Cursor’s agent specifically, not external APIs.