Footage and agentic editing

AI Can Edit a Timeline Now. What Does That Actually Mean for Filmmakers?

Premiere, Resolve, Edits and Descript now take instructions from AI agents. What each can do, what's still beta, and where your judgment stays.

Updated November 11, 2026 · 12 min read

In September, Blackmagic Design released DaVinci Resolve 21.1 and said it now works with AI assistants such as Claude, Claude Code and ChatGPT Codex. Blackmagic's example, as Digital Production reported it, asks Claude to turn a long clip into a three-minute highlight edit, remove edits under one second and render H.265. Adobe's AI Assistant in Premiere has been in public beta since June, building bins, adding markers and laying out stringouts. On November 5, Instagram released Edits for Mac with a setting that lets an outside agent make a rough cut. On November 10, Adobe said it is previewing local MCP integrations that let third-party agents edit Premiere project files.

So a chat can now organize a project and build an assembly in an editor you already use. That's real, and it's useful for the hours of preparation before the creative edit starts.

It's also narrower than "AI editing" suggests. Changing a timeline is not the same as understanding why a scene works. An agent can remove every edit shorter than a second. It can't know that the half-second reaction is the reason the scene lands, unless you tell it. This guide separates the four things sold as AI editing, follows one request through the machinery, compares what the current tools are documented to do, and marks the points where an editor should approve before anything moves on.

Four different things called "AI editing"

The phrase covers four jobs with different risks. Most of the confusion comes from mixing them up.

Generation raises its own questions about provenance and disclosure, so we leave it aside here. The other three often work as a chain: search finds the material, an agent decides what to do with it, and the editor's tools carry it out.

The difference between the middle two rows matters more than it looks. An assistant inside Premiere works within Adobe's product and its credit system. An external agent is your choice of model, connected to the editor through the Model Context Protocol (MCP), an open standard that lets an assistant use another app's tools. The same agent can read your notes, a script or a footage library before it touches the timeline. See what MCP is for the basics.

One request, end to end

Here's what happens when you ask an agent connected to an editor for a highlight edit. The steps are the same in every tool below; only the tool names change.

1. The brief. You type a request in plain language: "Make a 60-second highlight from the panel recording. Keep the answers about funding. Drop anything under a second. Render H.265."
2. Reading the project. The agent can't see your screen. It calls tools that describe what's there: timelines, clips, durations and, where the editor offers them, transcripts. Everything it knows about your footage comes back as text from those calls.
3. The plan. The model decides what "highlight" and "about funding" mean, usually from transcript text, and turns your brief into a list of ranges.
4. Tool calls. The agent asks the editor to act, one call at a time: create a timeline, add these ranges, remove the short clips, queue a render.
5. A reviewable change. The editor carries out each call. You end up with something you can inspect: a new timeline, a project file or a rendered file.

A trace of step 4 looks roughly like this. The tool names are made up for illustration; each editor names its own.

list_timelines()
get_transcript("Panel full")
create_timeline("Highlight v1")
append_ranges("Highlight v1", [ranges from the plan])
remove_clips_shorter_than("Highlight v1", 1 second)
add_render_job("Highlight v1", "H.265")

Two things stand out. First, the creative decision happened in step 3, inside the model, mostly from text. Nothing in the trace knows whether a line was delivered well. Second, how easy the result is to review depends on the tool. Adobe says the Premiere assistant produces an editable sequence, with every action recorded in Premiere's undo and history. Edits' product lead describes a project file you open in Edits and keep editing by hand. A code route writes new media files.

Ask the agent to report what it did: each range, its source timecode and why it chose it. That list is quicker to review than the timeline, and it's where a bad interpretation of "highlight" shows up first.

What each tool can do today

"Documented" below means a vendor page or reputable report says so, as of November 11, 2026, not that we've confirmed it ourselves.

Premiere Pro

Adobe's AI Assistant entered public beta on June 18, 2026. Adobe's beta announcement lists what it does now: create and organize bins, rename clips, apply color labels, generate transcripts, detect slates, add markers and build a stringout or rough assembly. Versioning, cut-downs and working from a script or production notes are listed as not yet available. Beta users get free daily credits, separate from paid Creative Cloud credits, and Adobe recommends trying it on a duplicate project.

At Adobe MAX on November 10, Adobe said it is previewing local MCP integrations for Premiere, Photoshop, Illustrator and After Effects, so that a third-party agent can edit native project files with sequences staying editable. That's a preview, not a shipping feature, and Adobe hasn't published pricing or a date. Community MCP servers for Premiere exist in the meantime; our tool table lists them.

Best for: Premiere editors who want help with project setup and first assemblies now.

Hand Off Clip Prep to the AI Assistant in PremierePlays on YouTube

DaVinci Resolve Studio 21.1

Blackmagic released Resolve 21.1 on September 8, 2026 as a free update. Its announcement describes assistants reviewing projects, sorting media, changing settings and running batch renders, including building highlight edits from long-form footage and removing unwanted clips. Digital Production reports that the native MCP server is in the paid Studio edition and is set up from File > Setup AI Assistants. It also notes that Blackmagic hasn't explained permissions, logging or safeguards for destructive operations. A new preference sets whether AI tools use full-resolution media or follow your proxy setting.

Best for: editors who already finish in Resolve and want an outside agent working in the real project.

What’s New in DaVinci Resolve 21.1Plays on YouTube

Edits for Mac

Instagram released its Edits editor for Mac on November 5. The Verge reports a multi-track timeline, keyboard shortcuts and an MCP covering the app's tools. Matthew Simari, who leads product for Edits, told The Verge that any agent can use it, including Meta's Muse. He described an agent making a rough cut from a video in your downloads folder, which you then open in Edits to keep working. iClarified reports that the app is free, needs an Apple silicon Mac and an Instagram account, and that MCP is turned on in Settings. Publishing goes straight to Instagram, and projects can't yet move between the phone and desktop apps.

Best for: creators cutting for Instagram who want to switch between agent and manual editing in one app.

Descript

Descript's MCP connector lets Claude, ChatGPT or another MCP client run what you'd ask its Underlord agent for inside Descript: captions, Studio Sound, removing filler words and retakes, overlays, reframing and translation. It exports transcripts, and timelines as EDL, AAF, FCPXML, Premiere XML and Resolve XML, which is a practical way to move an agent's assembly into another editor. Descript says the connector can't yet hand back an MP4 on request. There's no separate charge for MCP, but it uses your plan's AI credits, and Descript warns that automated editing uses them faster than editing by hand.

Best for: interviews, podcasts and talking-head pieces where the transcript is the edit.

What is an MCP? (And How It Makes You a Better Video Editor)Plays on YouTube

Code and FFmpeg

A coding agent such as Claude Code or Codex can run FFmpeg directly to trim, join, crop and burn in captions. Kinocut, formerly mcp-video, wraps those operations as a local MCP server, writes new files by default rather than overwriting, and is open source under Apache 2.0. The output is media files, not an editable timeline, unless you also ask the agent to write an EDL or FCPXML your editor can import.

That last step is the route documentary editor and director David Barry describes on his website. He says the workflow comes from editing a feature documentary with 250 interviews. SRT transcripts become clean, searchable spreadsheets. Soundbites are found by keyword. AI proposes themes and structure, and the edit arrives in DaVinci Resolve as a generated CMX 3600 EDL. The page, which sells his book on the method, pitches AI "as a true assistant editor." The division of labor is the useful part: the AI logs, searches and drafts a structure, and a person cuts from there.

Best for: fast string-outs, versions and social cut-downs, and editors comfortable reading what a script did.

Search comes before the timeline

Every editor integration above works on media that's already in the project. On a real job, getting the right material into the project is often the bigger task: the answer from the second shoot day, every take of a line, the B-roll that covers a sentence. That's where the fourth category does its work.

• Inside the editor. Jumper runs as a plugin for Premiere Pro, Final Cut Pro, DaVinci Resolve and Avid Media Composer. It searches speech and picture on your device, and its Pro tier adds agentic editing for Claude, ChatGPT and Codex.
• With files you already have. Transcripts exported as SRT can be searched across every connected drive. See how to find one line in hours of interview footage.
• Across a whole archive. A footage library an agent can query before it builds anything. Grain Photo, which we make, catalogs drives in place and transcribes video on your Mac, so a connected agent can search what was said, read timed transcripts and find B-roll across drives, including ones that are unplugged.

An agent that assembles from a selects list you've approved makes fewer choices you'll have to undo.

Where editors should keep control

Agents are fast at mechanical changes and confident about creative ones. Rather than watching every tool call, set a few approval gates and let nothing pass one without you.

1. Source selection. Decide which media the agent can use. Approve the selects list, with source timecodes and the reason for each pick, before anything goes on a timeline. In Resolve, decide whether AI tools work from originals or proxies.
2. Structure. Approve a paper edit, the order of beats, before assembly. Reordering a list is cheap. Reordering a timeline isn't.
3. Picture. Performance, reactions, cut points and pacing. Agents work largely from transcript text and metadata, so check every in and out, and check what a rule like "remove short clips" actually removed.
4. Sound. Dialogue edits on a breath, room tone, music and levels. An agent can normalize loudness. Only listening tells you whether a dialogue edit is clean.
5. Delivery. Specs, captions checked against the audio, rights for music and footage, and disclosure of any generated material. Start the final render yourself.

A few working rules make the gates easier to keep:

• Work on a copy. Use a duplicate project or a new timeline for every agent session. Adobe recommends duplicates for the Premiere beta, and undo history isn't a plan.
• Ask for a change log. Have the agent list each change it made and why. Review the list, then the timeline.
• Know where data goes. Whatever the agent reads, including transcripts, previews and project data, goes to its model provider under that provider's terms. Descript projects live in Descript's cloud.
• Watch the credits. Adobe's beta credits, Descript's AI credits and your model subscription all count against long jobs.

Words you'll see

• Agent: a model that plans a task and calls tools in a loop until it's done.
• Tool and tool call: one action an app exposes to an agent, such as "create timeline", and the agent's request to run it.
• MCP: the Model Context Protocol, the open standard that connects agents to apps' tools. See what MCP is.
• Skill: a packaged set of instructions, and sometimes scripts, that an agent loads for a kind of task.
• Transcript: timed text of what was said. SRT is the common file format.
• EDL: an edit decision list, a plain-text list of source clips and timecodes. CMX 3600 is the long-standing format most editors import.
• FCPXML: Final Cut Pro's XML format for projects and timelines, also read by other tools.
• Native project: the editor's own project, where every clip, effect and sequence stays editable.

For a fuller reference on agents, skills and MCP across creative apps, see agents, MCP and creative software. To choose a stack, see what each tool can do today.

How we put this together

We built this piece from vendor announcements, documentation and published reporting, checked on November 11, 2026, and have not run hands-on tests of these tools; beta and preview features change often, so check the linked source before relying on a detail.