LEARN

Kimi Code walkthrough

Start production in a Kimi Code local workspace, with ordinary Kimi chat treated separately.

← Back to assistants

Kimi Code Desktop; CLI alternative

Follow the product controls

Download a template first. The controls below follow official references; labels can change between versions. See the linked product guide if a control differs. Choose a template →

  1. 01

    Install and sign in

    Install Kimi Code Desktop from its official source, complete authorization, and check the model picker and your account’s available access.

  2. 02

    New session → Choose folder

    Click New session, click the folder name above the composer, then Choose folder… and select this video folder. Check the displayed workspace before sending.

  3. 03

    Send the brief and check file access

    Send the brief below and review the package report before planning. For CLI, run kimi in this project directory and use /login in the first session.

  4. 04

    Review changes and preview

    Inspect Changes, open File Preview or the returned browser URL, and check terminal output. Give timestamped feedback and request the exported video and project paths.

Starting brief for Kimi Code

Copy this, fill in the bracketed fields, and send it with the package path or readable guide.

Read the complete brief
I am producing this video in a Kimi Code local workspace containing the template and assets. Check the workspace path and actual package before helping me prepare the first version.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.

After the preview, finish these two steps

  1. Revise by timestamp. For example: shorten the title at 00:08 and use image two at 00:12. Reopen the full preview and check captions, picture, sound and actual duration.
  2. Approve export and save. Ask for the video, editable project and asset paths. Play the complete export and check aspect ratio, resolution and audio sync.
Preview and export checklist →

If you get stuck

There is no folder picker in Kimi chat

Open Kimi Code Desktop or install its CLI using the official guide. A chat attachment alone does not create a local production workspace.

The .motion file is rejected or unreadable?

Prefer the original package in the current project with an exact path. For attachments, wait for upload and request the actual filename and outer entries. Use the website’s ZIP-compatible download if available; do not wrap .motion in another ZIP.

Full file handoff instructions →

Official entries and references

References checked on 2026-10-31. Product homepages establish entry points; the content and handoff workflow is MotionGit guidance. Signed-in controls and availability vary by version, region and account. This is not certification of a full .motion export in every client.

← Back to the directory to choose another assistant