Ce document technique est disponible en anglais. L'interface suit la langue que vous avez sélectionnée.
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
- Claude Code and Codex: connect the local project and follow the template instructions.
- Cursor: open this video folder and use the Agent to read the package and run a preview.
- Doubao and DeepSeek: desktop app only; switch to work mode, then choose this video folder.
- TRAE: open the project and check file and terminal access in an execution-capable mode.
- 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.
- Grok Build: start Grok Build in the project directory; use ordinary Grok chat to prepare content, then hand off.
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.
Web or mobile only
Web chat and mobile apps cannot see a local project folder. Use them to draft copy, shots and an asset list, then preview and export with one of the desktop tools above. A coding tool using a DeepSeek model must supply its own file and rendering capabilities. Uploads and separate AI video generation are not 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.