I build CutVoke , 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: "cut the silences and add captions." Captions turned out to be the place where I had to be most careful about who is allowed to change the project, and when .
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.
1. Recognition returns a proposal, not an edit
Automatic captions use faster-whisper locally (optional cutvoke[asr] extra; the model downloads once, and you can pre-download it for offline machines). Nothing is uploaded.
The important part: a recognition run never touches the project . 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 one undoable command .
Agents get the same split.…