Video editing for AI coding agents

Let Claude Code, Cursor or Codex edit your videos

Your coding agent already knows how to run commands, read the results, and fix its own mistakes. Give it the framecompose command and it builds a real video for you: one you can watch, open in a proper editor, and fix by hand before anything is final.

Maintained by the FrameCompose product team · Last reviewed 30 October 2026

FrameCompose multi-track timeline with scenes, captions, voiceover, and music assembled by an AI agent
What your agent builds: a normal multi-track FrameCompose project that updates live in the browser as each command runs.

Your agent builds a real, editable timeline, not a flat MP4 or a script to babysit.

Watch every edit land in the open browser editor and fix anything by hand.

Small changes take about a second and cost no credits. No rebuild, no re-upload.

A free dry run shows the plan and the credit estimate before anything paid runs.

Paste this prompt into your agent

Install the CLI and sign in once (npm install -g framecompose, then framecompose login). Then copy this into Claude Code, Cursor, Codex, or the agent you already use, and change the parts in square brackets.

The prompt makes the agent check the cost first, send you the editor link, and wait for your go-ahead before it renders. It also tells the agent never to ask for your API key in the chat: you type the key into your own terminal, where it stays.

A ready-made prompt for your agent

Works as written. Add your own style notes, a voice you like, or a target length.

Use the framecompose CLI to make a finished video from the clips in ./clips.

The video: a [45-second] vertical 9:16 video for [who will watch it]. Lead with the strongest moment, keep the pace tight, add word-timed captions, background music that dips under speech, and a soft whoosh at the main cuts.

How to work:
1. Run framecompose whoami --json. If I am not signed in, stop and tell me to run framecompose login myself. Never ask me to paste my API key into this chat.
2. Look up valid names with framecompose transitions, motions, caption-styles, voices and sfx search before you write anything.
3. Write recipe.json (schema "framecompose.recipe/v1") and run framecompose build recipe.json --dry-run --json. Show me the length, the warnings and the credit estimate.
4. Build with --max-credits set to that estimate, send me the editor link, and stop.
5. For changes, inspect first, then use edit, patch, split, reorder or undo. Never rebuild the whole project for a small fix.
6. When I say the cut is right, render with framecompose render <projectId> --resolution 1080 --wait --out final.mp4 --json.

A real timeline beats a script that renders once

Ask a coding agent to edit video the usual way and it writes a script: a long list of render commands that spits out one flat MP4. If the second clip runs long, a caption sits in the wrong place, or the music drowns the voice, the whole script runs again and you get another flat file to check.

FrameCompose gives the agent a better target. One command builds a real project with separate scenes on a multi-track timeline, word-timed captions, voiceover, music that dips under speech, transitions, effects, and sound effects, each piece still editable. The agent does the assembly; you open the same project in the browser and judge it as a video, not as code.

Build the project, not just the file

The dry run is free. Re-running the build carries on in the same project, so nothing uploads twice.

framecompose build recipe.json --dry-run --json
framecompose build recipe.json --max-credits 40 --live --json

Watch it work, then fix the one thing that is wrong

Open the project in the FrameCompose editor and leave it open. As your agent runs commands, the timeline updates by itself within about two seconds, so you watch the cut take shape: clip order, captions, music, end card. When something looks off, say so in plain words and let the agent fix that one thing.

Those fixes are the fast part. Trim a scene, change a transition, restyle the captions, lower the music, split a clip, or reorder the story in about a second each, free, and every change can be undone.

Small fixes, in place, in about a second

Each command is one undo step.

framecompose inspect <projectId> --json
framecompose edit <projectId> --scene 1 --trim-end 4.5 --transition CROSSFADE --json
framecompose edit <projectId> --captions --animation pop --highlight on --json
framecompose undo <projectId> --json

Hand the agent the slow, fiddly jobs

The jobs that eat an afternoon are the ones agents are good at. FrameCompose hands them the tools directly: find the strongest highlights in a long recording, cut the silence without chopping the music, keep the speaker in frame in a vertical crop, score the opening hook, find the beats in the soundtrack, and cut a montage on them.

These analysis tools cost no credits, and each one can preview its plan before anything is applied. The agent does the hunting and the first assembly. You make the calls that make the video good: what leads, what goes, and when it is done.

Find the moments, cut on the beat

Applied results are normal timeline edits you can undo or polish in the browser.

framecompose highlights <projectId> --apply --top 3 --json
framecompose cut-silence <projectId> --dry-run --json
framecompose auto-reframe <projectId> --json
framecompose montage <projectId> --style punchy --duration 30 --sfx --json

You approve the spend and the final cut

Nothing paid runs blind. The free dry run shows recipe problems, warnings, the expected length, and the credit estimate before a credit moves. Cap the build with --max-credits and check the result in the editor before anyone renders.

When you approve the cut, the agent renders on the server and downloads the MP4, at no credit cost right now with Pro or any credit pack. Or export free from the browser editor on any plan. The Starter Pack is $5.99 once for 500 credits that never expire, and no plan adds a watermark.

Checkpoint the approved cut, then render once

Server renders need Pro or any credit pack. On the free plan, export from the browser editor.

framecompose checkpoint save <projectId> approved-cut --json
framecompose render <projectId> --resolution 1080 --wait --out final.mp4 --json

Frequently asked questions

A few quick answers before you jump in.

Which AI coding agents can use FrameCompose?

Any AI coding agent that can run terminal commands can run framecompose, including Claude Code, Cursor, OpenAI Codex, Gemini CLI, and GitHub Copilot in agent mode. It is the same command you would run yourself. Every command accepts --json for one structured reply and uses fixed exit codes, so the agent can read the result, correct a bad field, and keep working.

I do not write code. Can I still use this?

Yes. Install the CLI once with npm install -g framecompose, create a free API key on the API keys page, and run framecompose login. After that, paste the ready-made prompt from this page into your agent, watch the video appear in the browser editor, and ask for changes in your own words. You stay the editor; the agent runs the commands.

Why not just let my agent write ffmpeg commands?

A script like that produces one flat MP4. Every fix means editing commands and rendering the whole video again, and captions, music ducking, transitions, and timing all have to be rebuilt by hand each time. FrameCompose builds a real multi-track project instead: the agent makes one-second edits in place, you can open the timeline and fix anything yourself, and the final render happens once, when you approve the cut.

Is it free to let an agent edit my videos?

The CLI and API keys are free on every plan. Dry runs, timeline edits, and the analysis tools cost no credits. AI narration costs credits and is estimated in the free dry run before anything is spent. Server renders currently cost no credits with Pro or any credit pack (packs from $5.99 once), and exporting from the browser editor is free on every plan with no watermark.

What happens if the agent makes a bad edit?

Every edit is one undo step, and named checkpoints let you pin a version before a bigger change and return to it later. The project is also a normal FrameCompose project in your browser, so you can open the timeline, fix the edit by hand, and let the agent carry on from there. Nothing is final until you approve the render.