Scene state as the source of truth
Pretzel stores product, room, character, camera, timing, and output rules as a structured project master. The prompt is no longer the only memory.
Core innovations
Directed scene state for repeatable AI video.
Pretzel's core bet is simple: if a video model should keep something consistent, that thing needs to exist outside the prompt as structured state.
Previs
Structured control before render.
Locks
Structured control before render.
Variants
Structured control before render.
Pipeline
From vague prompt to inspectable project master.
01
Define the job: product shoot, hook test, or walkthrough.
02
Lock the canonical assets and visual references.
03
Direct camera, blocking, timing, and scene notes in previs.
04
Compile consistent render jobs for every required output.
What is new here
The technology is built around consistency, not novelty for its own sake.
Dual-layer identity lock
Spatial locks keep objects and people in the right place. Reference locks keep product sheets, spokesfaces, and room style consistent across renders.
Previs-first direction
Teams direct an eye-height walkthrough, hero spin, orbit, push-in, or hook move before asking a model to render. The video model receives intent, not vibes.
Model-ready render compiler
Pretzel translates the project master into model payloads: references, first frames, aspect ratio, duration, camera hints, and prompt context.
Variant matrix from one master
A single approved setup can fan out into 9:16, 1:1, and 16:9 cuts, localized markets, draft/final tiers, and hook variants without rebuilding the scene.
AI Director with guardrails
Natural-language direction proposes scene edits, but the structured state keeps changes inspectable, reversible, and constrained to the project's rules.
Model Context Protocol
An AI agent can direct the scene—not just write the prompt.
Pretzel MCP connects a compatible AI agent to the same editable 3D scene your team uses. The agent can arrange assets, block action, direct cameras, inspect the previs, and prepare a render plan without creating a second, hidden version of the work.
The scene remains inspectable and editable after the agent finishes. A paid render is not silently dispatched.
MCP scene workflowHuman-reviewed
- 01
Read the live scene, storyboard, and available capabilities.
- 02
Preview a typed plan for assets, blocking, cameras, and timing.
- 03
Apply the approved plan as one revision and one undo step.
- 04
Inspect previs frames and leave a render plan for human review.
Inspect before changing
Scene reads, camera paths, storyboard checks, and gray-box frames let the agent verify the work instead of guessing from prompt text.
The same scene as the team
MCP writes use Pretzel's typed scene actions, so the browser editor, AI Director, collaborators, and external agents stay on one source of truth.
Safe, reviewable writes
Scoped tokens, revision checks, dry-run previews, retry-safe writes, and atomic plans protect the scene from silent overwrites or duplicate edits.
Pretzel