<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: shansjl</title>
    <description>The latest articles on DEV Community by shansjl (@shansjl).</description>
    <link>https://dev.to/shansjl</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4235586%2F0977e859-5982-4a79-9026-ba4dd4cda2ec.jpg</url>
      <title>DEV Community: shansjl</title>
      <link>https://dev.to/shansjl</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shansjl"/>
    <language>en</language>
    <item>
      <title>One edit, three aspect ratios: production versions as sequences, not file copies</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Sun, 15 Nov 2026 14:50:18 +0000</pubDate>
      <link>https://dev.to/shansjl/one-edit-three-aspect-ratios-production-versions-as-sequences-not-file-copies-j</link>
      <guid>https://dev.to/shansjl/one-edit-three-aspect-ratios-production-versions-as-sequences-not-file-copies-j</guid>
      <description>&lt;p&gt;&lt;em&gt;I build &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an open-source (MIT) local video editor that Claude Code / Codex can drive over MCP. This post is about one feature and its limits.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A request that keeps coming up in editing threads this month is some version of:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Adapting finished edits from 16:9 to 9:16, 1:1, 4:5, etc. Reframing shots and repositioning graphics for different aspect ratios."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And from a Dev.to post on cutting Shorts from long talks (&lt;a href="https://dev.to/kelvaro/build-a-local-python-pipeline-that-turns-a-long-talk-into-six-916-shorts-mec"&gt;kelvaro&lt;/a&gt;):&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"most of the clock time is not creative. It is the same checklist"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;"Reframe to 9:16" is on that checklist. The usual way to do it is to duplicate the project file, change the canvas, nudge everything, and export. Now you have two projects that drift apart the moment you fix a typo in one of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Versions live inside one project
&lt;/h2&gt;

&lt;p&gt;In CutVoke a "production version" is another &lt;strong&gt;sequence in the same project&lt;/strong&gt;, not another file.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;sequence.duplicate&lt;/code&gt; copies the complete editable sequence and can set &lt;code&gt;width&lt;/code&gt;, &lt;code&gt;height&lt;/code&gt;, &lt;code&gt;fps&lt;/code&gt; and &lt;code&gt;reframe&lt;/code&gt; in the same step. Internal object IDs are regenerated and references updated, nested sequences included.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sequence.configure&lt;/code&gt; changes the active sequence's real canvas, frame rate and framing.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sequence.switch&lt;/code&gt; moves between them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Canvas sizes are even numbers from 2 to 8192, frame rates 1–240. Changing the frame rate keeps absolute time, so clip speed doesn't change. Duplicating, configuring and switching are all undoable, and the original 16:9 sequence stays as it was.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three framing modes, and what they really do
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;reframe&lt;/code&gt; takes one of three values:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;contain&lt;/code&gt;: keep the whole picture (letterbox/pillarbox).&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;cover&lt;/code&gt;: fill the canvas and &lt;strong&gt;crop from the centre&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;stretch&lt;/code&gt;: the old default, kept for older projects.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Positions and pixel font sizes are scaled to the new canvas; caption font size, stroke and shadow are scaled too, and default caption size is still picked from the canvas.&lt;/p&gt;

&lt;p&gt;The honest part: &lt;code&gt;cover&lt;/code&gt; is a geometric centre crop. &lt;strong&gt;It is not face detection and not speaker tracking.&lt;/strong&gt; If your speaker sits on the left third, a centre crop will cut them. For two people in frame, &lt;code&gt;contain&lt;/code&gt; or a layout you build yourself on extra tracks is the safer choice. CutVoke has no ready-made "two boxes stacked vertically" template; that is manual track positioning.&lt;/p&gt;

&lt;h2&gt;
  
  
  Letting the agent do the boring part, and look at it
&lt;/h2&gt;

&lt;p&gt;Over MCP, the flow an agent can follow is roughly:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;sequence.duplicate&lt;/code&gt; with 1080×1920 and &lt;code&gt;reframe: cover&lt;/code&gt; (or &lt;code&gt;contain&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;preview_frames&lt;/code&gt; to get up to 6 real rendered frames, captions included, and check headroom, hands, faces and subtitles.&lt;/li&gt;
&lt;li&gt;Adjust the supported transforms/keyframes where the crop is wrong.&lt;/li&gt;
&lt;li&gt;Leave the edit for a human to open and fix by hand on the same timeline if the agent's crop choice is off.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The agent doesn't get taste for free. What it gets is pixels to check before anyone exports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Queue every version at once
&lt;/h2&gt;

&lt;p&gt;With an output path prefix set, "queue all versions" submits one export job per sequence, with the sequence ID in the file suffix. Each job freezes that sequence's canvas, frame rate, framing and timeline when it is queued, so editing afterwards doesn't change a job that's already submitted. &lt;code&gt;export.enqueue&lt;/code&gt; and &lt;code&gt;POST /projects/{id}/exports&lt;/code&gt; both accept a &lt;code&gt;sequenceId&lt;/code&gt;, so you don't have to switch the active sequence first. Agents poll the job with &lt;code&gt;export_job&lt;/code&gt; and wait the returned &lt;code&gt;pollAfterSeconds&lt;/code&gt; between checks.&lt;/p&gt;

&lt;p&gt;Exports re-encode (libx264, or NVENC when available). This is not a lossless stream-copy tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this doesn't solve
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No subject/face-tracking reframe (centre crop only).&lt;/li&gt;
&lt;li&gt;No automatic highlight or "best 30 seconds" picking.&lt;/li&gt;
&lt;li&gt;No layout templates for split-screen verticals.&lt;/li&gt;
&lt;li&gt;Desktop only (Windows/macOS/Linux).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the versions problem is where your week goes, the docs for this part are in &lt;code&gt;docs/user/PRODUCTION_VERSIONS_INTERCHANGE.md&lt;/code&gt; in the repo: &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt;. Questions and "this broke on my footage" reports are welcome in the comments.&lt;/p&gt;

</description>
      <category>videoediting</category>
      <category>opensource</category>
      <category>mcp</category>
      <category>ai</category>
    </item>
    <item>
      <title>Three cameras, one recorder: waveform sync that is allowed to say "I don't know"</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Sun, 15 Nov 2026 04:22:24 +0000</pubDate>
      <link>https://dev.to/shansjl/three-cameras-one-recorder-waveform-sync-that-is-allowed-to-say-i-dont-know-5bp5</link>
      <guid>https://dev.to/shansjl/three-cameras-one-recorder-waveform-sync-that-is-allowed-to-say-i-dont-know-5bp5</guid>
      <description>&lt;p&gt;&lt;em&gt;I build &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an open-source (MIT) local video editor where Claude Code / Codex edit the same timeline you do, over MCP. This post is about one small piece of it: multicam audio sync, and why it refuses instead of guessing.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The boring part of a multi-angle edit
&lt;/h2&gt;

&lt;p&gt;Podcast and interview editors keep describing the same week: the edit itself is fine, but lining up the camera angles, switching between them and levelling the audio eat the time. Lining up angles is mechanical work, so it is a good job for software, or for an agent driving the editor. It is also a job where a confident wrong answer is worse than no answer: a camera that is 0.3 s off looks like a dubbed film, and you may only notice it at export.&lt;/p&gt;

&lt;p&gt;So the rule for &lt;code&gt;multicam.sync&lt;/code&gt; in CutVoke is: align when the audio clearly agrees, and refuse to touch the timeline when it doesn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it actually does
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;multicam.sync {referenceTrackId, targetTrackId, maxOffsetSeconds?}&lt;/code&gt; (source: &lt;code&gt;src/cutvoke/rendering/multicam_sync.py&lt;/code&gt;):&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Reads each camera's real source audio with ffmpeg: mono, 8 kHz, up to the first 60 seconds.&lt;/li&gt;
&lt;li&gt;Turns it into an RMS energy envelope in 10 ms windows, so the time resolution is 10 ms.&lt;/li&gt;
&lt;li&gt;Runs normalized cross-correlation over lags within ±10 s by default (you can raise it to ±30 s).&lt;/li&gt;
&lt;li&gt;Takes the best score as &lt;code&gt;confidence&lt;/code&gt;, and the best score at least 150 ms away from it as the runner-up. &lt;code&gt;ambiguityMargin&lt;/code&gt; = best − runner-up.&lt;/li&gt;
&lt;li&gt;If &lt;code&gt;confidence &amp;lt; 0.65&lt;/code&gt; or &lt;code&gt;ambiguityMargin &amp;lt; 0.05&lt;/code&gt;, it raises &lt;em&gt;"Ambiguous waveform sync … align manually"&lt;/em&gt; and changes nothing.&lt;/li&gt;
&lt;li&gt;Otherwise it moves the target clip. If the shift would push it before timeline zero, it trims that prefix and moves the source in-point to match.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The result is returned to the caller and stored in the project: &lt;code&gt;method&lt;/code&gt;, &lt;code&gt;lagSeconds&lt;/code&gt;, &lt;code&gt;confidence&lt;/code&gt;, &lt;code&gt;ambiguityMargin&lt;/code&gt;, &lt;code&gt;appliedDeltaSeconds&lt;/code&gt;, &lt;code&gt;clippedPrefixSeconds&lt;/code&gt;. The sync can be undone like any other edit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a margin, not just a threshold
&lt;/h2&gt;

&lt;p&gt;A high peak alone isn't enough. Repetitive audio (a steady beat, a clap track, room hum) can produce several peaks of almost the same height a fraction of a second apart. Picking the tallest one is a coin toss that looks like a precise number. The margin check turns "two answers are almost equally good" into an explicit refusal, which an agent can report back ("I couldn't sync camera B, please align it by hand") instead of quietly shipping an offset.&lt;/p&gt;

&lt;h2&gt;
  
  
  The guard rails (stated limits)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One continuous, ordinary 1x clip per camera. Speed changes, freeze frames and nested clips are rejected.&lt;/li&gt;
&lt;li&gt;At least two seconds of non-silent audio.&lt;/li&gt;
&lt;li&gt;Sync the target camera &lt;em&gt;before&lt;/em&gt; adding effects or keyframes to it, or the command refuses.&lt;/li&gt;
&lt;li&gt;It does &lt;strong&gt;not&lt;/strong&gt; fix clock drift on long recordings. It finds one offset from the first minute. Check the head and the tail after syncing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  After sync: switching and audio
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;multicam.switch {trackId, time}&lt;/code&gt; stores explicit cut points at timeline times (as rationals). Switching again at the same time replaces that cut. Camera source clips are not chopped up, and preview and export use the same selection.&lt;/li&gt;
&lt;li&gt;Program audio stays on the initial camera and doesn't jump with the picture cuts.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;audio.normalize&lt;/code&gt; runs ffmpeg &lt;code&gt;loudnorm&lt;/code&gt; in two passes (measure, then apply with the measured values) to a file, default target −16 LUFS.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Doing it from an agent
&lt;/h2&gt;

&lt;p&gt;Because these are ordinary commands on the shared timeline, Claude Code or Codex can call them over MCP and you can watch and take over in the UI. A reasonable agent loop is: create the multicam group, sync each angle, report the &lt;code&gt;confidence&lt;/code&gt; / &lt;code&gt;ambiguityMargin&lt;/code&gt; for each, and stop at the first refusal for a human to look at. Picking &lt;em&gt;which&lt;/em&gt; angle to show when is still your call; CutVoke doesn't choose shots for you.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt; (pre-release, desktop, MIT). If you sync multicam footage another way (timecode, slate claps, PluralEyes-style tools), I'd like to hear where audio-only sync breaks for you.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>video</category>
      <category>python</category>
      <category>mcp</category>
    </item>
    <item>
      <title>When prompting is slower than dragging: design for the hand-off between agent and editor</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Sun, 15 Nov 2026 00:12:58 +0000</pubDate>
      <link>https://dev.to/shansjl/when-prompting-is-slower-than-dragging-design-for-the-hand-off-between-agent-and-editor-3p3b</link>
      <guid>https://dev.to/shansjl/when-prompting-is-slower-than-dragging-design-for-the-hand-off-between-agent-and-editor-3p3b</guid>
      <description>&lt;p&gt;A beginner on r/davinciresolve asked a question last month that I keep coming back to (&lt;a href="https://www.reddit.com/r/davinciresolve/comments/1xh8x23/" rel="noopener noreferrer"&gt;thread&lt;/a&gt;):&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"5 hours later, I have the video edited pretty much exactly as I wanted, but I haven't learned a thing about how to really use Davinci Resolve."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;and then:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The UI was built and optimized for video editing, therefore I imagine with some basic skills I'd be able to edit videos much quicker than through prompting the MCP."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I think they're right about the second part. Plenty of edits are faster with a mouse than with a sentence: nudging a cut by a few frames, trying three positions for a title, scrubbing to find the moment someone laughs. Describing those in words is slow and lossy.&lt;/p&gt;

&lt;p&gt;But it doesn't have to be prompt &lt;em&gt;or&lt;/em&gt; drag. The question I care about is: &lt;strong&gt;what does an editor need so you can switch between the two at any moment, without losing work or trust?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I build &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an open-source (MIT) local video editor that Claude Code / Codex / any MCP client can drive. Here are the design choices I made around that hand-off. Nothing here makes learning an editor faster; that part is still on you.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. One timeline, not an export
&lt;/h2&gt;

&lt;p&gt;If the agent hands you back an MP4, every fix is either "re-roll the prompt" or "start over in a real editor". So in CutVoke the agent and the human edit the &lt;strong&gt;same declarative timeline&lt;/strong&gt;. Whatever the agent did is sitting in the UI as normal clips, captions and keyframes you can grab and drag.&lt;/p&gt;

&lt;p&gt;That gives a simple rule of thumb: let the agent do the mechanical passes (rough assembly, captions, loudness, a 9:16 copy), and do the judgment edits by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Taking over is a button, not a race
&lt;/h2&gt;

&lt;p&gt;Two writers on one timeline need rules. An agent that wants to make batch edits first takes an &lt;strong&gt;editing lease&lt;/strong&gt;. While it holds one, the editor shows the lease owner and the remaining time.&lt;/p&gt;

&lt;p&gt;When you want the timeline back, &lt;strong&gt;Take over editing&lt;/strong&gt; ends that specific lease and refreshes the project. Completed edits are preserved; any later request that still uses the old lease is rejected. So the agent can't quietly overwrite what you're doing after you've taken over.&lt;/p&gt;

&lt;p&gt;Before you take over, &lt;strong&gt;Review changes during this lease&lt;/strong&gt; lists the latest 20 committed revision summaries, so you can see what the agent actually changed instead of guessing. (It covers versioned edits only, not renames or exports.)&lt;/p&gt;

&lt;p&gt;The agent is told the same thing: its built-in guide says to "release the lease for human takeover".&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Every write says which version it was looking at
&lt;/h2&gt;

&lt;p&gt;Each agent edit carries an &lt;code&gt;expectedRevision&lt;/code&gt;. If you changed the timeline in the UI in the meantime, the revision no longer matches and the edit is refused rather than applied on top of a project the agent hasn't seen. The agent has to re-read and try again.&lt;/p&gt;

&lt;p&gt;Multi-step changes go through &lt;code&gt;edit.batch&lt;/code&gt;, which lands as &lt;strong&gt;one undo step&lt;/strong&gt;. If you don't like what the agent did, it's one undo, not twelve.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. "Show me before you commit"
&lt;/h2&gt;

&lt;p&gt;A lot of the slowness in prompting an editor isn't the typing. It's not knowing what a command will do until after it has run.&lt;/p&gt;

&lt;p&gt;So the agent can preview first. &lt;code&gt;preview_compare&lt;/code&gt; takes a command that hasn't been applied yet, plus 1 to 3 timestamps, and returns before/after PNG pairs rendered from the same snapshot, captions included. Project, history and revision stay unchanged. Then the agent (or you) decides whether to apply it with the latest revision.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;preview_frames&lt;/code&gt; returns up to 6 real rendered frames of the current project, and &lt;code&gt;preview_audio&lt;/code&gt; returns a short window of the mixed audio around a cut (up to 5 seconds). These are evidence, not judgment: a waveform peak doesn't prove a cut sounds clean.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What it does &lt;em&gt;not&lt;/em&gt; do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No highlight picking.&lt;/strong&gt; It won't choose your best 4 minutes out of 7 hours. Transcript search, locate and audition make finding takes faster, but choosing them is yours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The agent's taste is the agent's.&lt;/strong&gt; CutVoke executes edits and returns evidence; it doesn't decide what looks good.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exports re-encode&lt;/strong&gt; (libx264, or NVENC when available). It isn't a lossless stream-copy cutter.&lt;/li&gt;
&lt;li&gt;Desktop only (Windows/macOS/Linux), and it's a pre-release.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Back to the question
&lt;/h2&gt;

&lt;p&gt;Should a beginner skip the MCP? I'd say: learn the handful of hand moves that are faster than describing them (trim, nudge, ripple delete), and give the agent the boring passes. The tool's job is to make that switch cheap: same timeline, a clear takeover button, version checks, and previews before anything is committed.&lt;/p&gt;

&lt;p&gt;If you've built agent tools where a human has to step in halfway, I'd like to hear how you handled the hand-off.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>video</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Cut once, subtitles follow: a ripple delete that includes the caption track</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Sat, 14 Nov 2026 07:17:39 +0000</pubDate>
      <link>https://dev.to/shansjl/cut-once-subtitles-follow-a-ripple-delete-that-includes-the-caption-track-2m3</link>
      <guid>https://dev.to/shansjl/cut-once-subtitles-follow-a-ripple-delete-that-includes-the-caption-track-2m3</guid>
      <description>&lt;p&gt;A feature request on a popular open-source cutter this month put a common subtitle problem in one sentence:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I need to choose the cut points once and get both the edited video and synchronized subtitles. Repeating the edit in a subtitle editor adds time and makes it easy to introduce a sync offset."&lt;br&gt;
(public request: &lt;a href="https://github.com/mifi/lossless-cut/issues/3209" rel="noopener noreferrer"&gt;mifi/lossless-cut #3209&lt;/a&gt;)&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That tool has good reasons to be built the way it is. Stream-copy cutting is its whole point, and this post isn't a knock on it. But the request describes a real gap: the video and the &lt;code&gt;.srt&lt;/code&gt; are usually edited as two separate things, and every cut has to be made twice.&lt;/p&gt;

&lt;p&gt;I build &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an open-source (MIT) local video editor that Claude Code / Codex can also drive over MCP. Here is how it treats captions as part of the timeline, so one cut moves everything. I'll also cover where it is &lt;em&gt;not&lt;/em&gt; the right tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Delete a time range, not a clip
&lt;/h2&gt;

&lt;p&gt;Deleting a clip and closing the gap on one track is easy. The trouble is everything else sitting on that stretch of time: other tracks, captions, markers.&lt;/p&gt;

&lt;p&gt;CutVoke has a sequence-level command for this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;sequence.deleteRange { start, end }
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It deletes &lt;code&gt;[start, end)&lt;/code&gt; across the &lt;strong&gt;whole sequence&lt;/strong&gt;. It trims and closes up video, audio, &lt;strong&gt;captions&lt;/strong&gt;, markers, automation and multicam cut points in one atomic command. If any affected track is locked, the entire command is refused instead of half-applied. One undo restores everything.&lt;/p&gt;

&lt;p&gt;Captions that straddle the range are trimmed. Captions after it shift left by exactly the deleted duration, so there's no second pass in a subtitle editor and no offset creeping in.&lt;/p&gt;

&lt;p&gt;(There's also &lt;code&gt;clip.rippleDelete&lt;/code&gt; with &lt;code&gt;scope: "sequence"&lt;/code&gt;, which removes a clip and ripples tracks, captions and markers together.)&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Or cut by text
&lt;/h2&gt;

&lt;p&gt;When the captions came from speech recognition, the transcript itself is a good place to cut:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Search the transcript and &lt;strong&gt;locate&lt;/strong&gt; a sentence on the timeline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audition&lt;/strong&gt; it (playback stops at the end of the range).&lt;/li&gt;
&lt;li&gt;Select sentences, or individual words where word timings exist.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;"Preview deletion impact"&lt;/strong&gt;. This only calculates which clips and captions would be affected. It doesn't change the project or add an undo entry.&lt;/li&gt;
&lt;li&gt;Confirm, and the matching voice, picture and captions are removed together.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;However many sentences or words you picked, that confirmation is a single &lt;code&gt;transcript.delete&lt;/code&gt; command with one undo. Overlapping ranges are only processed once.&lt;/p&gt;

&lt;p&gt;An agent can call the same command over MCP, e.g. "delete caption lines 12 and 14". It goes through the same revision checks as the UI, so a human can review the result on the normal timeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Then export
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SRT&lt;/strong&gt;: export the project's captions after the cut. Multi-line captions survive an SRT round trip. I tested &lt;code&gt;parse_srt&lt;/code&gt; → &lt;code&gt;export_srt&lt;/code&gt; locally, and "line one / line two" came back as two lines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WebVTT&lt;/strong&gt;: &lt;code&gt;caption.exportVtt&lt;/code&gt;, also available to agents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Burned in&lt;/strong&gt;: the MP4 export can burn the captions into the picture.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you don't have captions yet, CutVoke can make a local draft with faster-whisper (auto / zh / en / ja / ko). Nothing is uploaded, and the draft only lands in the project after you review it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this is not the right tool
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;It re-encodes.&lt;/strong&gt; Export goes through libx264 (or NVENC when available). If you need lossless stream-copy cuts, keep using a stream-copy cutter. CutVoke solves the "cut once, captions follow" half, not the lossless half.&lt;/li&gt;
&lt;li&gt;It doesn't pick highlights for you, and it's desktop-only (Windows / macOS / Linux, currently a prerelease).&lt;/li&gt;
&lt;li&gt;I haven't measured how it performs on multi-hour recordings.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Takeaway (even if you never use CutVoke)
&lt;/h2&gt;

&lt;p&gt;If your tool lets people edit video and text tracks together, make &lt;strong&gt;time-range deletion a single command that knows about every track type&lt;/strong&gt;. Add a dry-run that previews the impact, and make the whole thing one undo. Most subtitle drift doesn't come from bad timestamps. It comes from making the same edit twice.&lt;/p&gt;

&lt;p&gt;Repo and docs: &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt; (transcript editing is in &lt;code&gt;docs/user/ADVANCED_TIMELINE.md&lt;/code&gt;).&lt;/p&gt;

</description>
      <category>video</category>
      <category>opensource</category>
      <category>subtitles</category>
      <category>mcp</category>
    </item>
    <item>
      <title>Why my local Whisper captions never write straight into the project</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Fri, 13 Nov 2026 13:21:53 +0000</pubDate>
      <link>https://dev.to/shansjl/why-my-local-whisper-captions-never-write-straight-into-the-project-5n6</link>
      <guid>https://dev.to/shansjl/why-my-local-whisper-captions-never-write-straight-into-the-project-5n6</guid>
      <description>&lt;p&gt;I build &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an open-source local video editor that Claude Code / Codex can drive over MCP while you keep a normal timeline open in the app. The most-asked-for agent task is boring: &lt;em&gt;"cut the silences and add captions."&lt;/em&gt; Captions turned out to be the place where I had to be most careful about &lt;strong&gt;who is allowed to change the project, and when&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Here is the design I ended up with, in case you're wiring speech recognition (or any slow, fallible model) into an app that both a human and an agent edit.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Recognition returns a proposal, not an edit
&lt;/h2&gt;

&lt;p&gt;Automatic captions use &lt;code&gt;faster-whisper&lt;/code&gt; locally (optional &lt;code&gt;cutvoke[asr]&lt;/code&gt; extra; the model downloads once, and you can pre-download it for offline machines). Nothing is uploaded.&lt;/p&gt;

&lt;p&gt;The important part: a recognition run &lt;strong&gt;never touches the project&lt;/strong&gt;. It produces a draft. In the UI you fix words and timings, delete bad candidates, then click "Add to project", and all accepted lines land as &lt;strong&gt;one undoable command&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Agents get the same split. &lt;code&gt;caption.transcribe&lt;/code&gt; only returns the proposal. &lt;code&gt;caption.bulkAdd&lt;/code&gt; commits many subtitle lines at once. So an agent can transcribe, look at the text, drop the junk, and commit, and the human can undo the whole batch in one step.&lt;/p&gt;

&lt;p&gt;(There is also an older &lt;code&gt;caption.autoSegment&lt;/code&gt;, which only splits on silence and inserts placeholder text. It isn't speech recognition, and the docs say so explicitly so agents don't confuse the two.)&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Bind the proposal to the source it was made from
&lt;/h2&gt;

&lt;p&gt;Speech recognition is slow. In the time it runs, someone can trim the clip, move it, swap the source file or change its speed. If you then commit the old timestamps, every caption is off.&lt;/p&gt;

&lt;p&gt;So each proposal carries a &lt;strong&gt;source signature&lt;/strong&gt;. It's checked when you resume a job and again at commit time. If the clip or file changed, the draft is rejected and you're told to re-run recognition, instead of silently writing misaligned subtitles. It's the same idea as the &lt;code&gt;expectedRevision&lt;/code&gt; check on normal timeline edits: stale writes come back as conflicts, they don't land.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Jobs survive closing the app
&lt;/h2&gt;

&lt;p&gt;Proposals and proofreading drafts live in a job ledger in the same SQLite database as the project, not in browser memory. Draft edits autosave about 350 ms after you stop typing. Close the app, reopen the project, and the draft is still there.&lt;/p&gt;

&lt;p&gt;A few edge cases that bit me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cancel must win.&lt;/strong&gt; Cancellation is persisted, and a late model result can't overwrite a cancelled job.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interrupted jobs don't auto-commit.&lt;/strong&gt; If the service dies mid-run, the job shows "waiting to resume". Resuming re-runs from the start of the clip with the same model and language, re-checks the source first, and still doesn't write captions by itself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Older saves can't clobber newer ones.&lt;/strong&gt; If an earlier save request arrives late, it's ignored.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bounded queue.&lt;/strong&gt; At most two queued/running jobs, and the ledger keeps running jobs plus the latest 24 others from the past 7 days.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Small details that matter for real footage
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Device &lt;code&gt;auto&lt;/code&gt;: GPU float16 if CTranslate2 sees CUDA, falling back to CPU int8 if the GPU model fails to load. &lt;code&gt;CUTVOKE_ASR_DEVICE=cpu|cuda&lt;/code&gt; forces it.&lt;/li&gt;
&lt;li&gt;For Chinese, output is normalized to Simplified with OpenCC &lt;code&gt;tw2s&lt;/code&gt; over the whole word sequence, so per-word timestamps stay intact and single characters keep their context.&lt;/li&gt;
&lt;li&gt;Accepted captions stay editable on their own track, export to SRT, and get burned into MP4 exports.&lt;/li&gt;
&lt;li&gt;Recognition still needs a human pass, especially names, dialects and music-heavy audio. That's exactly why it's a proposal.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the agent flow looks like
&lt;/h2&gt;

&lt;p&gt;With CutVoke added to Claude Code (&lt;a href="https://github.com/frankShan001/CutVoke/blob/main/docs/integrations/claude-code.md" rel="noopener noreferrer"&gt;setup guide&lt;/a&gt;), a prompt like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Find the sentence where I say 'pricing' in the transcript, remove it, and export a new MP4 next to the original."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;runs against the same timeline you have open, and anything it got wrong is a clip or a caption you can fix by hand, not a re-roll.&lt;/p&gt;

&lt;h2&gt;
  
  
  The general lesson
&lt;/h2&gt;

&lt;p&gt;If a model is slow and sometimes wrong, give its output a &lt;strong&gt;staging area&lt;/strong&gt;: a proposal bound to the exact input it saw, committed as one undoable step, rejected if the world moved underneath it. That made captions the least scary thing to hand an agent instead of the most.&lt;/p&gt;

&lt;p&gt;Repo (MIT, Windows/macOS/Linux): &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt;. Local ASR doc: &lt;a href="https://github.com/frankShan001/CutVoke/blob/main/docs/user/LOCAL_ASR.md" rel="noopener noreferrer"&gt;docs/user/LOCAL_ASR.md&lt;/a&gt;. I'd love to hear how others handle stale model output in collaborative apps.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>mcp</category>
      <category>video</category>
    </item>
    <item>
      <title>Instagram gave its video editor an MCP. Here's what an agent-editable timeline actually needs</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Tue, 10 Nov 2026 13:54:29 +0000</pubDate>
      <link>https://dev.to/shansjl/instagram-gave-its-video-editor-an-mcp-heres-what-an-agent-editable-timeline-actually-needs-437l</link>
      <guid>https://dev.to/shansjl/instagram-gave-its-video-editor-an-mcp-heres-what-an-agent-editable-timeline-actually-needs-437l</guid>
      <description>&lt;p&gt;Last week Instagram shipped Edits for Mac with an MCP server, so Claude and other agents can operate a real video editor instead of generating a clip from scratch. Whatever you think of Instagram, that's a signal: editors are turning into toolboxes that agents call.&lt;/p&gt;

&lt;p&gt;I've been building the open-source version of that idea since September. It's called CutVoke, an MIT-licensed, local-first editor that runs on Windows, macOS and Linux, with no account and no cloud. Disclosure up front: I'm the author, and it's an early prerelease.&lt;/p&gt;

&lt;p&gt;Building it taught me that "give the agent an MCP server" is the easy part. The hard part is everything that happens after the agent's first cut, when a human wants to change something. Here are five things I had to get right.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Leases, not hope
&lt;/h2&gt;

&lt;p&gt;The first version let the agent and the UI write to the same project at the same time. It worked fine until I dragged a clip while the agent was halfway through a batch of edits. One of us lost.&lt;/p&gt;

&lt;p&gt;Now the agent takes an editing lease before it makes grouped changes. While the lease is held, the editor knows an agent is working, and the agent's batch can't be split by a manual edit landing in the middle. When the agent is done, the lease is released and the human has the timeline back. The next feature I'm working on is letting the human safely take over a lease the agent forgot to release.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Dry-runs before commits
&lt;/h2&gt;

&lt;p&gt;Agents are confident. A command like "delete the sentence where I say 'um, basically'" sounds simple until it removes picture, audio and three captions on four tracks.&lt;/p&gt;

&lt;p&gt;So supported commands have a preview mode. The agent calls &lt;code&gt;command_preview&lt;/code&gt; first, gets back what would change, and only then commits. For transcript cuts it can see the deletion's impact before confirming. That one habit removed most of the "why did it delete that" moments.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Revision numbers, so nobody edits a stale project
&lt;/h2&gt;

&lt;p&gt;Every commit carries an &lt;code&gt;expectedRevision&lt;/code&gt; and a stable &lt;code&gt;commandId&lt;/code&gt;. If the project changed since the agent last looked (because I edited something by hand), the commit is rejected instead of silently overwriting my change. The agent re-reads and tries again. It's boring optimistic concurrency, and it matters more for agents than for people, because agents don't notice that the screen changed.&lt;/p&gt;

&lt;p&gt;Grouped edits also go through &lt;code&gt;edit.batch&lt;/code&gt;, which makes the whole batch one undo step. If the agent's idea was bad, one Ctrl+Z undoes it.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Let the agent actually look
&lt;/h2&gt;

&lt;p&gt;The biggest quality jump came from giving the agent eyes. &lt;code&gt;preview_frames&lt;/code&gt; returns real rendered PNG frames at the timestamps it asks for, captions and effects included. Before that, the agent "knew" a title was centered because the numbers said so. Now it looks at the frame, sees the caption is covering a face, and moves it before export.&lt;/p&gt;

&lt;p&gt;If you build an agent tool for any visual medium, I'd put this near the top of the list.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. The output has to be a timeline, not an MP4
&lt;/h2&gt;

&lt;p&gt;Most AI video tools give you a finished file. That's fine until you want to change one word in one subtitle, and the answer is to regenerate everything.&lt;/p&gt;

&lt;p&gt;In CutVoke the result of the agent's work is a normal project: multitrack, captions as individual objects, keyframes, masks, speed ramps. I open it in the same editor and keep going by hand. The agent can also clone a project and swap in new media to make a second version. The editor, the MCP server, the HTTP API and the CLI all read and write the same project database, so nothing has to be exported or re-imported between the agent and the human.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it falls short today
&lt;/h2&gt;

&lt;p&gt;Honestly, plenty. It's a v0.3.5 prerelease. The Windows build is unsigned, so SmartScreen will complain, and the macOS build isn't notarized. The project format may still change. It doesn't generate footage, and there's no LLM inside: you bring Claude Code, Codex, Cursor or any MCP client. Compared with mature editors like Kdenlive or Resolve, it's young and much smaller.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it or tear it apart
&lt;/h2&gt;

&lt;p&gt;Setup is three steps: download a build, copy the MCP command from &lt;code&gt;profile/mcp-config.json&lt;/code&gt;, and run &lt;code&gt;claude mcp add cutvoke -- &amp;lt;command&amp;gt;&lt;/code&gt;. Two demo projects ship in the repo with their source media.&lt;/p&gt;

&lt;p&gt;I'd really like to hear from people building agent tools for other creative apps. What did you need beyond "expose the commands"?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>opensource</category>
      <category>video</category>
    </item>
    <item>
      <title>Designing MCP tools for a stateful app: what I learned building an AI-editable video timeline</title>
      <dc:creator>shansjl</dc:creator>
      <pubDate>Mon, 09 Nov 2026 17:03:20 +0000</pubDate>
      <link>https://dev.to/shansjl/designing-mcp-tools-for-a-stateful-app-what-i-learned-building-an-ai-editable-video-timeline-4mfp</link>
      <guid>https://dev.to/shansjl/designing-mcp-tools-for-a-stateful-app-what-i-learned-building-an-ai-editable-video-timeline-4mfp</guid>
      <description>&lt;p&gt;Most MCP servers wrap something stateless: search an API, read a file, query a DB. I built one for something very stateful — a multitrack video project that a human is editing at the same time. This post is about the design choices that made that workable. The project is &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;CutVoke&lt;/a&gt;, an MIT-licensed, local-first video editor.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: AI video ends in an MP4
&lt;/h2&gt;

&lt;p&gt;Agent-driven video pipelines usually render a file and stop. When a caption is wrong or a cut is late, you re-run the pipeline or rebuild everything in a human editor. I wanted the agent's output to &lt;em&gt;be&lt;/em&gt; an editable project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture in one picture
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmjclpspmc3vdivfv62md.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmjclpspmc3vdivfv62md.png" alt="how it works" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A Python engine owns a persistent project (tracks, clips, captions, keyframes, effects), stored locally.&lt;/li&gt;
&lt;li&gt;Four front doors share it: a React editor (&lt;code&gt;cutvoke serve&lt;/code&gt;, loopback only), an MCP server (&lt;code&gt;cutvoke mcp --data …&lt;/code&gt;, stdio), an HTTP API, and a CLI.&lt;/li&gt;
&lt;li&gt;FFmpeg renders previews and exports. Desktop builds bundle it.&lt;/li&gt;
&lt;li&gt;There is no model inside. The agent is whatever you already use.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Lesson 1: give the agent a lease, not a lock-free free-for-all
&lt;/h2&gt;

&lt;p&gt;When a person is dragging clips and an agent is running a 15-step edit, you need a rule for who writes. CutVoke uses an &lt;strong&gt;editing lease&lt;/strong&gt;: the agent calls &lt;code&gt;edit_lock&lt;/code&gt;, renews it during long jobs, and releases it on success or failure. The UI shows that an agent is editing. Commits also carry &lt;code&gt;expectedRevision&lt;/code&gt;, so a stale plan is rejected instead of silently clobbering human work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 2: dry runs and batches beat "be careful" prompts
&lt;/h2&gt;

&lt;p&gt;Instead of telling the model to be careful, make carefulness cheap. Supported commands can be dry-run with &lt;code&gt;command_preview&lt;/code&gt;. Related changes go into &lt;code&gt;edit.batch&lt;/code&gt;, which is &lt;strong&gt;one undo step&lt;/strong&gt; for the human. A stable &lt;code&gt;commandId&lt;/code&gt; makes retries idempotent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 3: let the agent see pixels, not JSON
&lt;/h2&gt;

&lt;p&gt;A timeline JSON can be perfectly valid and still look terrible: captions off-screen, a title over a face, a black frame at a cut. &lt;code&gt;preview_frames&lt;/code&gt; returns real rendered PNGs (up to 6 timestamps per call), captions and titles included. The guide tells agents to check frames around cuts, transitions and caption intervals — and to first check whether the client can actually read tool images at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 4: keep the tool catalog small and lazy
&lt;/h2&gt;

&lt;p&gt;A video editor has a lot of commands. Dumping every schema into context hurts smaller models. Discovery is layered: &lt;code&gt;editor_help&lt;/code&gt; (onboarding + recipes) → &lt;code&gt;commands_list({"includeSchemas": false, "query": "caption"})&lt;/code&gt; → &lt;code&gt;editor_help({"topic":"command","command":"caption.patch"})&lt;/code&gt; for the exact payload schema.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 5: objects, not pixels, for the things people fix most
&lt;/h2&gt;

&lt;p&gt;The most common post-AI fix is text. Captions are individual objects: &lt;code&gt;project_lookup&lt;/code&gt; finds a line by its text, &lt;code&gt;caption.patch&lt;/code&gt; changes words, timing or style. Transcript-based cutting works the same way: locate a sentence, audition it, preview the impact of deleting it, confirm, undo in one step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Downloads (prerelease, unsigned): &lt;a href="https://github.com/frankShan001/CutVoke/releases/tag/v0.3.5" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke/releases/tag/v0.3.5&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;From source: &lt;code&gt;pip install -e .&lt;/code&gt;, build the editor, &lt;code&gt;cutvoke doctor --json&lt;/code&gt;, then &lt;code&gt;python skills/cutvoke-editor/scripts/demo.py --output .artifacts/first-edit&lt;/code&gt; builds a 12-second edit over real stdio MCP.&lt;/li&gt;
&lt;li&gt;The README has two complete edits with source footage and editable projects.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's early and I'd value feedback on the agent API more than anything: if you've built tools for stateful apps, what would you do differently?&lt;/p&gt;

&lt;p&gt;⭐ Repo: &lt;a href="https://github.com/frankShan001/CutVoke" rel="noopener noreferrer"&gt;https://github.com/frankShan001/CutVoke&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>ai</category>
      <category>mcp</category>
      <category>video</category>
    </item>
  </channel>
</rss>
