Describe the Bug
I’ve been experiencing a persistent issue with Cursor: it doesn’t recognize when the command prompt appears in the terminal window, and as a result, it can’t continue its work. I use Cursor to assist with writing C# code, and it runs commands like dotnet build (to check for compilation errors) or dotnet test (to verify that all tests pass) in the terminal window.
After the code is compiled or the tests are executed, the command prompt reappears in the terminal window. However, Cursor fails to detect that the build or test process has completed and doesn’t resume its workflow automatically. Earlier versions of Cursor handled this somewhat better, but the situation has worsened with each update, and now this command prompt detection doesn’t work at all and Cursor work “freezes”.
There is one exception: if I manually select “Open in Terminal” from Cursor and then kill that terminal window, the next time Cursor opens a new terminal for a build or test, it correctly identifies the command prompt—once. After that, the issue returns.
Cursor seems to realize it should do something if I press the Skip button a few times after a build or test has run. But since Skip implies failure or a desire to bypass the task, Cursor interprets it as an error or a user-initiated skip, think task briefly, and then attempts to rerun the command—either the same or a slightly modified version.
This leads to constant manual intervention and, at times, Cursor gets stuck in nearly endless loops, repeatedly running the same or similar build/test commands in the terminal without making any progress.
This issue remains same in my both laptops.
Steps to Reproduce
Just giving task to Cursor where it check compile errors with command dotnet build or try to running tests with command dotnet test. After first dotnet build or dotnet test command Cursor normally continue once, but when it run something second time, then Cursor normally never detect anymore that command prompt has appeared.
Expected Behavior
Because Cursor do not detect that command prompt is appeared, it won’t continue it work further and stall so long that “Tool call was ended” message pop up probably because of timeout. Older Cursor version detect this situation better and usually continued although there was stall/freeze situations as well.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.3 (user setup)
VSCode Version: 1.99.3
Commit: e50823e9ded15fddfd743c7122b4724130c25df0
Date: 2025-08-08T17:34:53.060Z
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
Additional Information
Minimum fix is adding “Please continue!” button which have different meaning to Cursor than with Skip button. Now with manual intervene and Skip button this lead to endless loops, because Cursor rarely check, was build or test command successful after pressing Skip button. Of course it will be better, if this bug can be fixed, but trend has been to different direction with new Cursor updates.
Does this stop you from using Cursor
Yes - Cursor is unusable