Can Claude Code control Premiere Pro directly?

Not on its own. Claude Code is a command-line agent; it has no built-in way to click inside a desktop app like Premiere. People reach Premiere from an agent through the host's own scripting or extension tools, or by having the agent write expressions or panel scripts that a person runs. Neither gives the agent a timeline it can see and edit the way it sees code.

What is claude code davinci resolve, and is it different from Premiere?

Same problem, different host. DaVinci Resolve ships a Python/Lua scripting API an agent-driven script can call into. Either way, the agent is scripting the app from outside, not reading and editing a timeline directly the way it can inside Shoty.

How do I get an AI-edited cut into Premiere Pro?

Edit on a timeline the agent can actually read and write, then export a format Premiere imports: EDL, FCPXML or OpenTimelineIO. In Shoty, Claude Code edits the project directly over a local MCP server, and the cut leaves as one of those formats for Premiere to open.

Does this need a Claude API key?

No, if you're using Shoty. It runs the official Claude Code CLI on your machine, signed in with your own Claude account, and never sees the token. Anthropic's own plan limits and policies still apply.

Can Claude also drive DaVinci Resolve or Final Cut Pro the same way?

The export side works for all three: Shoty writes EDL, FCPXML and OpenTimelineIO, which Resolve, Premiere and Final Cut Pro all read. Resolve additionally ships its own Python/Lua scripting API, which is a separate route from the Shoty workflow above.

Claude Code Premiere Pro: Edit With an Agent, Finish in Premiere

"Cut the dead air out of this interview and get it into Premiere Pro." Say that to Claude Code in a chat window and you get a script to run or an explanation of how Premiere Pro's panels work. You still do the cut. Say the same thing to Claude Code while it's holding an actual timeline, and the cuts happen, then the project lands in Premiere Pro as an EDL. Same words, different result, because of what's on the other end of the sentence.

Can Claude Code actually drive Premiere Pro?

Honestly: not by itself. Claude Code is a command-line agent. It reads and writes files and runs commands; it has no way to click a button inside Premiere's window. The paths people use to bridge that gap are the same for Premiere as for any desktop NLE:

The host's own scripting or extension tools, when it has them. DaVinci Resolve, for instance, ships a Python/Lua scripting API, so a script an agent writes has somewhere to plug in; not every NLE exposes the same depth of access.
Community MCP servers that wrap an editor's scripting layer so an agent can call it as a tool. These exist for several NLEs; check what a given one actually exposes before trusting it with a real project.
Having the agent write the script or expression, and a person runs it inside the app. This keeps the agent out of the editing loop entirely; it's homework delivery, not editing.

None of these give Claude a timeline it can see, reason about, and edit the way it edits code. That's the actual gap "claude premiere pro" searches are running into.

The route that gives Claude a real timeline

Shoty is a desktop video editor (Mac and Windows) with an agent chat built in. Pick Claude · my subscription in the model picker and the shape of the problem changes:

Shoty runs the official claude CLI on your machine, signed in with your own Claude account. It never sees your token and charges no fee for the agent.
For each turn, Shoty opens a local MCP server and hands Claude tools: look at a frame, read and update the timeline, generate a shot, export. Every call shows up in the chat.
The timeline is a text format (.shoty), so Claude is reading and editing a structure, the same way it reads and edits code, instead of guessing at pixels or hoping a script fires correctly.
When the cut is done, Shoty exports it as EDL, FCPXML or OpenTimelineIO. That file is what Premiere Pro, DaVinci Resolve or Final Cut Pro opens for the finish.

The agent never touches Premiere directly. It edits a project Premiere can later read, which is the part the scripting-API route struggles to deliver.

1. Do the cut in Shoty, not in Premiere

Ask for the rough cut, the VFX fix, the subtitle pass, whatever Claude is actually good at, while the project is still in Shoty.

Cut the dead air out of the first five minutes, keep room tone under the cuts, and add burned-in English subtitles.

2. Name what must not change

If a shot needs a VFX fix before it leaves Shoty, say what stays fixed so the model doesn't repaint the whole frame.

Replace the hallway behind the two people in shot 4 with an office at night. Keep the walk, the camera move and both people exactly as they are.

3. Export for the host you're finishing in

Export this project as an EDL for Premiere Pro.

Ask for FCPXML instead if you're finishing in Final Cut Pro, or let Resolve's own scripting layer take it from an OTIO export if you want to keep scripting there too.

4. Finish where you already work

Color, mix and final delivery happen in Premiere like they always have. Shoty's job ends at the cut and the AI shots; Premiere's part of the job doesn't change.

Where this still needs you

Picking the beat. Claude finds every pause fast; which one actually lands is still a editor's call, and you can always grab the Shoty timeline and trim by hand.
Reviewing generated shots. Anything Claude sends to a video model costs credits, so set the run mode to review if you want to approve shots before they render.
Round-trips. If Premiere-side notes mean a shot needs to change again, that change happens back in Shoty, not by re-scripting Premiere.

Download the free Shoty editor and connect Claude Code from the model picker. For the general case, see how to edit video with Claude.