An AI agent that operates DaVinci Resolve

What the agent does inside Resolve

The Resolve plugin is a two-way bridge between EditAssist and the edit page, colour page, and deliver page. The agent reads the current timeline and media pool, then executes real operations: adding and trimming clips, placing and labelling markers, building selects and assembly timelines, running colour-grading operations (node trees, LUTs, CDLs, power windows), and queueing renders to your delivery presets. It can read render-queue status back to you, and because the bridge exposes Lua execution, anything Resolve's scripting API can do, the agent can drive too.

• Timeline read/write

  Add, trim, reorder, and mark clips on any timeline.

• Colour operations

  Node trees, LUTs, CDLs, power windows, reference matching.

• Render queue

  Queue jobs to delivery presets and report status back.

• Media pool access

  Browse, search, and pull clips into the cut.

• Multi-instance

  Drive several open Resolve projects at once.

• Lua execute

  Reach the full scripting API for anything bespoke.

How the plugin works

EditAssist runs as a single agent on your machine. The Resolve plugin connects that agent to the running Resolve instance, so the cut you see and the cut the agent operates are identical: the same project state, the same media, in real time. It is multi-instance aware, so if you have several Resolve projects open, the agent can discover and address each one, and colour and conform work on one project won't collide with an edit in another.

You don't have to sit inside Resolve to use it. The same agent is reachable from the EditAssist desktop app, a Telegram message from set, or the terminal, and whatever you ask for lands in your live Resolve timeline.

Commands you can give it

You edit by describing the outcome. A few Resolve-specific examples:

• “Apply the show LUT to every clip on the timeline and render a ProRes 4444 master.”

• “Add a power window to the sky on the wide shots and push it two stops warmer.”

• “Match the grade from this reference still across the whole reel.”

• “Apply the CDL values from the colourist's report to every graded clip.”

• “Build a selects timeline from every close-up of the lead and colour-match to episode 3.”

• “Check the render queue and tell me how long the current job has left.”

• “List every marker on the timeline and export them as a CSV for the producer.”

• “Conform the locked AAF from Avid into Resolve and flag any relink mismatches.”

Hundreds more across every workflow live in the prompt library.

Grading, conform, assembly and delivery

Resolve is where EditAssist's colour and finishing strengths land hardest. Colour matching works from a reference still, a LUT, or a CDL, and the agent can apply it across a whole reel rather than clip by clip. For finishing, it conforms offline edits to camera originals through FCPXML, FCP7 XML, and CMX3600 EDL, validating relinks as it goes. For delivery, it builds render jobs against 32 delivery specs and queues them to Resolve's render queue.

Behind all of that, semantic search indexes every frame and transcribes every word, so the agent can assemble rough cuts and selects timelines from intent (say, “build a selects timeline of every close-up of the lead”) and drop them straight onto a Resolve timeline. Audio sync, loudness checks, and multi-cam all feed the same pipeline.

Local-first by design

Transcription, vision analysis, embeddings, and search indexing all run on your own GPU. No frames are uploaded and no media is sent to a server. The only thing that leaves your machine is the text of your conversation with the agent. Your client's footage, your project files, and your grades stay on your hardware. EditAssist runs on macOS (Apple Silicon, Metal) and Windows (x64, CUDA).