Title: [Bug] "Blob not found" internal error in agent chat (macOS, v3.5.33)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Title: [Bug] “Blob not found” internal error in agent chat (macOS, v3.5.33)

Hi Cursor team,

I’m hitting an “unexpected error” mid-conversation in the agent chat,
and I can no longer continue the thread. I’ve already tried the usual
workarounds without success, so I’d appreciate a backend investigation.

────────────────────
Environment

  • Version: 3.5.33
  • VSCode Version: 1.105.1
  • Commit: aac81804b986d739acab348ed96b8bea6e83cc50
  • Date: 2026-05-22T06:47:48.039Z
  • 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.5.0 (macOS)
    ────────────────────

Request IDs
I have two Request IDs because I temporarily toggled Privacy Mode to
help your team investigate.

  1. Original error (Privacy Mode: ON)
    Request ID: 413ce967-af95-4456-a18a-af2cfee78aa2

  2. Reproduced with Privacy Mode set to “Share Data”
    Request ID: 65203ddf-31a4-430a-83dc-4f4ed4dd65be
    (I switched Privacy Mode back to ON immediately after reproducing.)

Error (same for both)
An unexpected error occurred.
[internal] Blob not found: &��Z�8⭁���0 ;'�2k���դ[�4��
m6e: [internal] Blob not found: …
at qhk (…/workbench.desktop.main.js:35852:26781)
at oDw (…/workbench.desktop.main.js:35852:25580)
at zhk (…/workbench.desktop.main.js:35853:6852)
at Qdf.run (…/workbench.desktop.main.js:35853:11731)
at async NZs.runAgentLoop (…:48220:22008)
at async bKf.streamFromAgentBackend (…:48288:12345)
at async bKf.getAgentStreamResponse (…:48288:19576)
at async zyn.submitChatMaybeAbortCurrent (…:35985:17397)
at async UzE.submitMessage (…:58088:266243)
at async jgA.submitMessage (…:59109:19677)

What happened

  • The error appeared suddenly in the middle of an agent conversation,
    and I could no longer send any further messages in that thread.
  • It is reproducible: the same error also occurs in a brand-new chat
    with the same workflow.

Already tried (none resolved the issue)

  • Starting a new chat (Cmd+N)
  • Restarting Cursor
  • Clear Editor History (via Cmd+Shift+P)
  • Switching the model from Auto to a specific model
  • Temporarily switching Privacy Mode to “Share Data” to reproduce
    (new Request ID captured above; Privacy Mode is now back to ON)

Since none of these workarounds helped, could you check the backend
logs / blob storage state for the Request IDs above? Happy to provide
additional info such as exported logs or more detailed repro steps —
just let me know what would be most useful.

Thanks for your time!

Steps to Reproduce

Title: [Bug] “Blob not found” internal error in agent chat (macOS, v3.5.33)

Hi Cursor team,

I’m hitting an “unexpected error” mid-conversation in the agent chat,
and I can no longer continue the thread. I’ve already tried the usual
workarounds without success, so I’d appreciate a backend investigation.

────────────────────
Environment

  • Version: 3.5.33
  • VSCode Version: 1.105.1
  • Commit: aac81804b986d739acab348ed96b8bea6e83cc50
  • Date: 2026-05-22T06:47:48.039Z
  • 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.5.0 (macOS)
    ────────────────────

Request IDs
I have two Request IDs because I temporarily toggled Privacy Mode to
help your team investigate.

  1. Original error (Privacy Mode: ON)
    Request ID: 413ce967-af95-4456-a18a-af2cfee78aa2

  2. Reproduced with Privacy Mode set to “Share Data”
    Request ID: 65203ddf-31a4-430a-83dc-4f4ed4dd65be
    (I switched Privacy Mode back to ON immediately after reproducing.)

Error (same for both)
An unexpected error occurred.
[internal] Blob not found: &��Z�8⭁���0 ;'�2k���դ[�4��
m6e: [internal] Blob not found: …
at qhk (…/workbench.desktop.main.js:35852:26781)
at oDw (…/workbench.desktop.main.js:35852:25580)
at zhk (…/workbench.desktop.main.js:35853:6852)
at Qdf.run (…/workbench.desktop.main.js:35853:11731)
at async NZs.runAgentLoop (…:48220:22008)
at async bKf.streamFromAgentBackend (…:48288:12345)
at async bKf.getAgentStreamResponse (…:48288:19576)
at async zyn.submitChatMaybeAbortCurrent (…:35985:17397)
at async UzE.submitMessage (…:58088:266243)
at async jgA.submitMessage (…:59109:19677)

What happened

  • The error appeared suddenly in the middle of an agent conversation,
    and I could no longer send any further messages in that thread.
  • It is reproducible: the same error also occurs in a brand-new chat
    with the same workflow.

Already tried (none resolved the issue)

  • Starting a new chat (Cmd+N)
  • Restarting Cursor
  • Clear Editor History (via Cmd+Shift+P)
  • Switching the model from Auto to a specific model
  • Temporarily switching Privacy Mode to “Share Data” to reproduce
    (new Request ID captured above; Privacy Mode is now back to ON)

Since none of these workarounds helped, could you check the backend
logs / blob storage state for the Request IDs above? Happy to provide
additional info such as exported logs or more detailed repro steps —
just let me know what would be most useful.

Thanks for your time!

Operating System

MacOS

Version Information

Title: [Bug] “Blob not found” internal error in agent chat (macOS, v3.5.33)

Hi Cursor team,

I’m hitting an “unexpected error” mid-conversation in the agent chat,
and I can no longer continue the thread. I’ve already tried the usual
workarounds without success, so I’d appreciate a backend investigation.

────────────────────
Environment

  • Version: 3.5.33
  • VSCode Version: 1.105.1
  • Commit: aac81804b986d739acab348ed96b8bea6e83cc50
  • Date: 2026-05-22T06:47:48.039Z
  • 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.5.0 (macOS)
    ────────────────────

Request IDs
I have two Request IDs because I temporarily toggled Privacy Mode to
help your team investigate.

  1. Original error (Privacy Mode: ON)
    Request ID: 413ce967-af95-4456-a18a-af2cfee78aa2

  2. Reproduced with Privacy Mode set to “Share Data”
    Request ID: 65203ddf-31a4-430a-83dc-4f4ed4dd65be
    (I switched Privacy Mode back to ON immediately after reproducing.)

Error (same for both)
An unexpected error occurred.
[internal] Blob not found: &��Z�8⭁���0 ;'�2k���դ[�4��
m6e: [internal] Blob not found: …
at qhk (…/workbench.desktop.main.js:35852:26781)
at oDw (…/workbench.desktop.main.js:35852:25580)
at zhk (…/workbench.desktop.main.js:35853:6852)
at Qdf.run (…/workbench.desktop.main.js:35853:11731)
at async NZs.runAgentLoop (…:48220:22008)
at async bKf.streamFromAgentBackend (…:48288:12345)
at async bKf.getAgentStreamResponse (…:48288:19576)
at async zyn.submitChatMaybeAbortCurrent (…:35985:17397)
at async UzE.submitMessage (…:58088:266243)
at async jgA.submitMessage (…:59109:19677)

What happened

  • The error appeared suddenly in the middle of an agent conversation,
    and I could no longer send any further messages in that thread.
  • It is reproducible: the same error also occurs in a brand-new chat
    with the same workflow.

Already tried (none resolved the issue)

  • Starting a new chat (Cmd+N)
  • Restarting Cursor
  • Clear Editor History (via Cmd+Shift+P)
  • Switching the model from Auto to a specific model
  • Temporarily switching Privacy Mode to “Share Data” to reproduce
    (new Request ID captured above; Privacy Mode is now back to ON)

Since none of these workarounds helped, could you check the backend
logs / blob storage state for the Request IDs above? Happy to provide
additional info such as exported logs or more detailed repro steps —
just let me know what would be most useful.

Thanks for your time!

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi there!

This is a known server-side issue on our end. The error is not related to your setup or network.

As a workaround, please try starting a new chat (don’t continue the conversation where the error occurred). This typically resolves the issue since the error is tied to a specific conversation state.

Appreciate the Request ID, it helps in our investigation! The team is working on it.