Blob not found + fails on getAgentStreamResponse

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent chat: [internal] Blob not found + fails on getAgentStreamResponse (Linux)

Steps to Reproduce

Environment

  • OS: Linux (Ubuntu/derivative, kernel 6.8)
  • Cursor install path: /usr/share/cursor/resources/app/ (workbench.desktop.main.js)
  • Issue: Affects some chat threads only; works in a new chat for the same prompt.

Symptoms

  • Chat/Agent throws: [internal] Blob not found
  • Stack (abbreviated) includes: rK_ → nK_ → dK_ → h8u.run → xDn.runAgentLoop → W1d.streamFromAgentBackend → W1d.getAgentStreamResponse → N3e.submitChatMaybeAbortCurrent
  • “Reconnecting” has also been observed on chats in the same period.

Request IDs

  • Request ID: cd83f614-6328-46e0-a0be-912fa250487a
  • (Optional) Other reference mentioned in UI: ac405781-9e70-4709-909c-d21ed3e0d688

Local checks already done

  • Project application database: N/A (chats are not stored in our app DB)
  • Local Cursor state: PRAGMA integrity_check on ~/.config/Cursor/User/globalStorage/state.vscdb → ok

Expected behavior

  • Existing threads should keep working; agent should stream without missing stored blobs.

Actual behavior

  • Some threads fail repeatedly with Blob not found; new chat can work for the same work.

Tried http 2 / 1 though

Request ID: cd83f614-6328-46e0-a0be-912fa250487a
[internal] Blob not found
aae: [internal] Blob not found
at rK_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28926:24637)
at nK_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28926:23543)
at dK_ (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28927:6487)
at h8u.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28927:11285)
at async xDn.runAgentLoop (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41235:11960)
at async W1d.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41305:12151)
at async W1d.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41305:18486)
at async N3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29033:16809)
at async Object.Va [as onSubmit] (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40288:4233)
at async vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40287:100561

Operating System

Linux

Version Information

Version: 3.1.17
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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: Linux x64 6.8.0-110-generic

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey there,

Thanks for the report! This is a known issue, and I’ve added your report to the internal report. In the meantime, starting a new chat should fix this (as you’ve noted).