Use the native Video Editor node as a durable editable composition inside a flow, route layers/audio/compositions/mattes/design systems into it, then render or reuse its outputs.
Where: Flowgen → Add node → Compose → Video Editor.
Key ideas
- Video Editor is a native composition node: The node formerly called Video Compose now hosts the native timeline/compositor. It is not the legacy Konva quick editor and not the separate Agentic Video & Motion Gen iframe editor.
- Editable and rendered outputs are distinct: composition_out carries the native editable composition to Video Render or Image Sequence. compose_out is the rendered-composition compatibility output used by composition consumers.
- Graph input and local draft can conflict: composition_in can replace the editable document. If upstream changes while a local editor draft is open, the node stops and asks whether to preserve/save or discard the draft instead of overwriting silently.
Steps
- Add Video Editor and wire visual layers to layer_in, audio to audio_in, an existing native composition to composition_in, an optional matte to matte_in, and a design system to design_system_in.
- If using matte_in, choose the Matte target visual layer on the card.
- Open video editor and author the edit/composite in the native same-window surface.
- When the card reports transient media, use Save media to project before reload, collaboration, or handoff.
- If an upstream composition changes during local edits, review the warning. Save/resolve the draft or choose Discard local draft and use upstream only when the upstream revision should win.
- Connect composition_out to Video Render composition_in or Image Sequence composition_in for delivery. Use compose_out only where a rendered-composition input is expected.
- For MCP, call flowgen_open_compositor, inspect returned live schemas, invoke read_compositor before a revision-safe write, then flowgen_close_compositor.
- Check the first-frame preview, layer count, dimensions/duration, warnings, render output, and reopenability after saving the flow.
Sockets
- layer_in — visual/composition layers
- audio_in — audio
- composition_in — editable native composition
- matte_in — mask applied to the chosen Matte target
- design_system_in — connected project design tokens/system
- compose_out — rendered-composition compatibility output
- composition_out — editable native composition
Card and editor surface
- First-frame preview, native badge, layer count, width × height, duration
- Matte target picker
- Migration/input/persistence/collaboration warnings
- Save media to project
- Open video editor
- Embedded project menu for close, JSON import/export, backup/restore, and theme
External MCP lifecycle
- flowgen_open_compositor waits for the same-window native executors
- flowgen_invoke_compositor_tool accepts exact tool names and JSON schemas returned by open
- flowgen_get_open_compositor verifies node/document identity
- flowgen_close_compositor closes the native surface
- Do not use flowgen_open_node_editor or f0_invoke surface=document for videoCompose
Tips
- Route the editable composition to Render so later native edits remain part of the flow.
- Resolve upstream/local conflicts before saving transient media.
Limitations and important notes
- Video Editor itself is an editor, not a generation node; paid media operations inside AI still require their own authorization.
- Only one same-window compositor surface is exposed to MCP at a time.
- A card preview is the first frame, not proof of full playback.
Troubleshooting
MCP says document surface is unavailable.
Video Editor is not an iframe. Use flowgen_open_compositor and flowgen_invoke_compositor_tool.
The node refuses an upstream update.
A local draft diverged. Decide which revision should win and use the card’s conflict action deliberately.
A shared flow loses imported media after reload.
Open the card and use Save media to project until the transient-media warning clears.