Internal error - An unexpected error occurred on our servers. Please try again, or contact support if the issue persists

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Internal Error - An unexpected error occurred on our servers. Please try again, or contact support if the issue persists. , please help resolve this issue

Steps to Reproduce

I don’t know, cursor wrote a script with a bug the created a large number of recursive folders and crash my machine and probably the cursor server as well

Expected Behavior

cursor is sending this error response to me for every single question or request I am sending

Operating System

Windows 10/11

Version Information

Version: 3.8.23 (user setup)
VS Code Extension API: 1.105.1
Commit: 7cf19b7482706625cdb70db3211b7dd035b7aa30
Date: 2026-06-23T14:57:42.334Z
Layout: editor
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.256
OS: Windows_NT x64 10.0.26200

Additional Information

need this working asap

Does this stop you from using Cursor

Yes - Cursor is unusable

Thanks for flagging this, and sorry for the disruption while you’re trying to work.

The “An unexpected error occurred on our servers” message you’re hitting on every request is a known server-side issue we’re actively working on. Under the hood, it shows up as a “Blob not found” error: the saved state for that conversation can’t be retrieved on our end, so the request fails. It’s not caused by anything wrong with your account, settings, or the script that ran locally.

Here’s what I recommend to get unblocked now:

  • Start a brand new chat instead of continuing the affected conversation. New chats are generally working. The older conversation’s saved state can’t be recovered, so retrying it or restarting Cursor won’t bring that specific chat back.

Separately, since the script created a large nested folder tree and crashed your machine, it might be worth looking into deleting that huge directory that was created. Be careful to avoid deleting anything unintended.

We’re working on a fix on our side, so you shouldn’t need to do anything beyond starting fresh chats for now. If a brand new chat also fails for you, reply here with the new Request ID and I can take a closer look!

Here’s how you can send us the request ID (and disable privacy mode so we can look closer) if this continues:

To disable Privacy Mode:

  1. Open Cursor Settings with Cmd+Shift+J on macOS or Ctrl+Shift+J on Windows/Linux.
  2. Go to General.
  3. Turn Privacy Mode off / switch to Share Data.

To get the Request ID:

  1. Open the relevant conversation in the Chat sidebar.
  2. Click the ... menu.
  3. Select Copy Request ID.