Generate through Omni without breaking your existing model flow.
Omni Bridge is the C2C sidecar orchestration lane for multimodal video work: prompt in, references in, route selection, conversational revision, asset packaging, and fallback handling.
Current structure supports text, image, audio, and video inputs; up to 5 reference photos; avatar-aware jobs; 10-second clip planning; and fallback routing across Gemini App, Flow, YouTube Shorts, and future API paths.
- Preferred lane: Gemini App
- Fallback chain: Flow → YouTube Shorts → Vertex API
- Mode: Free-first with provider-aware fallback
- Output pack: Video, thumbnails, captions, prompt log, publish payload
Canonical local-service engine currently modeled as structured stages rather than direct provider lock-in.
Use a structured job shape with intent, inputs, references, avatar, routing, constraints, and outputs.
Treat short clips as chained scenes, preserve watermark awareness, and keep route selection separate from creative intent.
Wire this page to load config JSON dynamically and turn it into a real orchestration cockpit.
These mock sections turn Omni from a text-only concept into a believable routing product with visible workflow evidence.
Show how identity, setting, and product continuity can hold across generations and edits.
A simple storyboard rail makes Omni’s workflow legible at a glance.
Omni Bridge is now a sidecar workflow lane, not a replacement for your existing system. The current Studio structure can keep its normal free flow while Omni evolves into a reusable orchestration engine on top of it.
Important: keep the live file and canonical source file synced after every patch.