Chat error "Blob not found" - RetriableError: [internal] Blob not found

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m experiencing a persistent error when using Cursor. Every time I try to use the chat/agent feature, I get the following error:

“Blob not found” - RetriableError: [internal] Blob not found

The error occurs consistently and prevents me from using the AI features. I’ve tried restarting Cursor but the issue persists.

Request ID: 045f3b2d-8693-4c2d-94f4-3e6d5f019a4d

Full error stack:
[internal] Blob not found
RetriableError: [internal] Blob not found
at ZL_ (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11938:27753)
at J0c (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11938:26488)
at JCb (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:11416)
at Object.classify (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:15921)
at tN_ (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:5707)
at async gSm.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:15273)
at async fH.runAgentLoop (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:21249:3041)
at async jXm.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:13900)
at async jXm.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:22743)
at async DIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12054:1967)
at async fd (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:23360:34887)

Steps to Reproduce

  1. Open Cursor
  2. Try to use the AI chat or agent feature
  3. The error appears immediately

Expected Behavior

The chat/agent should work normally without errors.

Operating System

MacOS

Version Information

Version: 3.8.11 (user setup)
VS Code Extension API: 1.105.1
Commit: e56ad3440df06d22ca7501e65fd518e905486ef0
Date: 2026-06-18T01:40:18.333Z
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.19045

For AI issues: which model did you use?

composer 2.5 fast

For AI issues: add Request ID with privacy disabled

Request ID: 045f3b2d-8693-4c2d-94f4-3e6d5f019a4d

Full error stack:
[internal] Blob not found
RetriableError: [internal] Blob not found
at ZL_ (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11938:27753)
at J0c (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11938:26488)
at JCb (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:11416)
at Object.classify (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:15921)
at tN_ (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:5707)
at async gSm.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11939:15273)
at async fH.runAgentLoop (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:21249:3041)
at async jXm.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:13900)
at async jXm.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:22743)
at async DIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12054:1967)
at async fd (vscode-file://vscode-app/c:/Users/Groppo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:23360:34887)

Additional Information

  • OS: Windows
  • Cursor Version: (please fill in your version)
  • User: loerci_cardoso_gropp

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

hey @Loerci_Cardoso_Gropp, thanks for the report “Blob not found” means the agent tried to load a piece of stored chat state that isn’t available anymore (known issue; we’re working on fixes). Usually a new agent chat works fine; can you confirm whether a fresh chat fails too, or only existing ones?

7

new chat works

8

@Loerci_Cardoso_Gropp thanks for your answer.. oh, unfortunataly, it seems like there was an issue with the selected chats.. it could have been corrupted or had an issue while being saved.. saddly unless a fixes comes up, the only way you can continue using it would be by using the “past chat” capability, you can use it in a new chat by doing “@” and clicking on past chat and the selecting the one that didn’t work, please tell us if you step on another issue. In the meantime, you can clear this bug report as fixed since the issue is known and being fixed in other thread already, have a good day!

10

Hey @Loerci_Cardoso_Gropp, @Tom_Coustols got the diagnosis right here. This is a known server-side issue we’re already working on, and it’s nothing wrong on your end.

What’s going on: that one chat’s saved state lost its reference to some stored data, so every message you send in it fails with “Blob not found.” New chats don’t point at that data, which is why a fresh chat works fine.

Two quick clarifications:

  • That specific chat can’t be resumed right now, so starting a new chat (as you confirmed works) is the way to keep moving. If you need to carry context over, briefly re-summarize the key points into the new chat.
  • The @ Past Chats reference was removed back in 2.0, so it won’t show up in your version.
  • I’d hold off on marking this as fixed. The issue is tracked and a fix is in progress, but it hasn’t shipped yet, and I’ll follow up here once it does.

Sorry for the disruption in the meantime!

12

Hi team,

I am a Pro user. When I try to send a prompt via Composer 2.5 Fast, I immediately get an “An unexpected error occurred” message. My context usage is quite low (only ~15%).

I copied the error details and it seems to be related to a missing blob in the cache:

Request ID: 78083dcb-5f66-40c0-bf3e-b956910a9e90
An unexpected error occurred.
[internal] Blob not found: 33,103,17,132,231,241,115,143,134,118,129,63,7,208,184,100,88,177,166,129,132,154,128,43,70,56,221,4,248,113,86,32
RetriableError: [internal] Blob not found: 33,103,17,132,231,241,115,143,134,118,129,63,7,208,184,100,88,177,166,129,132,154,128,43,70,56,221,4,248,113,86,32
at zCE (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:11938:27797)
at cNh (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:11938:26526)
… (and a few more agent loop traces)

Is there a way to clear this specific cache or force a re-index to bypass this blob error? Any help is appreciated!

13

You’re running into the same known issue this thread is tracking. I took a look at the request ID you shared, and it’s failing the same way: it’s a problem on our side with retrieving some saved state for that chat, not anything wrong with your setup, cache, or network.

To answer your question directly: clearing a local cache or re-indexing won’t get around it. The error means that one chat is pointing at a piece of stored conversation state we can’t retrieve anymore, and there’s no client-side way to bring that back. That specific chat can’t be resumed.

The reliable workaround is to start a new chat. New chats don’t reference the missing data, so they should work normally. If you need to keep going with the same task, briefly re-summarize the key points into the fresh chat.

This is a known issue our team is actively working on. The fix hasn’t fully shipped yet, so I’d hold off on assuming a client update will resolve it. I’ll follow up here once it’s out. Sorry for the disruption in the meantime!

14

Is there a solution for this problem? It’s been 18 days since I reported the bug. It’s making it difficult to use because after each chat it generates an error and I have to open a new chat.