Codex local project / CLI
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
Choose Codex and the local project
Select Codex in the desktop product selector and open or choose this local project folder. Add the downloaded package and assets and check the task directory.
- 02
CLI alternative
Install the CLI using its official guide, run codex from this video directory, and sign in when prompted. Use either desktop or CLI; cloud tasks need their own files and environment.
- 03
Send the exact path and brief
Ask it to verify the package, entry and tools using the brief below. After planning, switch to task execution and handle tool requests for the actual operation.
- 04
Open the real preview
Open the preview path or browser URL. If it fails, ask it to verify file existence and server status. Review picture and sound before requesting video export and editable sources.
Starting brief for Codex
Copy this, fill in the bracketed fields, and send it with the package path or readable guide.
Read the complete brief
I am using a local Codex production project. Check the working directory and .motion path, read the real package, identify missing inputs and runtime tools, and provide an opening link when the preview is ready. 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
The path looks right but is not accessible
Ask for the current working directory and visible files. Check for a cloud environment or different project, then supply the file in the actual workspace or choose the correct local folder.
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.