Describe the Bug
Cursor is apparently arbitrarily timing out the processes it is starting as a part of a Chat agent process. The timeout duration must be configurable.
Steps to Reproduce
Make Cursor run in agent mode and have it execute long-running processes, such as unit tests. At some arbitrary point it will send the sequence:
“q^C”
to the terminal, which will stop the process (^C = Ctrl-C). Cursor will then act surprised and say “The command seems to have gotten interrupted. Let me try running it again:”
Usually Cursor explicitly shows a message like “The command takes too long”, but I can’t find it in the Chat history after the agent ends - it’s like it deletes some parts of the process.
Here’s another screenshot where Cursor sent a Ctrl-C to the terminal and stopped the test:
Expected Behavior
Cursur letting the commands run for as long as they need, OR until the user stops them.
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
Additional information
Note that this might or might not be related to other reports of Cursor sending “q^C”, but this report is specifically about cursor timing out prcesses that it started.
The problem is indepentent of which model is used, including “auto”.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor