Claude Code + DaVinci Resolve: a guide to editable Fusion graphics

What the video establishes

Blackmagic’s Resolve 21.1 announcement confirms integration with AI assistants including Claude Code for supported project tasks. This companion explains a practical way to approach that integration and inspect editable Fusion graphics.

The video’s Resolve interfaces, model replies and graphic-building exchanges are illustrative worked examples. No successful native Resolve run, generated Fusion build or reopened project was independently established for this production. The infrastructure reference came from an After Effects example; the fictional Workshop Notes sequence was rendered from HTML. Treat the prompts below as starting briefs to test in your own project.

Prepare a separate demo project

Use the current official Resolve Studio download and documentation for your installed version. The video describes File > Setup AI Assistants as the native setup route; this menu path has not been checked against a running local installation here. Follow the actual configuration flow rather than copying an old community-bridge command.

1. Save any unrelated work and create a separate demo project.
2. Put reference media and exports in a dedicated folder.
3. Complete the current assistant configuration, restart the assistant if its installer requires it, and inspect the available Resolve tools.

Check the connection before a write

A configured server entry does not prove that the assistant can see the correct application or project. Start with a request that changes nothing, then compare the reported state with Resolve.

1. Ask: “Report the Resolve version, open project and selected timeline. Do not change anything.”
2. Check those names and settings against the open application.
3. If they do not match, resolve the connection before permitting an edit.

Build a small editable graphic

The video plans a 1920×1080 timeline at 30 fps and a Fusion Composition. Use Text+ for editable wording, Background and masks for panels, and Merge tools to combine them. These are the elements to inspect; a finished MP4 alone does not establish an editable node graph.

1. Provide more than one reference frame and describe the order in which elements appear.
2. Ask for separately named text, panels and shapes, plus a still before a full render.
3. Inspect the node connections and change one word manually. Confirm that the viewer updates while the rest of the layout stays intact.

Request one controlled revision

A useful revision identifies the element, the change and what must remain unchanged. Keep a saved version before the edit.

1. Try: “Inspect the existing nodes first. Change the peach Infrastructure panel to muted blue, change the small first label to Foundation and delay the lower block’s entrance by half a second. Preserve my manual text edit, the other elements and the total duration.”
2. Compare the before and after at matching points.
3. Check the panel colour, label, keyframe timing and editable text separately.

Plan the Workshop Notes sequence

Workshop Notes is fictional sample data. The planned twenty-second sequence moves from two source notes to a project page, then a question opening the supporting note, and finally the app name. It is a storytelling brief, not evidence of a real product or completed Resolve result.

1. Ask for one still from each of the four scenes.
2. Keep the same workshop question, answer and supporting note throughout.
3. Build separate compositions with named elements so one scene can change without rebuilding the closing card.
4. Review the full sequence to check readability and scene transitions, then inspect individual text controls again.

Save a project you can verify

A review video shows the picture; a project copy is what may preserve nodes and timing. A reopen check is part of the intended workflow, not a step demonstrated by this production.

1. Save the working project and export a separate project copy.
2. Reopen the copy in a separate test and inspect the compositions and text.
3. Keep the reference, review export and project version together so a later revision has a clear starting point.

The takeaway

Start with a read-only check, inspect the editable structure, make a small controlled revision and verify the saved project. A plausible animation is not proof that every step worked in Resolve.