The chat has just crashed; every model throws an error

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: b5e553c7-8ac2-49ae-af9f-84899f429933
An unexpected error occurred.
[internal] Blob not found
mIe: [internal] Blob not found
at mg_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24345)
at dg_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at wg_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at nCh.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async lQi.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41749:12418)
at async mim.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:12344)
at async mim.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async hCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async ORC.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45410:98816)
at async I7C.submitMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46428:17064)

Steps to Reproduce

Nothing out of the ordinary – I just sent a message in the chat

Operating System

MacOS

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, this is a known issue on our side. A specific existing chat can break because one of its blobs goes missing in storage, and when we try to restore the conversation state it throws Blob not found. New chats work normally.

Workaround: please start a new chat for this request. Unfortunately, the old one can’t be restored.

We’re tracking the bug, but I can’t share an ETA for a fix yet. If we have an update, we’ll post it in the thread.