[Internal Error] Unable to parse image

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chat becomes unusable after I copy / paste some screenshots. It seems related to an inability to parse images.
“Internal Error. An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.”

Steps to Reproduce

It’s a normal chat, one that I think I’ve done many times (so it seems like a regression to me). At some point, it just becomes unusable, whatever the prompt, whatever the model I choose.

Expected Behavior

chat should be usable

Screenshots / Screen Recordings

Screenshot 2026-04-15 084537.png
Screenshot 2026-04-15 084537.png1132×154 7.79 KB

Operating System

Windows 10/11

Version Information

Version: 3.1.14 (user setup)
VSCode Version: 1.105.1
Commit: d8673fb56ba50fda33ad78382000b519bb8acb70
Date: 2026-04-14T01:39:23.679Z
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: Windows_NT x64 10.0.26200

For AI issues: add Request ID with privacy disabled

Request ID: 610bdef8-9490-44cd-aa05-db83bbcea164
[internal] Unable to parse image: [object Object]
oae: [internal] Unable to parse image: [object Object]
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Ra (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)

Additional Information

And another one:
Request ID: 5c6db2a4-6a3f-4a58-85da-f26d75e95467
[internal] Unable to parse image: [object Object]
oae: [internal] Unable to parse image: [object Object]
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Object.Ra [as onSubmit] (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)
at async vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40235:100561

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi Thibauld,

Thanks for the detailed report and stack traces. This is a server-side image processing error that we’ve been seeing reports of from other users as well over the last couple of days.

A couple of things to try:

  1. Start a fresh chat – the conversation with the broken images may keep triggering the error on every subsequent message. A new chat should work normally.

  2. Check for updates – open the Command Palette (Ctrl+Shift+P) and run Attempt Update. Some users have reported that updating resolved this.

If you’re still hitting this in a brand new chat (with no prior images), could you share the Request ID from that attempt? That would help us narrow down whether this is tied to conversation state or something else.

7

It just happened to me again right now (all the time, same chat):

Request ID: 1150fa58-2976-4251-85fa-2a9582e34867
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
[unavailable] Error
oae: [unavailable] Error
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)

And also:


Request ID: 2a09ffeb-4229-4a0f-8482-f0e7b1693fce
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
xLi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24552)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Object.Ra [as onSubmit] (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)
at async vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40235:100561
8

Just tried changing the model again (using claude-sonnet-4-6 MAX now) : same.

Request ID: 884228cb-eb3a-4736-a6c1-8cdb08e2e254
[internal] Unable to parse image: [object Object]
oae: [internal] Unable to parse image: [object Object]
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Object.Ra [as onSubmit] (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)
at async vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40235:100561

9

As you can tell, the first errors above (12:01pm message) where not about “image parsing” but “unable to reach the model provider” → then, the latest message (12:03pm) is now finally about “image parsing”.

  • Could it be that the parse image issue occurs only after there was an initial issue with connecting to the model?
  • Could it be that the parse image issue occurs only after a model switch in the same chat?
  • Both at the same time?
10

I just tried switching back again to using gpt-5.4 MAX and got this error :backhand_index_pointing_down: Now my chat is completely toast again. I won’t delete it and will keep it open in case you want me to do something… but man is this frustrating!

Request ID: 797157bd-a2a6-4d7a-9514-b54d7f034fe4
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
[unavailable] Error
oae: [unavailable] Error
at iz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:24637)
at tz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28874:23543)
at uz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:6487)
at i6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28875:11285)
at async uDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41183:15384)
at async Mkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:11486)
at async Mkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41253:17740)
at async P3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28981:16809)
at async Object.Ra [as onSubmit] (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40236:4230)
at async vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40235:100561

11

UPDATE:
I just updated to the latest Cursor version:
Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
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: Windows_NT x64 10.0.26200

Unfortunately, my chat is still unusable:
Request ID: 46a67b29-8e91-4452-8ba7-7c6ebbbc15fa
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
[unavailable] Error
lae: [unavailable] Error
at Bz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:24637)
at Nz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:23543)
at Wz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:6487)
at h6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:11285)
at async vDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41216:15384)
at async zkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:12151)
at async zkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:18486)
at async B3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29014:16809)

13

Got the issue again today (just now). Chat unusable again… :frowning:
Request ID: 13813a8c-a9ec-49ea-8828-a9d8cb9f4ee2
[internal] Unable to parse image: [object Object]
lae: [internal] Unable to parse image: [object Object]
at Bz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:24637)
at Nz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:23543)
at Wz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:6487)
at h6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:11285)
at async vDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41216:15384)
at async zkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:12151)
at async zkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:18486)
at async B3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29014:16809)

Switched model right after but I am getting this error now:
Request ID: 4b0a5882-d68c-4416-a9fe-d0633b354953

{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
NLi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at Bz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:24552)
at Nz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28907:23543)
at Wz_ (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:6487)
at h6u.run (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:28908:11285)
at async vDn.resume (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41216:15384)
at async zkd.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:12151)
at async zkd.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41286:18486)
at async B3e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29014:16809)
at async Object.Ma [as onSubmit] (vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40269:4230)
at async vscode-file://vscode-app/c:/Users/thiba/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40268:100561

14

@mohitjain gentle ping to know if you guys had the time to look at it? It really completely kills my productivity, it’s sooo frustrating to get my chat rendered unusable :sob:

15

I asked Cursor to troubleshoot itself, here is what it had to say:

Here’s a concise read of what’s going on and what you can do about it.

What’s going wrong

1. Unable to parse image: [object Object]

That message is almost certainly a bug in Cursor’s client (or agent pipeline), not something wrong with your project. The [object Object] bit is what you get when JavaScript turns a plain object into a string — so somewhere in the path that handles images in chat (paste, screenshot, or resumed agent context), the app expects one shape (e.g. base64, URL, buffer metadata) but gets another object and blows up while streaming / resuming the agent (streamFromAgentBackend, resume in your stacks).

Your forum report matches that: after pasting screenshots, the thread becomes unusable for any model. That strongly suggests the conversation state for that chat now contains image payload(s) the current build can’t deserialize, so every new message hits the same failure.

2. Provider Error / ERROR_PROVIDER_ERROR

That path is “we couldn’t complete the request to the model provider” — outage, timeout, rate limit, auth, or an oversized/broken request. It can be unrelated (real network/API issue), or it can show up after the image bug if the client sends a bad or empty multimodal payload and the backend rejects it. The "isRetryable":false in your JSON is what the app got back; it doesn’t prove the root cause is only “OpenAI down.”

So: two symptoms, one likely root cause for the bricked chats (bad image handling in a long Agent thread), plus occasional real provider blips.

What you can do (workarounds that actually help)

  1. Treat a poisoned chat as done
    Start a new chat (or new Agent session). Don’t rely on “Resume” on a thread that already pasted images if that thread is failing every time.

  2. Avoid pasting images into heavy Agent sessions until Cursor ships a fix
    Prefer: save PNG to disk and @-mention the file, or describe the UI in text and attach only when necessary. If paste is what triggers the regression, avoiding paste avoids the bad state.

  3. Keep threads shorter when using screenshots
    Long runs (your screenshot showed hours and many files) plus multimodal context increase the chance of hitting edge cases. Splitting work across chats reduces pain if one thread corrupts.

  4. Update Cursor
    You were on 3.1.14 in the forum post; newer patches often fix exactly this kind of serialization bug. Check for updates regularly.

  5. For Provider Error only
    Quick checks: network/VPN, Cursor status, whether custom API keys are valid, and simply retry later. If it happens on every model only in one chat, it’s probably still the broken thread, not your internet.

  6. For support
    You already did the right thing: forum post + Request IDs + version. You can also use in-app Help → Report issue and paste the same IDs so they can correlate server logs.

Bottom line

Nothing is “wrong” with your repo or your prompts in the usual sense. The evidence points to a multimodal / agent-resume bug: pasted images get stored or streamed in a form the client can’t parse, which locks that conversation. New chat, fewer pasted images in Agent, @ files instead, update Cursor is the practical fix until Cursor patches it.

If you want, paste whether the failure happens in normal Chat vs Agent only, and whether new chat without any images works 100% — that narrows it for your next message to Cursor support.

16

Hey @thibauld , sorry about the continued frustration – we’re actively investigating this.

Your observations in your earlier message were actually really helpful. To narrow down the trigger, a few quick questions:

  1. Image source: When you paste screenshots, are these from the Windows Snipping Tool / Win+Shift+S, or are you copying images from a browser / webpage? Specifically, were any of the screenshots taken from pages that might serve .avif format images?

  2. Your theory from earlier: You noticed the “Unable to parse image” error seems to follow a provider error or model switch. Has that been the pattern every time? Or have you seen the image error appear as the very first error in a chat – before any provider issue?

  3. Controlled test: If you’re willing, could you try this sequence in a brand-new chat: paste one screenshot, send one message, confirm it works, then keep chatting. We’re trying to isolate whether the corruption happens at paste time or after some number of messages / model switches.

The corrupted chat you’ve kept open is still useful for our server-side debugging – thanks for holding onto it.