A clear workflow records decisions before a render and checks the result afterward. Kleo connects to an assistant through MCP, while the assistant presents the treatment, tools and result. Keep the approved creative version separate from the job identifier and quote. The guides in this section address different operational decisions, from choosing an animatic to archiving the final MP4. Product availability and quoted costs should be confirmed at the time of production.
A clear workflow records decisions before a render and checks the result afterward. Kleo connects to an assistant through MCP, while the assistant presents the treatment, tools and result. Keep the approved creative version separate from the job identifier and quote. The guides in this section address different operational decisions, from choosing an animatic to archiving the final MP4. Product availability and quoted costs should be confirmed at the time of production.
Kleo presents two products: a film with generated moving footage and an animatic using drawn frames with camera movement. Choose according to what you need to assess; an animatic is useful for story review but does not prove the final footage will behave identically.
Moving a project between assistants requires a concise production record: the approved brief, treatment, decisions and job status. Conversation context alone may not travel with the connection.
A video conversation should distinguish discussing a concept from authorizing a paid job. Ask the assistant to show the treatment and quote, then give an explicit instruction when you are ready to proceed.
A submitted render has a job identifier and status. Use that record to follow progress instead of repeating the original creation request when the assistant appears slow or the conversation is interrupted.
When a render fails, preserve the job identifier, reported error and approved settings before retrying. The cause may require a product-side fix; changing several creative instructions at once makes diagnosis harder.
Credit planning should include the intended product, duration and possible additional production steps. Use Kleo's current pricing page and the quote shown before submission as the source of truth, especially if the project has changed since planning.
A longer explainer needs a progression of questions rather than an extended introduction. Kleo's current public pages describe films up to five minutes; check the live limits before planning a deliverable around a longer running time.
Adapting a longer video idea means selecting one self-contained question, not merely accelerating the narration or cutting every paragraph in half. Write a new opening and ending for the smaller scope.
A product demonstration must show the actual interface when viewers need to learn where to click or assess a specific feature. Generated illustrative scenes cannot verify what a real application looks like or does.
An editor handoff should explain what is approved, what remains to be added and which details must not change. The MP4 alone does not communicate the intended wording, source credits or publication requirements.
A durable project archive includes the final file and the information needed to understand its origin. Kleo's public site says download links last seven days, so save the deliverable rather than relying on the chat link as permanent storage.
Browse all production topics or read the complete Kleo workflow. Choose guides by the decision at hand, then keep your approved choices with the project.