Work with Vini, the studio copilot

Open Studio menu → Ask Vini in the project you want to work on. Vini’s conversation belongs to that project. Give the assistant a concrete outcome and the constraints that affect it.

Ask for an explanation or a change

An explanation can be as simple as:

Explain why this scene has both an Element reference and a first frame.
Then tell me which input is missing. Do not start a generation.

For a change, identify what should stay consistent:

Prepare two short scenes using the Element already connected to this project.
Keep the character and portrait format. Show me the proposed graph changes
before I apply them, and identify the next paid step.

These are example requests to the copilot, not MCP tool arguments or guaranteed generation outputs. For an external agent, use the MCP workflows.

Review a proposed graph edit

Vini can return a proposal card. Read the described additions and changes, then choose Apply when they match the task. The proposal is tied to the graph revision it inspected.

If the graph changed in the meantime, the card asks you to recompute. Request a fresh proposal against the current project. A stale proposal is not a reason to overwrite newer work.

After applying, inspect the actual nodes and connections. A graph edit can prepare a workflow without generating any media. Generated frames and clips still need their own runs and review.

Build workspace lore with Vini

Ask Vini to set up the lore of a series or a brand, and it asks the steps of the lore wizard one question at a time. It then offers a card with Open the wizard: the wizard opens with Vini’s answers, and you check them and press Write to the shared lore yourself. Vini proposes lore; it does not write it. For a ready document already in the shared lore, the card opens the wizard from a text, where Sort into steps shows its price before you press it. Opening the wizard is free.

Use step-by-step guidance

Guide me step by step turns on guidance for the current project. Vini names the next supported action and offers a button; each step needs your go-ahead. An offered run shows its cost or ceiling. Expanding a scene structure and generating a new image are different actions.

A custom graph may not have a recognized next step. In that case, ask about the specific node or use its controls. Guidance is not a guarantee that any arbitrary graph can be completed automatically.

For a complete route, follow your first video. The prepared free tutorial is an orientation to the interface; it is not an unlimited free generation pipeline.

Understand conversation cost and context

The panel shows the turn’s spending limit and, when available, the actual turn cost. The copilot’s language-model work and a media generation are separate costs. A turn that explains the project can still cost credit.

Long conversations can show context compacted. Important facts should also live in editable project material: scene text, Element definitions and project or workspace lore. Do not rely on a detail buried far back in chat as the sole project specification.

The interface language determines the panel’s labels. State the intended dialogue language in your brief as well; changing interface language does not translate an already generated clip.

Recover after an interrupted turn

Wait for the current turn to finish before submitting the same request again. If the outcome is unclear, inspect the conversation, current graph and run history. A missing reply alone does not establish that no edit or charge occurred.

When reporting a problem, include the project, the action, its visible error and whether a proposal was applied or a generation started. See runs and billing recovery. Protected system instructions and internal traces are not part of the ordinary copilot display.