Describe a multi-stage task and the assistant builds the whole pipeline at once — creating several nodes, wiring their outputs into later nodes, and running them in dependency order so frames generate before the video that uses them.
Where: Assistant panel — Describe a task with multiple stages (e.g. two frames then a video)
Key ideas
- Connect actions: The plan can connect one created node's output into a later node's input with a role (first / last / reference / auto); each connect records a run-order dependency so the consumer waits for its source.
- Dependency-ordered runs: Runs execute in waves: a node only fires once every node it depends on has finished. Each wave runs concurrently, awaits all, then a short settle lets outputs land before the next wave reads them.
- Consistency reference: For 'the same subject' requests the assistant connects the first generated image into later ones as a reference so the character/object stays visually consistent across frames.
Steps
- Open the Assistant and describe the full pipeline in one message, e.g. 'a first frame of a cat on the ground, a last frame of the same cat in the air, then a video of it flying.'
- Optionally attach reference images — they're applied to every image stage automatically.
- Send; the assistant creates each node, wires the frame outputs into the video (first/last), and chains the first frame into the second as a reference for consistency.
- The pipeline runs in dependency order — frame 0 → frame 1 (waits for 0) → video (waits for both) — with the panel showing 'Generating…' until the whole chain finishes.
- Review results on each node's card; continue the conversation to refine or extend the flow.
FAQ
Can the assistant build more than one node per message?
Yes. A single response can create multiple nodes, connect their outputs into later nodes, and add a run for each. The runs are ordered automatically by the connect dependencies.
What happens if a dependency can never be satisfied?
The orchestrator runs each ready wave and stops if no remaining node has all its dependencies done, rather than looping forever.