After using chat for sometime I get Unexpected Error

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It have been happening for a long time ago, when I am using the same chat for many interactions I get

“An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.”

when the chat gets stuck there, no matter the time I wait to try again later, the only solution is to open a new chat and explain the whole context to the new chat

It happens very frequently

Steps to Reproduce

Use the same chat all the day

Expected Behavior

Chat should not get stuck forever

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
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: f7abace6-d7ef-48a8-9358-5c4ca3f99a01
[internal] Unable to parse image: data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjMwIiBoZWlnaHQ9IjEzNyIgdmlld0JveD0iMCAwIDIzMCAxMzciIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CiAgICA8cGF0aCBmaWxsLXJ1bGU9ImV2ZW5vZGQiIGNsaXAtcnVsZT0iZXZlbm9kZCIKICAgICAgICBkPSJNMjI5LjgxMiAwLjEwMTg1MkgyMjcuNjAyQzIxNS45NyAwLjA4Mzc0MDIgMjA2LjUzIDkuNTA1NTcgMjA2LjUzIDIxLjEzNzlWNjguMTgzNkMyMDYuNTMgNzcuNTc4MyAxOTguNzY2IDg1LjE4ODMgMTg5LjUyNSA4NS4xODgzQzE4NC4wMzUgODUuMTg4MyAxNzguNTU0IDgyLjQyNTEgMTc1LjMwMiA3Ny43ODY3TDEyNy4yNSA5LjE2MTMyQzEyMy4yNjQgMy40NjI5MiAxMTYuNzc4IDAuMDY1NjEyOCAxMDkuNzU3IDAuMDY1NjEyOEM5OC44MDM2IDAuMDY1NjEyOCA4OC45NDcgOS4zNzg3NCA4OC45NDcgMjAuODc1MlY2OC4xOTI3Qzg4Ljk0NyA3Ny41ODc0IDgxLjI0NjQgODUuMTk3MyA3MS45NDI0IDg1LjE5NzNDNjYuNDM0MiA4NS4xOTczIDYwLjk2MjMgODIuNDM0MiA1Ny43MSA3Ny43OTU3TDMuOTQyMDggMS4wMDc4QzIuNzI4MTUgLTAuNzIyNTQ5IDAuMDAxMjIwNyAwLjEyOTAyOCAwLjAwMTIyMDcgMi4yNDg5NVY0My4yNzkyQzAuMDAxMjIwNyA0NS4zNTM4IDAuNjM1Mzc2IDQ3LjM2NTEgMS44MjIyIDQ5LjA2ODJMNTQuNzI5NCAxMjQuNjMzQzU3Ljg1NDkgMTI5LjA5OSA2Mi40NjYyIDEzMi40MTUgNjcuNzg0MSAxMzMuNjJDODEuMDkyNCAxMzYuNjQ2IDkzLjM0MDggMTI2LjQgOTMuMzQwOCAxMTMuMzQ1VjY2LjA1NDdDOTMuMzQwOCA1Ni42NiAxMDAuOTUxIDQ5LjA1MDEgMTEwLjM0NSA0OS4wNTAxSDExMC4zNzNDMTE2LjAzNSA0OS4wNTAxIDEyMS4zNDQgNTEuODEzMiAxMjQuNTk2IDU2LjQ1MTZMMTcyLjY0NyAxMjUuMDY4QzE3Ni42NDIgMTMwLjc3NSAxODIuNzk0IDEzNC4xNjQgMTkwLjEzMiAxMzQuMTY0QzIwMS4zMyAxMzQuMTY0IDIxMC45MjMgMTI0Ljg0MSAyMTAuOTIzIDExMy4zNTRWNjYuMDQ1NkMyMTAuOTIzIDU2LjY1MSAyMTguNTMzIDQ5LjA0MSAyMjcuOTI4IDQ5LjA0MUgyMjkuODAzQzIzMC45ODEgNDkuMDQxIDIzMS45MzIgNDguMDg5OCAyMzEuOTMyIDQ2LjkxMjFWMi4yMjE3N0MyMzEuOTMyIDEuMDQ0MDQgMjMwLjk4MSAwLjA5Mjc4ODcgMjI5LjgwMyAwLjA5Mjc4ODdMMjI5LjgxMiAwLjEwMTg1MloiCiAgICAgICAgZmlsbD0iYmxhY2siIC8+Cjwvc3ZnPg==
EEe: [internal] Unable to parse image: data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjMwIiBoZWlnaHQ9IjEzNyIgdmlld0JveD0iMCAwIDIzMCAxMzciIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CiAgICA8cGF0aCBmaWxsLXJ1bGU9ImV2ZW5vZGQiIGNsaXAtcnVsZT0iZXZlbm9kZCIKICAgICAgICBkPSJNMjI5LjgxMiAwLjEwMTg1MkgyMjcuNjAyQzIxNS45NyAwLjA4Mzc0MDIgMjA2LjUzIDkuNTA1NTcgMjA2LjUzIDIxLjEzNzlWNjguMTgzNkMyMDYuNTMgNzcuNTc4MyAxOTguNzY2IDg1LjE4ODMgMTg5LjUyNSA4NS4xODgzQzE4NC4wMzUgODUuMTg4MyAxNzguNTU0IDgyLjQyNTEgMTc1LjMwMiA3Ny43ODY3TDEyNy4yNSA5LjE2MTMyQzEyMy4yNjQgMy40NjI5MiAxMTYuNzc4IDAuMDY1NjEyOCAxMDkuNzU3IDAuMDY1NjEyOEM5OC44MDM2IDAuMDY1NjEyOCA4OC45NDcgOS4zNzg3NCA4OC45NDcgMjAuODc1MlY2OC4xOTI3Qzg4Ljk0NyA3Ny41ODc0IDgxLjI0NjQgODUuMTk3MyA3MS45NDI0IDg1LjE5NzNDNjYuNDM0MiA4NS4xOTczIDYwLjk2MjMgODIuNDM0MiA1Ny43MSA3Ny43OTU3TDMuOTQyMDggMS4wMDc4QzIuNzI4MTUgLTAuNzIyNTQ5IDAuMDAxMjIwNyAwLjEyOTAyOCAwLjAwMTIyMDcgMi4yNDg5NVY0My4yNzkyQzAuMDAxMjIwNyA0NS4zNTM4IDAuNjM1Mzc2IDQ3LjM2NTEgMS44MjIyIDQ5LjA2ODJMNTQuNzI5NCAxMjQuNjMzQzU3Ljg1NDkgMTI5LjA5OSA2Mi40NjYyIDEzMi40MTUgNjcuNzg0MSAxMzMuNjJDODEuMDkyNCAxMzYuNjQ2IDkzLjM0MDggMTI2LjQgOTMuMzQwOCAxMTMuMzQ1VjY2LjA1NDdDOTMuMzQwOCA1Ni42NiAxMDAuOTUxIDQ5LjA1MDEgMTEwLjM0NSA0OS4wNTAxSDExMC4zNzNDMTE2LjAzNSA0OS4wNTAxIDEyMS4zNDQgNTEuODEzMiAxMjQuNTk2IDU2LjQ1MTZMMTcyLjY0NyAxMjUuMDY4QzE3Ni42NDIgMTMwLjc3NSAxODIuNzk0IDEzNC4xNjQgMTkwLjEzMiAxMzQuMTY0QzIwMS4zMyAxMzQuMTY0IDIxMC45MjMgMTI0Ljg0MSAyMTAuOTIzIDExMy4zNTRWNjYuMDQ1NkMyMTAuOTIzIDU2LjY1MSAyMTguNTMzIDQ5LjA0MSAyMjcuOTI4IDQ5LjA0MUgyMjkuODAzQzIzMC45ODEgNDkuMDQxIDIzMS45MzIgNDguMDg5OCAyMzEuOTMyIDQ2LjkxMjFWMi4yMjE3N0MyMzEuOTMyIDEuMDQ0MDQgMjMwLjk4MSAwLjA5Mjc4ODcgMjI5LjgwMyAwLjA5Mjc4ODdMMjI5LjgxMiAwLjEwMTg1MloiCiAgICAgICAgZmlsbD0iYmxhY2siIC8+Cjwvc3ZnPg==
at cVy (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29387:25583)
at aVy (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29387:24382)
at gVy (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29388:6490)
at d9d.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29388:11311)
at async zfs.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41721:14477)
at async h1h.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41789:12518)
at async h1h.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41789:19638)
at async ryt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29503:16976)
at async Dd (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40776:4226)

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report with the Request ID and the stack trace, it really helped.

This is a known bug: the chat history ends up with an image block that contains an SVG data URI, in your case the Cursor logo SVG, and the SVG image parser can’t handle it. After that, every new request replays the history with that block and crashes again, so only starting a new chat helps. I reported your case internally and I’ll link it to the existing ticket.

No ETA for a fix yet. If there’s an update, I’ll post it here.

Workarounds for now:

  • Start a new chat, like you’re doing.
  • If you paste something from a browser, Figma, or icons into the chat, make sure it’s plain text and not SVG markup or an image block. It looks like the problematic SVG gets in exactly through that kind of paste.
7

It seems to break even when I paste a location of a image or a url of an image

8

Thanks for adding this. It looks like the same issue. In some cases, the paste handler turns a URL or an image file path into an image block with a non-string value, and that breaks chat history the same way as the SVG paste from the first report.

No ETA for a fix yet. As a workaround:

  • If you want to give the model an image, drag and drop the file into chat or use the attach button. Don’t paste a URL or file path as text.
  • If you need to reference an image from the web, send the link as plain text in a separate message. Don’t paste it where the IDE might treat it as an image attachment.

If you can catch the exact scenario, like where you’re copying the URL from: browser, file explorer, Figma, etc., send it over. It’ll help narrow down the repro.