They add analysis to sim racing lap guides programmatically. Claude Code drives DaVinci Resolve three ways: timeline files, Lua scripts and computer use. Computer use burns tokens, but it works.
Result Works, though computer use is token-hungry
“I'm programmatically adding analysis to sim racing lap guides, therefore my flow is probably different from the usual editing flow, but I have to say I found Claude Code + Opus to be quite capable of making edits with computer use.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
Uses Claude Code to add analysis to sim racing lap guides in DaVinci Resolve: by generating .otio timeline files to import, by writing Lua scripts and running them through Resolve’s scripting engine with UI automation, and by controlling the app directly with computer use.
OTIO doesn’t support everything Resolve can do, and computer use is token-intensive, but it works: they found Claude Code with Opus quite capable of making edits through computer use.
I edit [type of video] in DaVinci Resolve. In the project [name], add [overlays, titles or markers] at these timestamps: [list]. Prefer a Lua script for Resolve's scripting engine. If a step can't be scripted, tell me and fall back to an .otio timeline I can import. Show me the script before running it.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.