Define the stages
Keep a supported sequence and named inputs in a Generator. Review its configuration before using it again.
Build a Generator for a repeatable task, supply new inputs, review the plan and credit total, then inspect each output in Work.
Start creating in Chat ↗Illustrative event announcement: the recipe is saved, while the event name, date and location change for a new run.
Keep a supported sequence and named inputs in a Generator. Review its configuration before using it again.
Enter the current details and inspect the prepared tasks, selected sources and total credit cost before starting.
Open the run in Work. Completed, failed and partial tasks remain distinct; choose usable outputs rather than assuming a whole batch succeeded.
The same configured steps can produce different results with different inputs.
Check facts, visual details and each saved output. A Generator does not guarantee uniform images or publish the result. See the run guide or collect selected outputs for handoff.
An illustrative example. Review current inputs, settings and the quote in your workspace.
Draft a concise invitation using this run’s approved event name, date, time and venue; do not invent attendance details.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Run a repeatable creative process with new inputs.
Explore ↗Create from structured facts and review proposed changes.
Explore ↗Package selected versions for a clear handoff.
Explore ↗Supply new inputs, review the plan and inspect each task result.
Explore ↗Give each stage a clear purpose and reuse supported templates and compatible models. Save configuration changes before preparation, then supply this run’s facts and sources. Check effective models, settings, dependencies and the total quote. A proposed public recipe is not a runnable Generator by itself.
Reuse a GeneratorInspect individual task outputs and visible partial failures. Keep useful successful work and review any eligible retry as a new request. Select exact accepted versions for Studio or delivery instead of automatically handing off every task. Configuration helps coordinate the process; output quality still needs inspection.
Inspect model supportNo. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
Use the contextual links for the source, artifact or decision you have now. A feature explains a tool, a workflow explains its steps and an output guide explains the saved result.