A few days ago, I praised OAI because automations finally seemed to be running bug-free. Today, however, I noticed that the AI spun up an isolated chat for its image generation automations, and the initial execution failed. After a few rerolls, the image successfully generated, but I discovered a weirdness in the asset pipeline: these new outputs completely bypass the user gallery and are instead routed directly into my file library.

Just like every other testing environment OAI deploys, this sandbox is very leaky when coupled with image generation. (Visible COT’s) I suspect this automation space was created to a/b test a new wrapper for ⁠img.gen⁠. It is worth noting that the guardrails in this environment are more aggressive than in my standard chat threads; the generator triggered safety refusals multiple times even when fed completely standart prompts. As is typical for these raw test environments, both the bio tool and the standard image generation mode (in this particular sandbox) are disabled. The only active tool left is the agentic execution mode-the exact one I dislike, as it breaks my preferences, preventing the model from returning to the conversation, sending consecutive messages, or providing immediate commentary. 

Img.gen⁠ saves images to the file library, not the gallery