Describe the Bug
After the agent opens multiple terminal sessions, the “Kill” (trash icon) button often does not work.
When I try to close terminals using the kill/delete button, nothing happens — the terminals remain open and active.
This leads to two major problems:
Clutter — more and more terminals accumulate, making it hard to keep track.
Agent Stuck — sometimes a terminal becomes unresponsive, and the only way to get the agent to continue is by killing the terminal — but that’s no longer possible.
This used to work reliably in the past.
Steps to Reproduce
Let the agent perform actions that open terminal sessions.
After a few terminals are opened, attempt to close them using the Kill (trash icon).
Observe that in most cases, nothing happens — the terminal remains open.
Note: Sometimes it does work for one terminal, but the others won’t respond. For example, I recently had three terminals open — only one was successfully closed, the others ignored the kill command.
Expected Behavior
The Kill/Delete button should reliably close any open terminal, especially when the agent relies on that to reset or restart tasks.
Until recently, this functionality worked perfectly. This may be a side effect of a new terminal-related update.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
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.19045
Additional Information
It’s great to see frequent updates and improvements to Cursor — thank you!
However, I really miss the update changelog message that used to pop up after new versions. It helped me understand what changed and made me more excited about each update.
Does this stop you from using Cursor
No - Cursor works, but with this issue
