Unexpected terminal killing

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When one or more terminals are open in Cursor IDE, closing the Agent window automatically terminates all the existing terminal sessions.

Steps to Reproduce

  1. Open Cursor IDE.
  2. Open one or more terminals.
  3. Open the Agent window.
  4. Run any process/command in the terminal.
  5. Close the Agent window.
  6. Observe that after slight delay the existing terminal sessions are automatically terminated.

Expected Behavior

Closing the Agent window should not affect or terminate any existing terminal sessions. All open terminals and their running processes should continue to work normally.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.15.6 (user setup)
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with steps and the video. The Windows confirmation is helpful.

This is a known issue we’re tracking: if you have both the Agents window and the IDE window open on the same folder, closing the Agents window will also terminate terminals in the IDE window. That shouldn’t happen, and it’s not related to your setup. I don’t have an exact timeline yet, but I’ll post an update here when I have one.

For now, the workaround is:

  • Keep the Agents window open while you have important long running processes in the terminal.
  • Or run those processes in an external terminal outside Cursor, so closing the window won’t affect them.

Let me know if the behavior differs from what’s described, or if you can reproduce it in other scenarios.