Cursor Crush: code '5'

When I open the project folder, this dialog pops up and crashes.I had just run a series of tasks using nanobanana MCP to generate background images for an app, but I’m not sure if that was the cause. I’ve had crashes due to memory shortages when converting a PyTorch model to CoreML, but I’ve never had a crash like this one when simply opening a project folder. I tried restarting it, but it didn’t work.

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey, thanks for the report.

Try this workaround: reset Cursor data with a backup:

cd ~/Library/Application Support
mv Cursor CursorBackup

After that, start Cursor again. This helped a few users with the same error: Cursor Crashes Constantly After Latest Update (code: ‘5’) — Cannot Work at All

If it doesn’t help, we’ll need a bit more info to debug:

  • Cursor version (Menu > About Cursor > Copy)
  • Try running from Terminal cursor --disable-extensions and see if it still crashes
  • Logs from Help > Open Logs Folder > main.log
  • Does it crash in an empty folder with no MCP servers?

MCP servers can make the issue worse, but resetting the folder usually fixes it. Let me know how it goes.