Window terminated during agent running

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

after run a agent task with a few minutes, the IDE window terminated
I executed it four times in a row. The third time, the agent task got stuck, and the rest of the times, Windows terminated.

Steps to Reproduce

Just run a agent task

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.38
VSCode Version: 1.99.3
Commit: 3fa438a81d579067162dd8767025b788454e6f90
Date: 2025-10-29T20:45:40.883Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Now after cursor 2.0.40
It works a few times. But it get window not responding and waste my several tokens

Hey, thanks for the report. We’re seeing similar Agent tab crashes on Windows and macOS in recent 2.0.x versions.

Please try these workarounds:

  1. Check settings.json (known crash trigger):

    • Open Command Palette Cmd+Shift+P → Preferences: Open User Settings (JSON)
    • Look for ”workbench.editor.showTabs": "single"
    • If present, change it to ”multiple" or remove the line
  2. Test in Safe Mode:

    • Run: cursor --disable-extensions
    • This will rule out extension conflicts
  3. Clear chat history:

    • Long Agent conversations can cause memory issues

Also, could you share:

  • When exactly the window becomes unresponsive (file size, task type, duration)?
  • Memory usage in Activity Monitor when it crashes?
  • Does this happen in all projects or only specific ones?

These details will help us decide if we need to escalate to the team.

  1. When a window becomes unresponsive, there are no abnormal memory phenomena, but sometimes there are abnormal spikes in CPU usage.

  2. Then the unresponsive status seems to appear frequently now that I’m using a workspace and multi-root agent setup? But my two projects aren’t large, and there are only 4 chat history entries.

Thanks for the detailed follow-up with the CPU spike info and multi-root workspace context, that’s very helpful!

Quick question: have you tried the workarounds I suggested?

If not, please test:

  • In settings.json, find ”workbench.editor.showTabs": "single" and change it to "multiple”
  • Try a single-root workspace (not multi-root) to see if the issue persists
  • Run in safe mode: cursor --disable-extensions

If none of these help, let me know, I’ll escalate to the team. The CPU spike + multi-root workspace pattern is useful for debugging.

Please share what you find!

Yes,single root workspace is work well
And I’ve tried change showTabs from “single” to “multiple” also works

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