Cursor constantly crashes after Agent response

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Almost every time I interact with an Agent using either Auto or any of the models directly, at the end of generating either changes or even just text, Cursor freezes completely and must be killed/restarted. Sometimes it appears to make all the changes it needed to, and sometimes appears to freeze before completing thinking.

Sometimes when I kill Cursor, I get a ‘This operation cannot be performed’ message from Windows.

Steps to Reproduce

Ask an agent to review a file, make changes, and/or explain code. The agent will review successfully, and make changes, but then freezes the entire IDE.

Expected Behavior

Cursor doesn’t freeze and allows continued conversation

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (user setup)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto, Sonnet 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known bug, and the team is already working on a fix.

Workaround that helps immediately:

  1. Open Command Palette Ctrl+Shift+P → Preferences: Open User Settings (JSON)
  2. Find ”workbench.editor.showTabs": "single"
  3. Change it to ”multiple" or remove the line
  4. Restart Cursor

This setting is causing the Agent to freeze in your version.
Let me know if this helps!

Thanks for the quick response!

Unfortunately, that line is not present in my user settings JSON:

is that expected? Is there something else I can/should try?

Thanks for checking. Try launching Cursor without extensions to see if the freeze goes away.

cursor --disable-extensions

Then test the Agent. If everything works without freezing, one of your extensions may be causing the issue.

You can check which extensions are active: Ctrl+Shift+P → Developer: Open Extension Monitor

Let me know if this helps!

Unfortunately this didn’t help either. I did also try adding “workbench.editor.showTabs”: “multiple” as well. I don’t have any extensions but did try with extensions disabled and same thing. This has really ruined my productivity.

I’m having the same issue, disabling extensions and ”workbench.editor.showTabs": “single” doesn’t have any effect.

Cursor just freezes after 1-2 chats are completed. This renders Cursor completely useless.

Do note I just installed a fresh Windows 25H2, latest Cursor version system install.

[Window Title]
Cursor

[Main Instruction]
Cursor

[Content]

Version: 2.0.77 (system setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z (1 day ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

[Copy] [OK]

Thanks for the extra info. This might be an issue related to MCP servers that the team is already working on. MCP servers, especially GitHub and Atlassian, can cause Agent freezes or crash Cursor.

Please check and disable MCP servers:

  • Do you have GitHub or Atlassian MCP servers enabled? If yes, disable them
  • If you have many servers (more than 80 tools in total), temporarily disable all of them
  • Restart Cursor and test Agent

If the freezes continue:

  • Open Help > Toggle Developer Tools > Console tab and screenshot any errors when the freeze happens

Please let me know which MCP servers you have configured and whether disabling them helped!

Hello i am having the same problem. I dont have any mcp server set up.

1 Like

I am also having the same issue. I’m on Windows 11. It happens after almost every agent response.

@deanrie Hello , I am also encounter the same issue in Plan mode . It ask me questions , then I choose the answer . Then it will stuck.

I tried using WSL to see if that would make it more stable… no luck. It is still crashing.

I am having the same issue, it is a massive problem for me. Basically freezes after every 1-2 agent responses. I tried all fixes and nothing seems to work.

Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

I can say for me that if you keep the IDE as the active window, it seems to work just fine. If you navigate away to a different app when it finishes, that is when it seems to lock up.

Sadly, this didn’t work for me. It looks like the bottom info bar still updates and refreshes, but the interface is otherwise totally locked.

When I restart with extensions disabled, though, it looks like it’s working. Time to do the one-by-one game…

EDIT

So, after a few agent chats, it froze up again, still with extensions disabled. Back to the drawing board.

Also experiencing this, I’ve been updating cursor every time there is something new. I manage to get a few more chats in if I restart my pc.

This issue isn’t being addressed and its a big one! completely unusable. Please escalate to urgent @deanrie

1 Like

+1 on this. Restarting my PC also seems to help giving me 4-5 chat responses before crashing instead of 1-2.

after weeks of suffering with this, I may have found the issue.

I found another thread mentioning this issue occurs when Cursor is not the selected window when the agent finishes. Running an agent and ensuring Cursor is the selected window seems alot better.

I think the issue is windows notification, which is triggered when cursor is not the selected window. Since turning the notifications off, I’ve not been getting any freezing (for now).

Hope this helps, please try :saluting_face:

Absolute legend. Turned off notifications and everything works now!

1 Like

Hey everyone, could you update to version 2.2? We’ve made many improvements in this update and fixed a lot of bugs.

You can download it here: Download · Cursor
Or update via Help > Check for updates

Please check if the issue persists on the new version and let me know. If the bug remains, I’ll pass it to the engineering team right away.