Use the Storyboard node for existing-screen assembly or the desktop website motion agent, then inspect and revise the actual saved reel.
Where: Flowgen node search → Storyboard; its linked Designer opens the board or reel editor.
Key ideas
- Two original paths: The reelStoryboard node can assemble existing screens deterministically without a model round. Its website motion-agent path uses the wired Brief, desktop capture/session capability and paid model rounds. There is no separate newReel node type.
- Use the matching saved format: Beat storyboards use read_storyboard and beat editing helpers, including Designer page edits. Motion reels use read_motion_reel and scene, voice-line, lock, revision and kept-version helpers. A still board establishes direction; watch current moving output before claiming motion quality.
- Compatible model routing: The current website motion tools use the Claude transport. Auto uses the account/JEV storyboard policy restricted to image-capable Claude candidates; incompatible explicit pins are refused before dispatch. Concept/director use the strong model; film/revision/questions normally use the configured Haiku delegate unless delegation is off.
- Run Log explains the agent run: When log entries exist, the Storyboard card shows an expandable Agent log. It records the run by round and phase, with tool calls/results, refusals, retries, stops and director notes. Its summary can show checks that sent the reel back and whether they remained, tool errors, rounds by phase, common motion moves and director notes; the full JSON log may be linked when available.
Steps
- Connect the prepared Brief and the actual screens or website source.
- Choose deterministic screen assembly or the compatible website motion path. Use the desktop app for site filming/capture.
- New Briefs default to board review. Inspect the current still board, then use Approve on the Storyboard card/sidebar or its linked Reel editor before filming; skip board review only when you choose to. Existing saved settings are retained. Review the moving reel’s timing, words, interactions and requested sound.
- Read the saved format before editing. Make focused changes in the owning node/editor; inspect its actual busy/progress, resulting scenes and errors before claiming completion. A content edit can return approval to draft, so re-read the current state.
- To troubleshoot a run, expand Agent log on the Storyboard card. Review checks that fired versus checks still standing, tool errors, rounds by phase, moves and director notes; select Failures only to narrow the event list. Earlier entries may be omitted from the node copy; open the full JSON log if its link is present.
- Keep the accepted version and approve the filmed reel in its native card/editor when ready for Produce. Stop ends an active run or approval wait.
Asynchronous tools
revise_motion_reel and ask_motion_reel return a started acknowledgement. Follow read_motion_reel until the original run finishes or fails; lastAnswer holds the question result. The acknowledgement is not the finished reel or answer. ask_motion_reel costs a model round and saves an answer, so it is not a read-only Ask/Plan tool.
Limitations and important notes
- Browser/server discovery does not supply desktop capture or make this node server-executable.
- MCP read/edit helpers do not provide a separate storyboard-approval command; approval is a human action on the current native card or editor. Do not fake it by editing node properties.
- Edits made in the Reel Storyboard’s own “Edit in Video Editor” are recorded and replayed onto later Storyboard builds by stable layer/composition IDs while those targets remain. If a target is removed, the edit is reported stale. This guarantee does not extend to an independent Video Editor/composition copy or the separate Produce output, which are outside the Storyboard revision owner.