Use Claude Motion with ChatGPT and Codex (2026)

Decide where each part of the work happens

Use a conversation to establish the audience, factual claims, scene order, and final call to action. Move the approved brief and assets into the local project before implementation. A code block produced in an ordinary chat is not evidence that a local file changed or a render ran. In a connected coding session, inspect the available directory and tools first. Ask the agent to name the project path and describe the existing scripts so you know it is working in the intended environment.

Install Codex and establish a clean baseline

Follow the current official Codex CLI instructions. The npm installation option and launch command appear below; sign in using an available authentication method. Separately obtain the whaleyxbt repository, install its dependencies, and build the unmodified example as described in our requirements guide. Confirm out/effort.mp4 exists and plays. Installing Codex does not supply Python, FFmpeg, or the repository itself. This is a documentation-based procedure, not a claim that every host or account configuration has been tested.

npm install -g @openai/codex
cd claude-motion
codex

Make the repository instructions explicit

Start Codex in the repository and ask it to read AGENTS.md and the relevant files in .claude/skills/. A directory named for another agent can contain useful project instructions, but do not assume automatic skill discovery works identically across tools. Request a summary of the storyboard, timing, sound, and review conventions before editing. Supply exact source text and prohibit invented metrics. For Claude Motion Skills on this website, follow the separate getting-started flow and install its own skill; it uses templates and HyperFrames rather than this Remotion project.

Iterate with artifacts you can inspect

Ask for one short scene first, then a draft video and timestamped contact sheet. The repository’s commands below produce a draft and inspection images after dependencies are ready. Inspect typography, clipping, and factual accuracy, then play the video for motion and audio. Request a single focused revision, such as extending a reading hold, rather than changing every design variable at once. Keep a checkpoint before each accepted revision. Re-run the relevant export after edits; an old MP4 does not prove the new source works.

npm run draft
npm run sheet -- --video out/draft.mp4

Keep usage and delivery claims precise

Codex account usage, API billing when applicable, and this site’s subscription are separate cost categories. Consult official current pricing instead of converting a subscription into an assumed unlimited video allowance. Local rendering also consumes your computer’s resources. Deliver the actual MP4, source files, and a list of checks performed. Do not describe generated code as a finished export or infer that this site’s optional audio service is open. A local project can be inspectable even when a later account-dependent feature is unavailable.