Build it once: save_workflow stores a recipe, not a generate button

Build it once. Run it again whenever you want. Save and reuse a video workflow is save_workflow: scenes, asset map, style, video model — a recipe. Saving or editing a draft is free. Each actual run is priced like a full multi-scene video generation. Using save as if it were generate_videos, or generating a one-off plate every week because you never saved the format, is how you either dispatch a workflow-shaped bill for a six-second shot, or pay to reinvent the same five scenes from chat history.

Required field is name. Versely scene workflows need scenes and an asset map; a direct_scenes pass is required before save so wardrobe, palette, and pacing lock. Skipping the director and saving raw drafts is how repeats drift. Legacy step workflows are the other shape. Do not pass both. The AI movie maker and the workflows index are the browsing doors; this agent job is the keep.

Recipe vs one clip

"Save this so I can run it next week." "Run that saved workflow again — new plot, same characters." "Swap the product shot in scene 2." Those are this job. A first run uses your saved scenes exactly. A re-run writes a fresh plot around the same cast and style so repeats do not feel identical — unless you stripped the theme.

A single prompted clip with no recurring subject is generate a video from text. A complete script you want rendered once, now, is turn a script into a finished video. A clock on the recipe is run a recurring video series. Characters and products that must match across scenes are set up reusable characters and products before you treat the save as done.

The waste is the weekly blank prompt: same bottle, same caption style, five new scene generations planned from scratch because nothing was stored. The other waste is saving a one-shot B-roll and then hitting run as if it were cheap — it is not; the run is the multi-scene bill.

Draft is free, run is not

Tinker on the draft. Bind assets. Direct scenes. Save. Watch one run before you schedule. A scheduled hollow recipe is a cadence of expensive misses.

FAQ

Does save_workflow generate the video?

Not by itself. Save stores the recipe. run_workflow (or the script one-shot, or a schedule) is the generate. Confusing save with run is how people expect a file and get a name in a list.

Why is a re-run not identical?

On purpose, when a theme exists: new plot, same assets and style. If you needed a carbon copy, say so or strip the freshness. If you needed a series, that variety is the point.

Do I need direct_scenes?

Yes, before saving Versely scene workflows. Raw drafts drift in wardrobe and light. That drift is not a free aesthetic; the next run spends video credits on the worse prompts.

Can I skip assets and describe the character in every scene prompt?

You can. You will fight identity every run. Upload the cast once. Reuse the keys. That upload does not use generation credits.