Cursor 2.0.34 Crashes on Win10

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

While using the new Agents Tab, the cursor gets unresponsive with message
“The window is not responsive”

Steps to Reproduce

  1. Open Cursor.
  2. Change View to new Agents (since cursor 2.0 release).
  3. New Agent.
  4. Spin up any task.
  5. Freezes, after a while an error message

Expected Behavior

should not crash.

Screenshots / Screen Recordings

Cursor2.0Crash.jpg
Cursor2.0Crash.jpg1612×996 144 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.34 (user setup)
VSCode Version: 1.99.3
Commit: 45fd70f3fe72037444ba35c9e51ce86a1977ac10
Date: 2025-10-29T06:51:29Z (11 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Sonnet 4.5 Thinking

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. We’re seeing similar Agent tab crashes on Windows and macOS in version 2.0.34, you’re not alone.

Try these workarounds:

  • Check settings.json: there’s a known issue with this setting that can cause crashes:

    • Open Command Palette Ctrl+Shift+P → Preferences: Open User Settings (JSON)
    • Look for "workbench.editor.showTabs": "single"
    • If it’s there, change it to "multiple" or remove it

  • Launch in Safe Mode: run cursor --disable-extensions in the terminal to start without extensions. Does it still crash?

  • Also let me know if this happens across all your projects.

  • Clear chat history: long conversations can sometimes cause memory issues and crashes.

Could you also share:

  • When exactly the crashes happen (using AI, editing certain file types, etc.)?
  • What memory usage looked like in Task Manager when Cursor crashed?

This will help us see if it’s tied to known issues or if we should escalate to the team.