Keep a video project coherent between assistants

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.

Kleo production guides · English · Editorial review 2026-09-23

Planning sequence: Plan, then Approve, then Render, then Save.

A practical method

  1. Export a clean handoff note without private account credentials.
  2. Include whether a render has already been submitted.
  3. Ask the receiving assistant to summarize the state before taking action.

An example brief to adapt

Written illustration of this method; not a report of a rendered film or a customer result.

Continue this project from the supplied handoff. The treatment is approved, but no render is authorized yet. Repeat the chosen product, duration, aspect ratio, look and narration language. Ask for missing information rather than inferring it from an older chat.

Review before moving on

  • Is the job state explicit?
  • Are approved decisions preserved?
  • Have private keys been excluded?

Record a concrete observation beside each check: a line in the treatment, a source passage or a timestamp in the downloaded film. If you cannot inspect an item yet, leave it open. A request in a brief is an intention; the result is what must be reviewed.

Download this guide’s editable text worksheet

What to avoid

Switching assistants does not justify creating the same job again. Check the existing job identifier and status before authorizing a new request.

Sources and scope

The method and fictional brief are original editorial guidance for planning and review. They do not establish a measured performance gain or guarantee a particular render. Product statements follow Kleo’s public pages, checked on 2026-09-23; official platform guidance is linked where relevant.

  • Kleo FAQ — Product capabilities and limitations; reconfirm before production.
  • Kleo pricing — Current starter offer, product conditions and quoted credit costs.
  • MCP: architecture overview — Background on the host, client and server model; not a guarantee that conversation history moves between hosts.

See the published Kleo examples to inspect actual showcased work. Example films may reflect a different production setup; check the current offer for your own job.

Continue your production plan

Copied