No preview, no file saved. Reproduced in Agent mode with simple prompts (e.g. red apple on a white plate), after full Cursor restart, and in an ASCII-only empty folder D:\img-test.
Network Diagnostics are all green after fixing Kaspersky SSL interception and setting HTTP Compatibility Mode to HTTP/1.0. Chat/Agent text work; only image generation fails. Used to work earlier.
Steps to Reproduce
Open Cursor IDE on Windows 10, open any project folder (Agent mode, not Quick Chat).
Optionally open an empty ASCII-only folder, e.g. D:\img-test.
Start a new Agent chat.
Ask: Generate a single red apple on a plain white plate, photorealistic, soft daylight, no text.
Agent calls GenerateImage.
Observe: Failed to generate image, error: Error — no preview, no file in the folder/assets.
Retry with another simple prompt (mug photo / simple illustration) — same Error.
Confirm Network Diagnostics are all green (after Kaspersky SSL fix + HTTP Compatibility Mode = HTTP/1.0) and fully restart Cursor — GenerateImage still returns the same Error.
Expected Behavior
GenerateImage should succeed: show an inline image preview in the Agent chat and save a PNG to the project/assets folder. Simple prompts should work when Network Diagnostics are all green and a project folder is open.
Auto (Agent mode). GenerateImage fails with: Failed to generate image, error: Error. Same failure when testing from an ASCII-only folder D:\img-test. Not Tab.
For AI issues: add Request ID with privacy disabled
Request ID: c0bdb658-5618-4104-8454-9d364b8c5f28
Additional Information
Troubleshooting already done on PC:
Network Diagnostics initially FAILED:
DNS slow (~2343ms)
SSL intercepted by Kaspersky (Kaspersky Anti-Virus Personal Root Certificate)
Chat: streaming buffered by proxy
Agent: bidirectional streaming not supported by http2 proxy
Fixed Kaspersky HTTPS interception / exclusions for Cursor.
Set HTTP Compatibility Mode to HTTP/1.0.
Fully restarted Cursor.
Network Diagnostics after fix: ALL GREEN (DNS, SSL, Chat, Agent, API, Auth, CDN, etc.).
GenerateImage STILL fails with bare: Failed to generate image, error: Error
Also ruled out Cyrillic path:
Failed in project under D:\Важное...
Failed twice in empty ASCII-only folder D:\img-test (no files created)
Chat/Agent text works. Only built-in GenerateImage fails.
Feature used to work earlier.
Hey, thanks for the detailed report and for carefully ruling out the network side.
This isn’t caused by the network, Kaspersky, or HTTP/1.0. The image generation requests are reaching us, but they’re being rejected because of a usage limit: the included usage for this billing cycle has been used up, and the account is now limited to Auto mode. That’s why text chat on Auto still works, but Generate Image doesn’t. Instead of showing a clear limit message, the tool only shows Error. That shouldn’t happen, and I’ve passed it on to the team.
You can check the current usage status in Dashboard > Usage. Your cycle resets on 1 November. Please let me know whether image generation starts working again after the reset or after turning on on-demand usage in the spending settings. That’ll help confirm whether the limit is the only cause.
Same error, but it does not match the usage-limit explanation.
Cursor 3.27.14 (stable), macOS, Agent mode, model Grok 4.7. Plan is The X Subscription Plus.
GenerateImage fails every time with:
Failed to generate image, error: Error
No image preview and no file is saved. I retried simple prompts (a cat, a teapot, a lemon, a green apple) several times today, 27 October 2026, around 16:14–16:28 JST. Each attempt returns in about 0.6–2.7 seconds.
What I already checked:
Included usage was reset today and the remaining balance is not zero.
Image generation works in Imagine on the same account.
Chat and Agent text responses work.
An earlier HTTP/2 proxy streaming error was fixed by disabling HTTP/2. Network diagnostics for Chat and Agent are no longer failing. GenerateImage still returns only “Error”.
So this does not look like a used-up usage pool or an Imagine outage. The image request reaches Cursor and is rejected with an empty “Error”, with no model-restriction, safety-filter, or provider status message.
Hey, thanks for the detailed report. You’re right, this isn’t the same case as the one higher up in the thread. Your usage and access to Imagine both look fine.
Right now, on the Plus plan, image generation requests from chat get rejected when Grok 4.7 is selected. On top of that, the tool shows just Error instead of a clear message. That shouldn’t happen, and it’s not related to your setup or network. I’ve passed it on to the team.
For now, you can try this workaround: before sending the image request, switch the chat model to Grok 4.6 or Grok 4.5. Composer 2.5 is currently affected in the same way as Grok 4.7.
Let me know if that helps. I’ll post an update here when I have one.
Hey @T.Suzuki, thanks for checking. Glad the workaround helps. For now, please generate images with Grok 4.6 or 4.5.
This case is different from the original report at the start of the thread, so to avoid mixing them up, please open a separate thread for the GenerateImage issue on Plus with Grok 4.7. You can just copy post #9 there and add a link to this thread. I’ve already passed the issue to the team. I don’t have an ETA yet, but I’ll share an update when I have one.
If you have time to test Composer 2.5, please post there too and let me know whether it works or not.
GenerateImage works again for me after the included usage quota reset. I did not enable on-demand spending.
Confirmed with a simple test prompt (“red apple on a white plate”) in Agent mode — image generated and saved successfully.
So for my original report, the usage limit was the root cause. The remaining issue is UX: when the quota is exhausted, GenerateImage still returns only a bare Error instead of a clear “usage limit exceeded” message.
Hey, thanks for coming back with an update. It’s clear now that the cause in your case was the usage limit.
I agree, in this situation there should be a clear message about the limit, not just a plain Error. We’re tracking this issue and it’s been passed to the team. There’s no timeline yet, but I’ll reply here when there’s an update.
If you see Failed to generate image, error: Error again, first check Dashboard > Usage. That’s the fastest way to confirm if it’s related to the limit.