Cursor unable to correctly detect command completions

Bug Reports
1

Describe the Bug

Every other terminal command, cursor doesnt recognized the command status to continue independently, that means I need to intervene manually ever more, since recent updates. Its time consuming and prevents reasonable task size automation. Annoying, and not response from the team.

Steps to Reproduce

Just give it terminal commands to run like docker logs inspection, netstat, etc.

Expected Behavior

when forking a terminal, fork a watchdog to see when that terminal should have completed its job and checks its status properly

image
image928Ă—324 12.4 KB

In the picture attached, cursor will never conclude the execution to decide what to do next. And recently this happens every other terminal command.

In just a minute, another one:

image
image935Ă—256 8.21 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
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.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

9 Likes
3

I pay them enough to be agitated :slight_smile:

4

Yes, I completely understand! Deleted my comment priorly.
I’m a new user and still baffled by the new possibilities

5

I encountered the same problem

2 Likes
6

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
7

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
8

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
10

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
11

That’s good to know! I will pass this to the team :folded_hands:

12

Related topic that describes this and related problems fully (Windows)

13

You should check it out @danperks

14

Same issue here

15

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.

16

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.

17

Thanks!

18

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?

19

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.