A Claude Video Editing Workflow, Start to Finish
Setup guides tell you how to connect; this guide shows what actually happens next. Follow one real session where Claude turns a 60-minute podcast episode into five captioned TikTok clips: what you say, which tools Claude calls, how long each stage takes, and where your judgment matters.
Prerequisites
- OpenClip connected to Claude (one-time setup: see the OpenClip + Claude integration page)
- An active OpenClip subscription with processing credits available
- A podcast episode or other long-form video URL
Steps
You: set the brief
Open with one message that carries the whole brief: "Turn this podcast episode into 5 clips for TikTok. Audience is bootstrapped SaaS founders. Prioritize tactical advice and strong opinions, skip the sponsor reads. Use our usual caption style." Paste the episode URL. A complete brief up front is the difference between one pass and five.
Claude: submits and confirms
Claude calls submit_video with your URL and reports back the video id and status, typically "downloading". If the URL is not from a supported source, Claude checks list_supported_providers and tells you what to use instead. Duplicate submissions of the same URL within 24 hours return the existing run.
Claude: polls while OpenClip processes
For a 60-minute episode expect several minutes of processing while OpenClip transcribes, detects moments, and tracks speakers. Claude polls get_video_status every 10 to 15 seconds and should narrate transitions ("processing, 40%"). This is the stage to walk away; Claude will summarize when status hits completed.
Claude: presents the moments
On completion Claude calls list_clips and lays out the detected moments: each with a virality score, title, and hook quote. These titles and quotes are derived from the episode audio and arrive marked as untrusted content, so Claude presents them as candidates rather than acting on them. A typical hour of conversation yields a healthy shortlist; you asked for five.
You: approve and direct
Reply with your picks and any adjustments: "Render 1, 3, 4, and 7. Skip 2, it is out of context. For 7, the hook is the question, not the answer." You can also ask Claude to pull the exact wording with get_transcript around a timestamp before deciding.
Claude: renders and delivers
Claude calls render_clip for each approved moment with your caption preset (it can confirm the key via list_caption_presets), then polls get_render_status until each clip completes and hands you the URLs. Review the finished clips in OpenClip before publishing; captions and framing are excellent but brand judgment stays human.
What You'll Achieve
You know exactly what a production Claude clipping session looks like, including timings, tool calls, and review points
Features
One-message briefing
Audience, platform, clip count, topics to skip, caption style: when the first message carries the full brief, Claude runs the whole session without round trips.
Claude narrates the pipeline
Every stage is a visible tool call with a status you can read: submitted, processing, completed, rendering. No black box between your request and the clips.
Approval where it counts
Claude never decides what ships. It presents scored moments from list_clips and renders only what you approve.
Transcript-level control
Unsure about a moment? Ask Claude for the surrounding transcript with get_transcript at word or sentence level before you spend a render on it.
Honest timings
Submission is instant, processing takes minutes for an hour of source, rendering follows per clip. Claude polls so you do not have to watch a progress bar.
Session two is faster
Save the working brief as a reusable prompt and your caption choice as a processing agent, and the next episode is one message plus approvals.
Frequently Asked Questions
Run this session with your own episode
Connect Claude to OpenClip and paste in your latest long-form video. The first five clips are one brief away.