The The Sweet Switch: Fruit Heist recipe is scenes you swap, not a new Omni board
/workflows/sweet-switch-fruit-heist is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
/workflows/sweet-switch-fruit-heist is a locked scene list. Recreate it; do not storyboard it again in Kling Omni.
The public recipe is a 9:16 3D Pixar-style heist: a fruit squad sabotages a salad, then realises they are the smoothie. Grappellina, Bananino, Strawberrina, Melonio, and Carrotino are locked character references, not "a cartoon grape." That is a scene graph — stills, prompts, VO, model, durations — not a vibe. Opening Kling 3 Omni and asking for "six shots of a fruit heist" is a new bumper that happens to contain fruit.
Seven scenes, not six Omni cuts
The workflow object is specific:
- Aspect: 9:16
- Scenes: seven, five seconds each, thirty-five seconds of finished tape
- Cast: five named assets — Melonio, Bananino, Carrotino, Grappellina, Strawberrina
- Style preamble: 3D Pixar animation, cinematic lighting, high-end commercial render
- Model on the recipe: VEO 3.1 Fast I2V
- Credit estimate: 441 listed, 875 at full — the model line is the spend
The beats are already written: kitchen huddle, watermelon as a crouton-jar bridge, grape on a vine, carrot under a giant shadow, the smoothie twist, abort to the pantry, the kale-is-safe button. Scenes 5 and 6 chain from the previous frame. The rest are discrete I2V plates with the same refs.
Each scene is a still, then that still animated, plus a VO line already in the graph. Recreate is "materialise this graph," not "make something like this." Read a workflow's credit estimate before you run it: scene count is not the bill. The video model is.
Recreate clones the graph. Omni invents a bumper.
Recreate a viral template is the agent verb: clone scenes, style, and model into your account, then run or remix. Cloning is free. Running is priced like the generation it is. You see the cost before anything dispatches. It is saved but not auto-run — swap the fruit stills, keep the cuts.
Recreate the workflow, not the screenshot is the same rule. A screenshot tells you the grade was candy. It does not tell you seven scenes, five character keys, VEO 3.1 Fast I2V, or 441 credits.
Kling 3 Omni multi-shot is not Movie Mode is the other confusion. Omni takes one prompt and returns up to six distinct shots inside a single generation, usually a 15-second file. Identities have to survive inside that generate. There is no scene planner, no chain off scene five, no combined 35-second export of seven plates. You get one bumper with cuts in it.
Useful for a three-beat gag. Not useful for five named fruits across a kitchen, a fridge, and a pantry with locked refs. Omni restages. Restaging is drift.
Swap the fruit. Keep the cuts.
Once the format works, the workflow is the product. Clone it. Change the SKU stills. Keep the huddle, the bridge, the twist, the 5-second beats. Do not go back to an Omni storyboard every Monday because the last clip performed.
If the clip you care about is not in /workflows, you do not have a recipe. Build one: stills first, then I2V, then save your graph. Do not use Omni's six-shot syntax as a substitute for a scene list you never wrote.
FAQ
Is Recreate the same as generating "fruit heist" in Omni?
No. Recreate clones the public workflow — seven scenes, five character refs, VEO 3.1 Fast I2V, 441 credits when you run the listed estimate. Omni is one generate with internal cuts, typically ~15 seconds, up to six shots. Different objects. Different files.
Does cloning Sweet Switch spend the 441 credits?
No. Clone is free. Credits apply when you run it, at the cost shown before dispatch. Edit prompts, swap assets, and adjust captions while it is still a draft.
Can I use Omni under the hood and keep the seven-scene structure?
Not as this recipe. Omni multi-shot lives inside one short generate. Sweet Switch is seven discrete I2V scenes with locked refs, two of them chained off the previous frame, stitched. Even if a scene happened to render on a Kling family model, the object is still the scene list, not Omni storyboard syntax.
Why is a 7-scene recipe 441 credits when a 3-scene interview can cost more?
Because the estimate is counting the video model, not the scene count. VEO 3.1 Fast I2V at five seconds a scene is a different unit from a dearer I2V row across three scenes. Read the model line on the workflow page before you approve the run.