When prompting is slower than dragging: design for the hand-off between agent and editor

A beginner on r/davinciresolve asked a question last month that I keep coming back to (thread):

"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."

and then:

"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."

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.

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

I build CutVoke, 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.

1. One timeline, not an export

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 same declarative timeline. Whatever the agent did is sitting in the UI as normal clips, captions and keyframes you can grab and drag.

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.

2. Taking over is a button, not a race

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

When you want the timeline back, Take over editing 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.

Before you take over, Review changes during this lease 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.)

The agent is told the same thing: its built-in guide says to "release the lease for human takeover".

3. Every write says which version it was looking at

Each agent edit carries an expectedRevision. 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.

Multi-step changes go through edit.batch, which lands as one undo step. If you don't like what the agent did, it's one undo, not twelve.

4. "Show me before you commit"

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.

So the agent can preview first. preview_compare 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.

preview_frames returns up to 6 real rendered frames of the current project, and preview_audio 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.

5. What it does not do

• No highlight picking. 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.
• The agent's taste is the agent's. CutVoke executes edits and returns evidence; it doesn't decide what looks good.
• Exports re-encode (libx264, or NVENC when available). It isn't a lossless stream-copy cutter.
• Desktop only (Windows/macOS/Linux), and it's a pre-release.

Back to the question

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.

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.

Repo: https://github.com/frankShan001/CutVoke