Queue it, and let a page make it

If you work with an AI assistant, you can ask it to make pictures in AI Pics. There is one detail that is easy to miss, and we would rather you heard it from us.

What your AI can do#

Through Geenius OS your AI gets a picture tool and a collection tool. For pictures it can check which providers are ready, queue a run with a prompt, a shape, a count and a seed, list runs and pictures, read one, check usage and delete a run with a confirmation. For collections it can list, create and add or remove pictures.

What happens when it queues a run#

The run goes into the history as queued. The Preview, today's maker, runs in a browser. So a queued run is made as soon as somebody in the workspace has AI Pics open. Your AI cannot make it on its own; it should tell you to open the app and give you the address.

Why a browser#

The Preview paints on a canvas and needs no server and no key. That keeps the whole product runnable without a vendor. A real model runs on the server instead, and once its key is set, a queued run is made without anyone watching.

What your AI should say#

That it queued a run, that the pictures come from a simulated Preview unless a real model is ready, and which provider is ready. It should not promise a result. Asking for the providers first gets that answer.

Plans#

Making pictures needs Premium or Max, whoever asks. The door is on every plan, and a Pro workspace gets the library and nothing queued.

A good first ask#

Ask your AI to check which providers are ready, queue one run of two square pictures with the Preview and give you the run id. Then open the app and watch the pictures arrive.

A note on waiting#

A queued run that nobody opens just waits. That is not a failure, and nothing is lost: the run stays in the history as queued until a page claims it, and a page that is closed hands the run on to another. If it matters that a run finishes tonight, open the app yourself or leave a tab open.

See use with your AI.