Terminal becomes extremely slow after stopping a process with Ctrl+C

[jhsmiranda (Henrique Miranda)]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I’m experiencing an issue with the integrated terminal in Cursor.

After running a process in the terminal and stopping it using Ctrl + C, the terminal becomes extremely slow and unresponsive.
From that point on, any command execution or typing has a noticeable delay.

The only way to fix it is to kill the terminal and open a new one, which immediately restores normal performance.

Steps to Reproduce

•	This happens consistently after stopping a running process with Ctrl+C
•	The issue only affects the current terminal session
•	Killing and reopening the terminal always resolves the problem

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (Universal)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z (3 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. The slow terminal after Ctrl+C indicates possible issues with terminal rendering or process handling - similar terminal delays are observed in version 2.2.20.

Similar reports: Latest v2.2.20 Significant Delay (~27 seconds) Between Sequential Agent Mode Terminal Executions

Meanwhile, try:

• Disable terminal GPU acceleration: Settings > search terminal.integrated.gpuAcceleration > set to off
• Disable hardware acceleration globally: Cmd+Shift+P > “Preferences: Configure Runtime Arguments” > uncomment "disable-hardware-acceleration": true and restart Cursor
• If using zsh - check .zshrc for slow commands (ssh-add, nvm, etc.)
• Try launching Cursor from terminal with flag: cursor --disable-gpu

To help investigate:

1. Does this happen only in Agent Terminal or in regular terminal too?
2. Which shell are you using (zsh/bash)?
3. Which specific processes were running before Ctrl+C (npm, docker, others)?

I’ll pass this to the team for investigation.