OSS demos: one recipe, not a new generate every release

Clone a workflow.

An open-source release demo that ships looks like last release: same cuts, same duration, same caption grammar, new screenshot, new version string. It does not look like a fresh Omni storyboard of "the product in 2026." Omni invents coverage. A changelog is not coverage. Lock a recipe. Swap the assets. Press it. Do not rebuild the board because the tag is 2.4.1.

A release demo is a scene graph

The object you need is a workflow: ordered scenes, prompts, a named model, an asset map for the screenshots and the mascot that have to hold. Workflows is the public catalog of those graphs. Browse it. Pick a shape that already behaves like a changelog — a product walk, a before/after, a three-beat "what shipped." Then clone it into the account that will run the next ten tags.

A screenshot of someone else's launch clip is not that graph. You can see dark chrome and a big caption. You cannot see the model, the stills, the scene list, the voice line, or the credit quote. Reverse-engineering a vibe on tag night is how a maintainer ships a cousin film.

A working changelog format is reusable infrastructure. The next tag is an episode of that format, not a new idea.

Recreate clones. It does not auto-run.

Recreate a viral template is the named agent job. The tools are list_public_templates, get_public_template, and recreate_public_template. List the curated public cards. Fetch one by id or slug for a per-scene summary — prompt snippet, voiceover, caption/overlay counts, duration, aspect, video model, required asset names. Then clone.

Cloning materializes a saved workflow in your account: scenes, style preamble, model, asset map. Cloning is free. Running afterward is priced like a full multi-scene generation. You see the cost before anything dispatches. The clone is saved but not auto-run. Edit first. Swap the changelog still. Swap the version line. Then run.

That is the whole product boundary. Recreate copies the object into your account. It is not "make something in this vibe." It is also not a one-tap finished video. Run a one-tap AI video template is a different object: attach a photo, get that template's finished file. A release series needs a graph you can edit. A one-tap needs a photo. Name the object before you press it.

Swap the screenshot. Keep the cuts.

A practical tag night:

1. Clone the recipe you already trust, or save and reuse a video workflow from last tag if the graph already lives in your account.
2. Onboard this release's stills — the README hero, the CLI dump, the settings panel. The asset map names the slots. Fill the slots. Do not rewrite the scene list.
3. Edit the overlay or VO so the version string is this tag, not last tag. Proofread it against git describe.
4. Run. Do not start a blank Omni board because last tag's gag felt cinematic.

The AI video generator is the launcher for a one-off plate when no recipe exists yet. The saved workflow is the launcher for tag 2.4.1, 2.4.2, and 2.5.0. Living in the generator every tag is restoryboarding a format you already solved.

Do not regenerate the mascot. Do not restage the terminal chrome. Do not write a new six-shot "day in the life of a commit" because the changelog has three bullets. Three bullets is a swap. It is not a film.

Do not storyboard Omni from scratch

A fresh Omni pass packs several shots into one generate. Identities have to survive inside that one file. You do not own a scene planner. You cannot chain off last tag's last frame. You cannot export "same cuts, new assets." You get one bumper that happens to contain the word terminal.

Fine for a three-beat joke on a community account. Useless for a changelog that has to match next month. Omni restages. Restaging is how the product becomes a cousin, and how the caption grammar drifts until nobody can say what the demo is.

Create a multi-scene AI movie is the object to use when the format does not exist yet: a scene list you can edit before anything renders. Use it once. Save the result. Recreate or reuse it for every tag after that. Do not spend release week on a blank board and call that a calendar.

If /workflows has no card that matches, you do not have a public recipe. Build one: stills first, then scenes, then save your graph. The next release is a clone, not a prompt.

FAQ

Does cloning a workflow spend credits?

No. Clone is free. Credits apply when you run it, quoted before dispatch. Remix prompts and stills in the draft if the cloned screenshots belong to last tag.

Can I recreate and have it generate immediately?

No. The workflow is saved but not auto-run. That is the point. Remix before you pay. A silent auto-run would bill a full multi-scene generate on last tag's stills.

Why not open Omni every release and attach our logo?

Attaching a logo does not turn Omni into a recipe. You still get cuts inside one file. A photographed mark is not a contract the way a saved scene list with named assets is. Recurring changelog films belong in a recipe.

Is a one-tap template the same as Recreate?

No. One-tap attaches a photo and returns that template's finished video. Recreate clones a public workflow into your account as a saved, editable graph. Release demos need the graph.