Um, based on the public information, I think it works roughly like this:
Yes — image generation currently works in HuggingChat/Omni. The simplest route is to leave Omni selected and ask for the image directly, for example:
Generate an image of a small red robot reading a book in a watercolor style.
This is also consistent with the current HuggingChat home page, which includes “Generate an image.” as one of its starter prompts.
There is also a useful public HuggingChat conversation showing the current behavior: the user asks for an image, Omni takes an agentic
route, and the conversation shows:
Called tool gr1_z_image_turbo_generate
So, at least in the currently observable implementation, you do not need to switch the whole conversation to an image model manually. Omni can call an image-generation tool/Space when the request calls for one.
For a Free account, my best reading of the currently public information is:
On the currently observed ZeroGPU image-generation route, the practical limit is probably around 3 generated images per day.
There is an important caveat to that wording: I do not see an official HuggingChat page saying “Free = exactly 3 images/day.”
Rather, the public information currently fits together like this:
hysts
explained that there is also a So the inference is roughly:
Free ZeroGPU account
|
+-- 5 GPU-min/day
|
+-- 3 ZeroGPU runs/day
|
+-- current observed image tool: 1 run -> 1 image
|
v
roughly 3 images/day
I would treat that as the current effective behavior, rather than a permanent “3-image HuggingChat plan.” The tool being selected, its implementation, and HF’s quota policy can all change.
One other thing that makes this confusing: the normal HuggingChat/Omni allowance and the ZeroGPU image-generation allowance are not the same quota.