Nodes is Wavemaker’s graph view. Chat is conversational; Nodes is spatial: you see how research, script, stills, clips, and assemble connect.
Open it from the shell Nodes / graph control while a session is selected. Chat and Nodes share the same session — switch freely. (The old /canvas URL redirects into the platform shell.)
Production graphs (display-only)
When you run a catalog video (General Video, commercial, film, …), Nodes shows the live graph so you can follow lineage: which mint plate grounded a character, which still seeded a clip, which QC gate blocked a lane.
You do not rewire a production graph mid-run to change the movie. Surgical changes go through chat iterate (Redo / Replace / Animate / Extend / Edit) or production edit on an idle run. Export and Send keep the bound graph; Nodes is honesty, not a second director.
During a run, nodes update as lanes spawn and settle. Failed gates show the real reason (identity, text, motion, product physics) — not a generic error.
Create workflow (authoring)
When you create a workflow — Discover → New workflow, empty-chat Build my own, or ?create=1 — Nodes is the editor:
- Describe it — Compose Copilot drafts a change set; you Apply or Discard. Nothing is saved until Save as workflow.
- Template — remix a Discover workflow.
- Import — paste ComfyUI JSON (curated packs run natively; unsupported types → residue report).
- Blank — wire blocks yourself.
Typed ports make invalid wiring unbuildable. Authoring is free; you spend credits when you run. Publishing still needs a verified successful run. See Building workflows.
When to use Nodes vs chat
- Chat — briefs, Decide-for-me, iterate, “make it feel more premium”.
- Nodes — understand why a frame looks the way it does; inspect QC; author a reusable recipe.
For everything else, stay in chat. Use both.