Context: We maintain a production suite of custom GPTs (GPT Builder) used in a daily animation/storyboard workflow. All of our GPTs that rely on the native Image Generation tool broke at the same time, so this is a systemic builder-side issue, not one misconfigured GPT.
Summary
Since around June 9, 2026 (coinciding with the new default model rolling out to GPTs), every one of our custom GPTs stopped displaying generated images. Instead the GPT either:
- outputs the internal sandbox path as plain text, e.g.
/mnt/data/msa_storyboard_clip10_4panel.png, with no image, or - replies “the image generation tool is not available in this session.”
It worked reliably until that date. The same prompt produces the image correctly outside a custom GPT — so the model/tool works; it’s the behavior inside the GPT that regressed.
This is NOT an “enable the capability” issue — I isolated it. I tested two opposite Capabilities configurations on the same GPT:
- (A) All four enabled: Web Search
, Canvas
, Image Generation
, Code Interpreter & Data Analysis 
- (B) ONLY Image Generation enabled, everything else disabled: Web Search
, Canvas
, Code Interpreter
, Image Generation 
It fails identically in both. Image Generation is on, by itself, and the GPT still won’t render — so there’s no capability conflict and nothing left to “turn on.”
This is unrelated to the Actions limitation. The image comes from the native Image Generation tool, not from a custom Action returning a file, so the known “Actions can’t return image/video files” behavior does not apply here.
Steps to reproduce
- Open a custom GPT with Image Generation enabled (reproduced with all capabilities on AND with only Image Generation on).
- Upload reference images and ask for a multi-panel storyboard sheet.
- The GPT returns
/mnt/data/…pngas text (or “tool not available”) instead of the image.
Expected: the generated image renders inline.
Actual: internal /mnt/data/… path as text, or a “tool not available in this session” refusal.
What I already tried (none fixed it)
- Both capability configurations above.
- An explicit GPT instruction telling it not to output
/mnt/data/…and to render inline — helps ~50%, inconsistently (the model still reverts to the sandbox path). - Re-prompting (“don’t give me the path, render the image here”) — sometimes forces a render on a 2nd attempt, not reliably.
- Brand-new chats, multiple accounts, multiple browsers/devices.
Evidence of links can be shared if enabled