Claude Motion requirements: prepare a working environment (2026)

Separate access from the rendering environment

For the open-source repository, you need a local folder and a coding agent if you want AI-assisted editing. For Claude Motion Skills, new compositions require an active site subscription plus your own Claude Code or Codex access. Paying for one service does not grant access to the other. A browser login also does not install command-line tools. Record which account controls content generation, which controls templates, and which machine will render the video.

Install only the dependencies your route needs

The repository README asks for Node 20 or newer, Python 3, and FFmpeg. Choose a currently supported Node LTS that satisfies that minimum rather than deliberately installing an obsolete major version. This site’s CLI requires Node 22 or newer and uses local Chrome, FFmpeg, and ffprobe for rendering. Python belongs to the repository’s sound workflow, not to this site’s basic template requirements. Use official download documentation and the build-provider links published by FFmpeg; check your operating system and CPU architecture.

Prepare a clean, writable workspace

Create a dedicated folder outside a system directory and keep source material in a clearly named subfolder. Reserve space for dependencies, browser downloads, temporary frames, audio, and final exports; there is no verified universal disk or memory minimum for every scene. Start with a short example before committing to a long production. Put approved text, logos, font licenses, and aspect-ratio requirements in the brief. Missing assets and unclear copy are project blockers even when every tool is installed.

Check tools from the terminal you will actually use

Run the version checks below in the same terminal environment that will build the repository. On Windows, a tool installed in PowerShell may not exist inside WSL; check inside the chosen environment. Each command should print a version rather than “command not found.” For this site, also run cm-skills doctor after setup and inspect its local tools and account result. Diagnose the first missing executable before changing project code; repeatedly reinstalling JavaScript packages will not fix a missing Python or FFmpeg binary.

node --version
npm --version
python3 --version
ffmpeg -version
ffprobe -version
git --version

Define readiness with a small successful output

For the repository, npm install followed by npm run build should produce the documented example at out/effort.mp4. Read the first failed stage if it stops: sound, silent render, or mux. Open the final file and verify picture and sound. For this site, follow getting-started and confirm a template preview before attempting local export. These are documentation-based acceptance criteria, not a claim that we tested your machine. Optional audio must be confirmed against current service availability; this site’s audio is not currently verified as available.