Choose an assistant and hand off production
Check the specific client before choosing a workflow. A model generates and reasons; tools provide file access and template execution. Web, mobile, desktop, IDE and CLI clients may have different capabilities.
Two starting routes
| Environment | Workflow | Before proceeding |
|---|---|---|
| Local files and command execution | Inspect the package in a separate folder, then follow its production instructions | Verify dependencies and generate a real preview |
| Chat or unconfirmed execution tools | Prepare copy, shots, parameters and an asset list, then hand off | A production tool receives the package and inputs and verifies the environment |
Project tools
- TRAE: open the project and check file and terminal access in an execution-capable mode.
- CodeBuddy: use an IDE or Code client with project tools; read the instructions and check dependencies.
- WorkBuddy: check file access and required commands in the installed desktop version.
- Kimi Code: use a desktop or CLI project session; assess ordinary Kimi chat separately.
- Qwen Code: use the coding tool for local production; Qwen chat can prepare content.
- Claude Code and Codex: connect the local project and follow the template instructions.
These are starting workflows, not certification of every tool, operating system and template combination. Official product capabilities and a tested .motion export are different evidence. Features vary by version, region and account.
Content preparation
Doubao, DeepSeek, Zhipu Qingyan, Tencent Yuanbao, Wenxin / Wenxiaoyan, iFlytek Spark, and ordinary Kimi or Qwen chat can start with instructions, copy and asset planning. If the current client has project execution tools, check them before using the local route. A coding tool using DeepSeek or GLM must supply its own file and rendering capabilities.
Use the assistant directory for individual guidance and official links. Chat, uploads and separate AI video generation are not proof of a .motion render.
Ask three questions first
- Can you read my actual package and identify its version and production entry point?
- Can you execute its documented workflow? Which tools, fonts and assets are missing?
- Can you deliver a preview and a final video I can open, rather than only code or descriptions?
Resolve missing requirements or prepare a handoff.
Handoff checklist
Keep the original package, brief, final script, assets, asset mapping, approved plan, current project, latest preview and revision notes. Ask the next tool to restate the project status before continuing. A chat message saying “finished” cannot restore a project.
Keep keys, accounts and private assets in controlled folders. Remove secrets and personal download links from public support materials. Model subscriptions, API credits, website credits and local runtime requirements are separate conditions.
Official references
Checked on 2026-10-31. Complete .motion export still requires verification in each client.