Use your own Claude Code or Codex account. Create a local project folder and collect a script, product notes or key numbers. State who will watch, the main message, target length and format.
Example prompt
Use the notes in launch-notes.md. Plan a 15-second, 16:9 product explainer for first-time visitors. The goal is to explain three benefits. Keep every number and source note unchanged. Show the storyboard before building.
Step 0 2
Install once and connect your account
Sign in, paste the connection request into your agent and approve the matching browser code.
Editorial costs 0 platform credits on every plan. Other styles require Pro or Studio; a standard paid task costs 1,000 credits after confirmation.
Example prompt
Recommend a style for this brief. Before task activation, show the style, version and exact credit cost. Wait for my confirmation. Use the same delivery receipt for retries.
Step 0 4
Build and inspect the local preview
After task activation, your agent creates the source project locally and opens a browser preview. Check the wording, numbers, reading speed and representative frames. Materials and source files stay in the project you control.
Example prompt
Build the confirmed storyboard in this folder. Open the local browser preview. Check text overflow, missing assets and reading time before showing it to me.
Step 0 5
Add sound in the same local project
Add original music and effects locally. Generate narration through the connected Skill without a Google key, or import your own audio. Review the script and listen before use. Local audio edits and exports use no platform credits.
Example prompt
Add original background music, voiceover from my approved script and subtle transition effects. Use my audio files or a speech service I approve. Do not default to a system voice. Keep speech complete, lower music under the voice and verify audio in the exported MP4. Do not use paid external services without my approval.
Step 0 6
Revise in the same conversation
Name the scene and the exact change. Keep working in the existing project. Local edits and renders use no platform credits; a new paid task or direction requires a new quote.
Example prompt
In scene 2, shorten the headline to six words and hold it for one extra second. Keep scene 1, the numbers and the existing style unchanged. Update the same project and show the preview again.
Step 0 7
Render, check and keep your source
Ask your agent to render locally and return both the MP4 and editable source folder. The installer checks resolution and duration with ffprobe. Inspect fonts and representative frames yourself before sharing. Node.js 22+, FFmpeg and your own agent access are required.
Example prompt
Render this project locally to MP4. Check the actual file’s resolution and duration, inspect the opening and closing frames, and give me the editable source folder together with the video. Report any failed check.
Make your first local video
A useful first step today.
Connect your account once and give your own agent the material for a short video.
Review the storyboard and exact task quote. Confirm only when the direction and cost are clear.
Your agent prepares the resources and creates the project. Check the local preview and request changes in the same conversation.
Use the installed Skill to apply your content, run the layout checker and open a local preview. After review, render an MP4 locally and verify its duration and dimensions. Keep your editable project.
If rendering fails, keep your source and inspect the error with your agent. Recover the same pack using its saved delivery receipt without another credit charge. Keep local copies of your material and project.
How to use the toolkit — from brief to local export | claudemotion.tv