# "q^C" and getting stuck after commands have finished?

**URL:** <https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403>\
**Category:** Bug Reports\
**Created:** [July 17, 2025, 5:54pm UTC](https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403 "2025-07-17T17:54:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![twilson-uk](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/twilson-uk/32/71440_2.png) [@twilson-uk](https://forum.cursor.com/u/twilson-uk)\
**Post date:** [July 17, 2025, 5:54pm UTC](https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403/1 "2025-07-17T17:54:36Z")

</div>

### 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

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [July 17, 2025, 6:21pm UTC](https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403/2 "2025-07-17T18:21:27Z")

</div>

Hey, thanks for the report. We’re already working on fixing this issue. I believe the fix will be available soon.

---

<div class="post-metadata">

**Author:** ![yes](https://avatars.discourse-cdn.com/v4/letter/y/ea5d25/32.png) [@yes](https://forum.cursor.com/u/yes)\
**Post date:** [July 18, 2025, 6:08pm UTC](https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403/3 "2025-07-18T18:08:00Z")

</div>

please do. I burned through half of my $60 quota due to this issue and had to upgrade to ultra just to continue.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [August 9, 2025, 6:08pm UTC](https://forum.cursor.com/t/q-c-and-getting-stuck-after-commands-have-finished/119403/4 "2025-08-09T18:08:29Z")

</div>

Closed on August 9, 2025, 6:08pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
