Internal error when send a message

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

request:Request ID: caaefd79-6ec9-4c14-b26d-055ccc347558
[internal] Invalid blob data for key fe80bb36101200ff225d18ce25d5336080b9413b0cab4f6faaa2d098a8295a0c. Expected length 391, got 1661.
uie: [internal] Invalid blob data for key fe80bb36101200ff225d18ce25d5336080b9413b0cab4f6faaa2d098a8295a0c. Expected length 391, got 1661.
at s5A (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:23755)
at i5A (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:22658)
at h5A (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:6285)
at kou.run (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:10400)
at async wOa.runAgentLoop (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46811:9955)
at async N3u.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:9277)
at async N3u.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:13663)
at async fMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34308:17597)

Steps to Reproduce

send any message

Screenshots

Operation System
Windows 10

Version Information

Version: 2.6.12 (user setup)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Opus 4.7,GTP5.5,Opus 4.6

For AI issues: add Request ID with privacy disabled
Request ID: caaefd79-6ec9-4c14-b26d-055ccc347558

Does this stop you from using Cursor?

Yes - Cursor is unusable

it is ok last week,but too many same error this week,model gpt 5.5 opus 4.6 and opus 4.7。

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

@tommy_chen Thanks for the report, and I’m sorry for the inconvenience. We do have a bug report open for this and I’ll let you know when it’s fixed. In the meantime however, I do have a couple questions. Are you on HTTP1 compatibility mode for a specific reason (e.g. corporate VPN, required proxy, slow connection etc.?) If you don’t have a reason I always recommended HTTP2 as that will give you the best possible Cursor experience. HTTP1 is a fallback for when HTTP2 doesn’t work properly.

Additionally, could you try the following?

  1. Update Cursor to the latest version.
  2. Fully quit and reopen Cursor.
  3. Try sending a message in a brand-new chat.

Let me know if that helps or if the same error message persists.

i m using some proxy ,and http2 do not work。http 1.1 worked well a week ago,i do not change tools、environments and so on。 i have tried these,and got same error message: 1、update cursor to latest version;2、fully quit and repoen;3、a new panel to send messages。 i found some msg in cursor usage pages, like this:“Aborted, no charged”,“Errored,no charge”,but spending is only 72%。Thanks a lot!

Thanks for the details and screenshots.

Since you mentioned you’re using a proxy and HTTP/2 no longer works, this is likely related to the proxy/network path interrupting Cursor’s streaming connection to the model provider. Could you try these checks?

  1. Temporarily disable the proxy/VPN and send a test message.
  2. If that works, make sure the proxy supports HTTP/2 and long-lived streaming requests.
  3. Try switching proxy modes or allowing Cursor traffic to connect directly without the proxy if possible.
  4. If it still fails, please share any request ID or error details from Cursor logs so we can investigate further.