Claude desktop · Code tab; 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 →
- 01
Open the Code tab
Sign in to Claude desktop and choose Code. Select a local execution environment below the composer; a cloud repository session does not automatically see your Downloads folder.
- 02
Choose this project folder
Use the project-folder control beside the environment selector, or the folder settings of a saved environment. For CLI, run claude from this project directory.
- 03
Read the entry and approve a plan
Provide the package path and brief. Use Plan to review the approach, then switch to an editing/execution mode for production and handle tool requests as prompted.
- 04
Open the preview and revise
In a local session, open the returned HTML or video path, or the preview server card. Review picture and sound, revise in the same session, and approve export.
Starting brief for Claude Code
Copy this, fill in the bracketed fields, and send it with the package path or readable guide.
Read the complete brief
I am working in a local Claude Code session. Confirm this project directory and the actual .motion path, read the package entry point, and prepare a reviewable plan before preview production. 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
- 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.
- 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.
If you get stuck
Plan does not start production
After approving the plan, switch to an execution mode and ask for a real preview and instructions for opening it.
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.