Describe the Bug
Cursor constantly ends up waiting forever for terminals to finish even when they already finished. I tried all the terminal types and I told it hundreds of times to use timeouts. Even with project rules and it still forges to use timeouts.
You cannot use cursor if you want to be productive.
I use WIndows 11, but it happens with WSL in Ubuntu as well.
I also used it on MacOs .. same story.
The whole purpose of using Cursor is to make us more efficient. There is no efficiency here when we need to constantly supervise it and then help him figure out what happened and so on … it’s just a big waste of time.
The fact that this issue is already present in the forum and lots of people are having it (and still no official response on it) makes it even worse.
Steps to Reproduce
Ask him to do a backend and front end simple project. Node, python .. whatever…
Simple CRUD on a couple of entities. Ask him to use TDD.
it starts in force and then suddenly it can’t keep up and you end up waiting for nothing.
Expected Behavior
Move next when the command finished.
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