Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Same Cursor account, same Agent GenerateImage tool, same 1024x1024 output.
2026-09-09 ~00:50 CST: photoreal portraits ~1.6MB PNG / ~180k unique RGB (skin pores, peach fuzz).
Same morning: every GenerateImage call returns ~300KB / ~50-60k unique RGB (plastic/CGI faces).
Not a prompt bug. Replaying yesterday’s exact product reference images + similar prompt still yields 313KB / 56435 colors.
Changelog 2.4 says the backend is Google Nano Banana Pro. Official GenerateImage schema only has description, filename, reference_image_paths, aspect_ratio. Passing undocumented model / image_size=2K / quality=high is ignored. Grok 4.6 parent chat AND Composer 2.5 subagent both hit the cheap lane. Chat model cannot restore Pro.
Docs say “Requests are never downgraded in quality or speed” and staff said chat model does not select the image pipeline. There is no Settings toggle for Pro vs Flash. If Pro is rate-limited, this looks like a silent Flash fallback with no 429 and no UI.
Steps to Reproduce
- Open a folder workspace in Agent mode (not Quick Chat, not Ask/Plan).
- Call the built-in GenerateImage tool: aspect_ratio 1:1, 1-2 product reference images, photoreal commercial portrait prompt.
- Save the PNG and measure: file size + unique RGB colors (e.g. Pillow/numpy unique over RGB pixels).
- Repeat in a Composer 2.5 subagent.
- Repeat with extra undocumented args: model=gemini-3-pro-image-preview, image_size=2K, quality=high.
Expected vs this account today: always 1024x1024, ~300KB, ~50-60k unique colors. Yesterday on the same account the same tool produced ~1.6MB / ~180k unique colors at the same 1024x1024.
Expected Behavior
GenerateImage should stay on Nano Banana Pro / Gemini 3 Pro Image Preview as documented in changelog 2.4, matching yesterday’s ~1.6MB / ~180k-color photoreal 1024 PNGs.
If Pro is unavailable (preview rate limits / 429), fail visibly instead of silently returning Flash-class ~300KB CGI.
image_size / aspect_ratio should be forwarded to Gemini (known related bug: backend currently drops them, so Gemini default 1K is used). Extra tool args should not be silently discarded if Pro/2K is intended.
Operating System
Windows 10/11
Version Information
Cursor 3.19.19 (Windows user install; app package.json also reports 3.19.13)
For AI issues: which model did you use?
Chat: Grok 4.6 (parent) and Composer 2.5 (subagent). Image tool: built-in GenerateImage (Gemini 3 Pro Image Preview / Nano Banana Pro — not selectable in Settings).
For AI issues: add Request ID with privacy disabled
PASS ~1.6MB (2026-09-09 00:49 CST): e844e706-cbe3-4054-86ba-89a6f325aadb
FAIL Composer 2.5 subagent: 25b1ca25-79ba-41d1-9f6a-893f82148da3
FAIL extra 2K/quality/model params: be64b464-2400-4831-aeda-efcd5b131d20
FAIL replay of yesterday refs (313KB): 04766b3e-9c07-4fb2-83a8-863c3f505ab5
Additional Information
Measured 1024x1024 PNGs on disk:
- Yesterday PASS: 1687010 bytes (1647KB), unique RGB=185619
- Today extra-params FAIL: 333177 bytes (325KB), unique=60424
- Today replay of yesterday refs FAIL: 320930 bytes (313KB), unique=56435
- Today Composer 2.5 FAIL: 305701 bytes (299KB), unique=50396
Resolution did NOT change (always 1024). This is texture/model-tier collapse, not the 1376x768 vs 1536x1024 size lock.
Related existing threads (titles only; new-user link limit):
- Image Generation Only Has Fixed Resolution (staff: backend does not pass size/aspect to Gemini; default 1K)
- Use model native image gen (staff: separate image models; chat model does not pick image gen)
- Image generation models not showing up (staff: Nano Banana is not user-selectable)
- Image editing regression + repeated 400 errors (recent quality regression reports)
Google names Flash (gemini-2.5-flash-image / 3.1-flash-image) vs Pro (gemini-3-pro-image). Today’s 1024 / ~300KB outputs match Flash-class defaults. Please confirm whether GenerateImage silently routed to Flash after a Pro rate limit, and restore Pro or fail loudly.
Please tag image-gen.
Does this stop you from using Cursor
No - Cursor works, but with this issue
