Terminal Fix Breaks Things Even More

[Artemonim]

Describe the Bug

Your hack to fix the terminal freeze after execution:

1. Doesn’t work
2. Makes it even worse

Steps to Reproduce

Use the Agent chat

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.2 (user setup)
VSCode Version: 1.99.3
Commit: 7db9f9f3f612efbde8f318c1a7951aa0926fc1d0
Date: 2025-07-24T22:25:04.483Z
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.22631

Additional Information

At least try adding Enter instead of an interrupt.
RID: 7944ab30-092c-407d-b840-002b43049c0c

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[mwjt42]

What? Did the agent introduce
…!!!KeyboardInterupt!!!..

Is that supposed to be the fix for the ‘q’ bug?!

[Artemonim]

@mwjt42

Is that supposed to be the fix for the ‘q’ bug?!

■■■■ yeah
Sometimes even ^C or C is inserted directly in the end

[Artemonim]

RID: 8b347dc0-1959-4cf3-9ea8-a2146c302355

Version: 1.3.5 (user setup)
VSCode Version: 1.99.3
Commit: 9f33c2e793460d00cf95c06d957e1d1b8135fad0
Date: 2025-07-30T00:37:52.749Z
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.22631

[Artemonim]

RID: 28cbbbe8-24cc-4ff1-9a1c-5f86453ec22d

[Artemonim]

A hack to circumvent this idiocy:

Call the commands like this: `c || command` - this is necessary due to current API issues.

UPD: Nah, don’t worked

[Artemonim]