Sign inStart creating

Vibe directing — talking to the Director

Conversational notes become structured, reversible operations on the graph, priced before they run.

Needs: ANTHROPIC_API_KEY for open-ended conversation. Without it this feature reports that it is unavailable rather than failing silently.

A persistent conversational Director sits over every project on the Director tab. You talk; it translates each note into structured operations on the Media Graph.

  • "Make the opening feel like a $50M sci-fi movie" → a twelve-shot sequence with a camera plan, pacing and style decisions, presented as a storyboard for approval before any video credits are spent.
  • "The ending should be sadder" → resolves to the final scene's shots, score and dialogue nodes, and regenerates only those. Persistent notes, localized edits — nothing else in the film moves.
  • "Maya should have a scar from Scene 13 onward" → a Character State Machine event, cascading to dependent later shots with confirmation.

Every instruction is recorded as a versioned graph mutation: auditable, reversible, branchable. That is the structural difference from chat-thread memory, and why this scales to features and seasons rather than five-minute clips.

Every instruction shows its estimated credit cost before executing — "regenerating the ending = 6 shots ≈ 240 credits in Cinema mode / 40 in Economy — proceed?".

Specialized crew agents — Screenwriter, Cinematographer, Composer, Editor and others — can be invoked individually or orchestrated silently by the Director.

Without ANTHROPIC_API_KEY the Director runs on a deterministic grammar: it handles the documented command patterns reliably but not open-ended conversation, and it says which mode it is in.

Did this answer your question?

Related

All help articlesAsk the community