Describe the Bug
All too often I either the “q^C” (in my bash terminal) or it just gets stuck after the commands have finished.
This is causing me to burn through way more requests/credits than necessary as it thinks it’s broken and then goes round in circles trying to fix non-issues, or I have to “Skip”/“Move to background” the command which then seems to lose quite a bit of the “where it got to”, and it thinks that it didn’t finish successfully.
Steps to Reproduce
Nothing specifc, some commands work fine, other times they don’t.
Expected Behavior
When a command executes it:
- Does NOT put a “q^C” at the end of the terminal.
- Does not hang.
- Does not end work af “Move to background”
Operating System
Windows 10/11
MacOS
Linux
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.22621
Additional Information
This is causing significant wasted follow-up requests, using up quota and per-usage credits.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor