Image error: The model provider could not read an image in this conversation. Animated GIFs, corrupted files, and images with extreme dimensions are rejected. Start a new chat without that image to continue

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I ask Gork‑4.6 to analyze and recognize a Figma design by pasting the Figma design link, an “Invalid Image” provider error is thrown.
Request ID: 5d0d7a28-e848-4d48-a4cc-2bdc162aafea
The error message says:

Image error: The model provider could not read an image in this conversation. Animated GIFs, corrupted files, and images with extreme dimensions are rejected. Start a new chat without that image to continue.

I only provided a public Figma web link instead of uploading any local image file. The backend incorrectly treats the Figma design resource as an invalid image and fails to process the Figma link analysis request.

Steps to Reproduce

  1. Open Cursor IDE on Windows 11
  2. Send this Figma design URL in chat and ask Grok‑4.6 to parse the UI design
    Link: https://www.figma.com/design/odBHtkj3x1OFguGAKn6eEb/%E6%96%B0%E5%AE%B4%E8%8D%9F%E4%BD%B3PC-%E5%8D%A2%E5%A8%B4?node-id=17276-12149&m=dev
  3. Immediately the “Invalid Image” provider error pops up, chat cannot proceed.

Expected Behavior

Cursor should correctly fetch and read the public Figma design resource from the provided web link. Gork‑4.6 should analyze the UI layout, components from this Figma link normally without throwing an invalid‑image error. It should not misinterpret a Figma hyperlink as an uploaded image file.

Screenshots / Screen Recordings

微信图片_20260918112114_191_30.png
微信图片_20260918112114_191_30.png1143×507 33.8 KB

Operating System

Windows 10/11

Version Information

Version: 3.16.2 (system setup)
VS Code Extension API: 1.128.0
Commit: 35d1ed8352c5b21573fc69a8645ec758060f5e10
Date: 2026-08-11T06:53:34.245Z
Layout: IDE
Build Type: Stable
Release Track: Nightly
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Gork‑4.6 Extra High Fast

For AI issues: add Request ID with privacy disabled

Request ID: 5d0d7a28-e848-4d48-a4cc-2bdc162aafea
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Invalid Image”,“detail”:“Image error: The model provider could not read an image in this conversation. Animated GIFs, corrupted files, and images with extreme dimensions are rejected. Start a new chat without that image to continue.”,“isRetryable”:false,“additionalInfo”:{“providerStatusCode”:“400”},“buttons”:,“planChoices”:},“isExpected”:true}
Invalid Image Image error: The model provider could not read an image in this conversation. Animated GIFs, corrupted files, and images with extreme dimensions are rejected. Start a new chat without that image to continue.
NonRetriableError: Invalid Image Image error: The model provider could not read an image in this conversation. Animated GIFs, corrupted files, and images with extreme dimensions are rejected. Start a new chat without that image to continue.
at oHg (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6978:82956)
at H8s (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6978:81539)
at THg (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6979:12878)
at Object.classify (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6979:17456)
at wHg (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6979:5856)
at async i$s.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6979:16808)
at async qae.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7122:34605)
at async pwo.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15024:14664)
at async pwo.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15024:32009)
at async qAe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7089:2524)

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with the Request ID and stack trace. That really helped us track this down. I can see the screenshot showing the error tray Invalid Image on the Extra High Fast model.

What happened: when you paste a Figma link, the agent uses the Figma integration to pull in design context and screenshots so it can analyze the UI. One of the assets Figma returned was an extremely thin image, basically a divider line sized 786x1 px. The model provider for Grok 4.6 rejects images with extreme dimensions like this, under 8 px on one side. Since that asset stays in the chat history, every next message in the same chat hits the same error. So the link itself is fine. It just tripped on one tiny image inside the design.

What you can do right now:

  1. Start a new chat. The old one will keep failing no matter what you send.
  2. Paste the Figma link again and add something like do not fetch screenshots or image assets, use the design context only, or ask it to describe the layout in text.
  3. If it still fails, run the Figma step on a different model like Composer, then switch back to Grok 4.6 for implementation.

This isn’t related to your setup. I’ve passed it to the team and we’re tracking it, but I can’t share an exact timeline yet. If you hit it again, send the new Request ID and we’ll take another look.

7

Thank you very much for your detailed investigation and clear explanation of this issue!

Now I understand the root cause: the Grok‑4.6 provider rejects extremely thin assets such as the 786×1px divider line exported from Figma, and this broken asset pollutes the whole chat history.

However, 1‑px divider lines and thin border elements are extremely common in real‑world Figma UI design work. Almost every web‑app design contains these thin separating lines. It would be really helpful if the model provider could relax this hard restriction on minimum image side‑length in future updates. Otherwise, many regular Figma design links will keep triggering this error and break the workflow for frontend developers.

I will follow your suggested work‑around for now: starting fresh conversations and adding instructions to skip fetching image assets. Hope this limitation can be improved on the Grok‑4.6 side soon. Thanks again for your support!

8

Glad the breakdown helped. And thanks for the feedback, you’re right. Thin 1px dividers and border elements are standard in UI design, so it’s really easy to run into this when working in Figma.

One important point: this shouldn’t break chat. Handling these thin assets more carefully is on us too, not only on the provider side. I passed this to the team as feedback. I can’t share a timeline yet, but I’ll reply here if there’s an update.

For now, the workaround is the same: start a new chat and add an instruction not to pull screenshots or assets, or run the Figma step on another model, like Composer. If you hit this again, send a new Request ID and we’ll take a look.