Agents In Use
What’s new todayLast update
11 use cases added today

How to cut dev videos with Claude Code and FFmpeg

ustype built a video-editing workflow with local whisper.cpp transcription, Claude Code selecting cuts and FFmpeg rendering. Their first 118-second raw take became 59.5 seconds. Silent rendering errors led them to inspect frames at cuts and measure audio levels.

Source published reddit.comAgent: Claudevia Claude Code
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Use [timestamped local transcript] to propose cuts that remove pauses and retakes from [developer-tool video]. Render with [FFmpeg settings] while preserving orientation and frame rates. Extract frames at each cut and measure audio levels. Flag visual or audio anomalies for human review before accepting the export.

Evidence at a glance

Sourced account
Source author
u/ustype
Original account
Read the source ↗
Published
Source link checked
Reported result
ustype reports cutting a first 118-second raw take to 59.5 seconds with Claude Code selecting transcript-based edits. They then added frame and audio checks after encountering silent rendering problems. The source does not quantify total time saved or independently verify export quality.
Human involvement
The author built the workflow, documented silent rendering failures and says they inspect frames and audio measurements before trusting a render. No quantified final review time or unattended publishing step is reported.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The author recorded a developer-tool video and transcribed it locally with whisper.cpp.
  2. Claude Code selected cuts from the transcript.
  3. FFmpeg rendered the selected segments into a shorter video.

Reddit author ustype was making short videos about developer tools and found editing much slower than recording. They built a workflow using local whisper.cpp transcription, Claude Code to select cuts from the transcript, and FFmpeg to render the result. The author reports that a first raw take of 118 seconds became a 59.5-second cut.

The difficult part was trusting the render. Their post describes phone footage whose reported dimensions differed from its decoded display dimensions because of rotation metadata. It also describes speed-change mistakes caused by the placement of FFmpeg timing arguments, audible pops at cut boundaries and judder from mismatched overlay frame rates. These are the author's findings from the workflow, not errors independently reproduced for this entry.

The author says they now extract frames at every cut and measure audio levels before trusting a render. They also collected the lessons in a HARD-RULES.md file in an open-source repository. The post does not provide a measured end-to-end editing-time saving or claim that Claude Code independently found every rendering problem.

Who it's for: developers editing spoken tool demonstrations who want AI-assisted cut selection while keeping explicit audiovisual checks. The concrete result is a completed shorter video and a working editing workflow with reported failure checks, rather than a guarantee that a successful FFmpeg exit means the output is correct.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/ustype

Frequently asked questions

Which part of the editing did Claude Code perform?

The author identifies Claude Code as selecting cuts from a locally generated transcript. FFmpeg rendered the video, and whisper.cpp supplied transcription. The source does not attribute every debugging step to Claude.

How did the author check the finished render?

They report extracting frames at every cut and measuring audio levels before trusting the render, after finding orientation, timing, cut-audio and overlay-frame-rate problems.

More details

Remaining steps

  1. The author investigated orientation, timing, audio-pop and overlay-frame-rate failures.
  2. They added frame extraction at cut boundaries and audio-level measurements before accepting renders.

About this account

Claude Code selected video cuts from the transcript within a workflow that used local transcription and FFmpeg rendering. The source does not establish that the agent performed all rendering diagnostics without human involvement.

Firsthand editing account by u/ustype: https://www.reddit.com/r/automation/comments/1x6mro5/i_got_laid_off_started_making_videos_and/. Full public RSS post and returned comments read on 16 October 2026; current body gate passed at 0.96. Durations and debugging findings are the author's, not independently reproduced. Suggested prompt by Agents In Use, not the author's original prompt.

Credit: u/ustype on Reddit

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude Code · FFmpeg · whisper.cpp · HARD-RULES.md

video editing · transcript cuts · render validation · local transcription

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.