Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hi Cursor team,
I’m an Ultra user and I’m currently running into an internal “Blob not found” error in Cursor Agent chat. Multiple existing/older chat threads can no longer be continued. When I try to send a message in those threads, Cursor briefly shows an error and the Agent cannot proceed.
New chats appear to work, so this does not look like a general account, model, or network outage. It seems specific to existing chat history / stored conversation blobs / local or backend chat state.
Request ID
Request ID: 45e27fb7-6598-4218-aa91-28e5b992a8d3
Error
[internal] Blob not found
Stack trace excerpt:
Mpe: [internal] Blob not found
at yy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:27577)
at hsg (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:26306)
at Iy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:7469)
at wsg.run (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:12370)
at async Ble.runAgentLoop (…)
at async yJg.streamFromAgentBackend (…)
at async yJg.getAgentStreamResponse (…)
at async Xct.submitChatMaybeAbortCurrent (…)
What happened
Several existing Agent conversations suddenly became unusable. I can open them, but sending a new message fails with the internal “Blob not found” error. Creating a brand-new chat works, but this means I lose continuity and context from older working sessions.
This is especially frustrating as an Ultra user, because older Agent conversations often contain important project context and debugging history. I did not expect paid/Ultra usage to still run into a state where multiple previous conversations become effectively unrecoverable.
Already tried
- Creating a new chat: new chats work, but old chats still fail
- Restarting Cursor
- Testing normal network conditions without VPN/proxy
- Trying multiple old conversations, all affected in the same way
Expected behavior
Existing Agent conversations should remain usable, or Cursor should gracefully recover if a referenced blob is missing. At minimum, the UI should allow the conversation history to be preserved/exported and provide a clear recovery path instead of failing with an internal error.
Actual behavior
Multiple old Agent chats fail with “[internal] Blob not found” and cannot be continued.
Steps to Reproduce
Operating System
Windows 10 / Windows 11
OS version shown by Cursor environment: win32 10.0.26200
Cursor install path shown in stack trace
d:/SOFTWARE/cursor/
Impact
This does not completely stop me from using Cursor because new chats still work, but it seriously affects my workflow because multiple older Agent conversations are now broken and cannot be continued.
Could you please investigate the backend/blob storage state for the Request ID above, and advise whether there is a way to recover or repair the affected conversation history?
I can provide exported logs, screenshots, or local backup details if helpful.
Operating System
Windows 10/11
Version Information
Request ID: d78f73e0-5526-463b-b72a-3daa6f5c9e8e
Failed to resume after background task completed: [internal] Blob not found
Mpe: [internal] Blob not found
at yy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:27577)
at hsg (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:26306)
at Iy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:7469)
at wsg.run (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:12370)
at async Ble.runAgentLoop (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48122:2927)
at async yJg._runBackgroundTaskCompletionAction (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48193:15077)
at async yJg._maybeDispatchBackgroundCompletions (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48193:17260)
Request ID: a35e0b37-9a6b-4883-8c4b-d5d904112c04
[internal] Blob not found
Mpe: [internal] Blob not found
at yy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:27577)
at hsg (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35721:26306)
at Iy1 (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:7469)
at wsg.run (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35722:12370)
at async Ble.runAgentLoop (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48122:2927)
at async yJg.streamFromAgentBackend (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48193:12152)
at async yJg.getAgentStreamResponse (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48193:20412)
at async Xct.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35852:1973)
at async Object.Qs [as onSubmit] (vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47076:33305)
at async vscode-file://vscode-app/d:/SOFTWARE/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44975:103149
Does this stop you from using Cursor
Yes - Cursor is unusable
