DaVinci Resolve 21.1 Lets an AI Agent Drive the Edit. Here Is What to Hand It, and What Not To.

What is new in DaVinci Resolve 21.1?

DaVinci Resolve 21.1, released on 8 September 2026, adds a built-in MCP server that lets AI assistants such as Claude and ChatGPT Codex control Resolve through natural-language requests. The agent integration is Studio-only. The update also brings 25-plus new Fusion tools, faster deep compositing and separate Dolby Vision, HDR10+ and HDR Vivid trim passes.

That is the summary. The rest of this piece is about what it means on a Tuesday afternoon in an edit suite, a DIT cart or a two-room grading house.

What the MCP server actually is

MCP, the Model Context Protocol, is described in its own documentation as "an open-source standard for connecting AI applications to external systems" — a common way for an assistant like Claude or ChatGPT to reach tools and data rather than only talk about them. Resolve 21.1 is now one of those external systems.

CG Channel's release write-up says the server connects Resolve "to external AI tools like Claude and Codex", so users can control the software with natural-language commands instead of hunting for the right panel, and names media organisation and highlight reels as suggested uses. Digital Production and Y.M.Cinema both report that setup runs through File > Setup AI Assistants, after which Resolve detects compatible assistants and configures the server; the conversation then happens in the assistant's own chat window, not inside Resolve.

Digital Production describes Blackmagic's own demonstration: an assistant takes a long video, cuts a three-minute highlight edit, removes edits shorter than one second and renders the result as H.265 for review. Y.M.Cinema lists further examples from the manual — rendering one timeline as ProRes 422 HQ, H.265 4K and an H.264 proxy in one go, renaming clips sequentially, adding coloured markers and exporting them to CSV, applying an S-Log3-to-Rec.709 LUT to specific nodes, and comparing settings between projects.

The rest of the release, briefly

For compositors, CG Channel reports more than 25 new Krokodove tools in Fusion, a Camera Tracker that can import external tracks, flipbook previews for deep compositing, and hardware-accelerated deep renders in Renderer3D that are "up to 8x faster". For colourists, the MultiMaster Trim manager now handles separate passes for Dolby Vision, HDR10+ and HDR Vivid, and a new ResolveFX Panomap node works with spherical and hemispherical footage. If your work leans toward that side, our piece on where AI actually sits in the VFX pipeline is the longer context.

One change matters to anyone who already automates Resolve: CineD and Digital Production report that advanced Python scripting has moved from the free edition to Studio. Digital Production says the scripting API remains available from the console in the free edition, and gives Blackmagic's reason as the API having been used to unlock Studio features.

Which tasks to hand to an agent, and which to keep

The sensible test for any task is three questions: is it repetitive, can a person check the result quickly, and can it be undone? If all three are yes, it is a candidate. If any is no, a person keeps it.

The pattern is that an agent is best treated like a fast, new assistant: good at the list-shaped work, never trusted with the only copy of anything.

A pre-flight checklist for a post house

Before an agent touches a client project, work through this once:

1. Licence. Confirm every seat that will run it is on Resolve Studio 21.1. The free edition does not include the integration.
2. Duplicate first. Run every new kind of request against a copied project, never the live one, until you have seen the output enough times to trust it.
3. Media stays read-only. Camera originals and the backup set should be on volumes the agent's user cannot write to. Blackmagic's own warning, quoted by Y.M.Cinema, is that "scripts created by an AI assistant have the same access permissions to disk, network and other system resources as the assistant itself."
4. Read the provider terms. Know what your AI provider stores and for how long, and whether project metadata, transcripts or frames leave the building.
5. Check the client contract. Many post agreements restrict who and what may handle footage. An AI service is a new party; ask before, not after.
6. Log what was asked. Keep the prompt and the result for anything that touched a deliverable. Digital Production notes that logging, permissions and access in shared environments are not yet clearly addressed.
7. Name a human owner. Every agent-run task has a person who checks it and signs it off.

If your team already works across locations, the same access questions apply as in remote post-production collaboration, just with a non-human collaborator added.

Who gains, and who is exposed

Assistant editors gain the most time and carry the most risk. Binning, renaming, markers and render queues are a large share of the job, and they are exactly the tasks listed above. The skill that grows in value is knowing what correct looks like fast enough to check an agent's work. The editor role page covers the path this sits on.

DITs gain on repetitive render and proxy set-ups, but their core promise — that the media is safe and verified — is not something to delegate. An agent with write access near the originals is a new risk on the cart. See the DIT role.

Colourists gain on housekeeping and on the new separate HDR trim passes, which are a feature rather than an agent task. The grade itself is judgement, as our guide to what a colourist does lays out. More on the colourist role.

Small post houses gain leverage, but they are the least likely to have an IT person setting permissions and reading provider terms, so the checklist falls on the owner.

What this does not tell you

No published data yet measures how accurately these agents bin, sync or cut in real projects, and demonstrations are chosen to succeed. Reports so far describe what an agent can be asked to do, not how often it does it correctly. We found no figures on error rates, and we have not tested the integration ourselves. Treat any productivity claim, including the ones implied here, as a hypothesis to test on your own footage.

What it costs

CG Channel reports that the base edition of Resolve stays free and that Studio costs US$295 for a new licence, with 21.1 a free update for existing users; Digital Production lists Studio at €305 in Europe. Because the agent integration is Studio-only, that licence is the price of entry, before whatever your AI assistant subscription costs. For how Resolve fits alongside the rest of a post workflow, see our post-production software page.