nolanlabs

Blog · Agents

How to edit video with Claude Code

· Updated · 5 min read

A red rotary telephone on a small plain wooden table, standing alone on a pale salt flat.

Short answer

Connect Claude Code to something that can cut, and give it frames to look at, since Claude reads images, not video files. Use ffmpeg or an MCP server for batch jobs, Remotion or HyperFrames when the video is mostly graphics, and an agent on a real timeline, such as Resolve over MCP, Cardboard or our own nolanlabs, when someone will give notes on the cut.

On this page
  1. What can Claude Code actually see?
  2. The routes, compared
  3. One request, then one note
  4. Which one should you pick?
  5. Three habits that help on any route

The route you pick decides what comes back and what a small note costs.

What can Claude Code actually see?

Pictures, not video. Claude takes JPEG, PNG, GIF and WebP and uses only the first frame of an animation. So on every route, the agent works from a transcript, numbers and frames that something pulled for it. A cut it hasn’t looked at is a guess.

This command puts one second of frames on a single image, starting at 00:01:47:00 on a 24 fps cut, so a cut at 00:01:47:12 sits in the middle of what the agent reads:

ffmpeg -ss 00:01:47 -i cut.mp4 -frames:v 24 -vf "scale=320:-2,tile=8x3" -update 1 around-cut.jpg

We ran it on ffmpeg 8.1.1. Sampling one frame a second isn’t a substitute: a two-frame flash falls between the samples.

The routes, compared

As of November 2026, read from each project’s own pages. The fix in the third column is the same note on every route: this cut should come two frames earlier. We make nolanlabs, the last row, so weigh that row accordingly.

Route What comes back The two-frame fix What it costs you
ffmpeg scripts A rendered file and a script Change a number, render again No timeline. Frame-accurate cuts mean re-encoding: with stream copy, ffmpeg keeps the stretch back to the seek point before your frame
Remotion or HyperFrames A code project and a rendered file Change a number in the code, such as Remotion’s trimBefore or durationInFrames, and render again You work in a project of files, not a bin. Remotion needs a company license from 4 people up; HyperFrames is Apache 2.0 and needs Node 22
An MCP server: Kinocut, formerly mcp-video Files, plus a receipt of what ran Run the trim again, and whatever followed it No timeline to drag, by design: every flow must be “approvable in words”. Needs Python 3.11 and FFmpeg
Resolve, over its own MCP server, a community one or a skill A timeline in Resolve Trim it yourself Resolve Studio ($295 list, $236 on Blackmagic’s page on November 4), because external scripting and the MCP server are Studio features
Cardboard, an editor with an agent inside A timeline in Cardboard, each shot its own clip Trim it, or ask in chat A paid plan: usage credits pay for its agent, and exports to other editors start at Starter. Transcription and generation use the cloud
nolanlabs (ours), an editor with an agent inside, its own or yours A timeline in nolanlabs, with clips and handles Press V at the cut, nudge with , or . A new editor to learn, though its keys follow Resolve. Mac on Apple silicon or Windows 11 (64-bit). Its own agent runs on credits, 100 a month free; yours runs on its own plan. No generated footage, voices or roto by model

One request, then one note

Here’s a request worth trying on any of them:

Cut the two false starts from the first answer. Take about 8 seconds out of the second half, but leave the answer at 00:03:12 alone. End on her laugh. Show me the frames around every cut.

Every route can do this, because it’s mostly transcript work. ffmpeg gets a list of segments, Remotion gets a row of <Video> components, and Resolve gets a timeline built through its API. Check the transcript, though. Aident’s HyperFrames guide warns that transcription misreads names and acronyms, and that code “cannot decide whether a speaker looks awkward at a cut”.

Now the first note: the cut at 00:01:47:12 is two frames late, because she’s already moving. Two frames at 24 fps is 83 ms.

On a file route, that note is a turn and a render. The agent finds the segment, changes a number and renders, then you watch again. That’s fine once. By the tenth note you’re reviewing whole files and describing frames in words.

On a timeline route, you press a key and carry on. The agent isn’t involved, and the fix costs no tokens.

That’s the trade. File routes give you repeatability: the same script, the same result, across 200 clips. Timeline routes give you back the cut.

Which one should you pick?

  • The same job many times: ffmpeg or Kinocut. Kinocut wraps FFmpeg in typed tools, runs locally and is Apache 2.0, and states its primary job as captioned vertical clips an agent can re-run. Its own comparison says to use the raw shell when you already know the exact filtergraph. Reframing one cut for a phone is a different job, done by eye.
  • Mostly graphics: Remotion or HyperFrames. Every frame comes from code, so renders are exact, and HyperFrames asks for each frame rather than relying on playback. Remotion’s Claude Code setup is npx create-video --yes --blank my-video, then npx remotion skills add.
  • Already in Resolve: stay there. Studio 21.1, from September 2026, has its own MCP server for Claude Code and Codex. The community server offers 37 grouped tools or 390 single ones, and its grouped server archives a timeline before changing it. Its README calls the output “a starting point you cut, not a finished cut”. The skills are instructions rather than code, aimed at first passes on vlogs and classes, and licensed CC BY-NC 4.0.
  • You need generated shots or a cloned voice: Cardboard. It generates video and music, finds B-roll on the web, and sends the timeline to Premiere, Final Cut or Resolve. Its Mac app works with Claude Code and Codex, and any agent can drive it through its CLI or MCP server.
  • You want an agent on a timeline you also drag: nolanlabs. It’s ours. It comes with Nolan Edit, an agent that needs only a nolanlabs account, or it runs yours: Claude Code is a full session on your sign-in, with your CLAUDE.md and skills, plus eight editor tools. Either way its edits go on the timeline as one step you can undo, and it looks at the frames around its cuts. Those frames go to the agent you chose, with Nolan Edit through nolanlabs.io to the company that runs its model; your footage stays on your disk. It won’t generate anything, so a shot you never got has to come from elsewhere. Your first cut takes you through it.

Three habits that help on any route

  1. Speak in frames. State the frame rate and give timecode with frames. “Around two minutes” and 00:02:03:14 are different instructions.
  2. Write the looking rule down. In CLAUDE.md: after any cut, make a strip of frames around it and read it before calling the cut done.
  3. Work on a copy, then watch it through. A strip shows a bad frame. Only playback at full speed shows a bad rhythm, and that call stays yours. If the note is about pace, this order of operations helps.

Blog

Keep reading.

Every piece

Written by the people who make nolanlabs, a video editor that edits with you.

Download for Mac Download for Windows Download

Free to start, on Mac and Windows.