We're building a world model for film

Any serious pipeline gets complex fast. You soon hit the same pattern over and over: identical node groups with different inputs — beats for film, variations for ads, or SKU swaps for ecommerce.

Example: you split a story into scenes. Each scene needs the same stages (prompt expansion, reference locks, generations, motion), only the brief and assets change. Ten scenes can mean the same subgraph copied ten times, which clutters the canvas and makes tweaks painful.

Flow Studio uses a dedicated tab-group node that sits on the canvas like any other node—except it embeds a tabbed workspace inside it. You shape one sub-flow once, duplicate it per scene (or shot / variation), and switch tabs to edit inputs. Nodes from inactive tabs hide so you always see one clean slice inside that group—without isolating it from the rest of the workflow.

That hiding is for focus, not isolation: nodes outside the tab group stay fully interactive with ports inside it—shared references, global prompts, mux nodes, and sinks keep connecting the same way they would on an open canvas.

You can also drop multiple tab-group nodes on one graph when different stages need their own iteration loops—for example scenes in one block and soundtrack or localization variants in another—instead of cramming unrelated tabs into a single control surface.

There is also a growing set of utility nodes for everyday operations—text splitting, image crop and resize, and more—so routine transforms stay on the canvas instead of bouncing through extra tooling.

Iteration sinks automatically route each output into the input for the next command and can run that loop as long as you need, which cuts down noisy chains of one-off nodes when you are stepping through variations or batch steps.

Generations from a model show up as a carousel inside the generator node, so you can flip through results, promote keeps, and manage assets without losing your place on the graph—better iteration with less hunting across panels.