A sofa, a plain wall behind it. A beat later the wall is a rooftop at dusk. The person on the sofa and the camera's slow push don't move; only what's behind them changes. That's the clip above, and it's the kind of shot "codex premiere pro" searches are usually asking about: can a terminal coding agent actually make that happen inside Premiere?
What the Codex CLI is actually good at
Codex CLI is a command-line agent built for writing and running code. Point it at a problem with a clear script to write, and it writes a good one. That's genuinely useful for Premiere Pro work: an expression, a panel script, a batch rename, a small automation aimed at whatever scripting or extension layer the host exposes.
What it doesn't have, by itself, is a way to see inside Premiere's window. It can write the script; it can't watch the timeline update, confirm the edit matched the brief, or notice that a clip landed one frame off. That gap exists whether Codex is running in a plain terminal or anywhere else it has no project to look at.
Why "it can write the script" isn't "it can edit the video"
Three things have to be true for an agent to actually finish a cut, not just hand you code to run:
- It can look. Check a frame before trimming it, not guess from a filename or a script's own assumptions.
- It can act on a real timeline, placing and trimming clips in the project itself, not in a file it hopes a script applies correctly.
- It can generate or fix a shot and put the result back, instead of leaving you to drag a rendered file onto a track.
A script Codex writes and you run can satisfy none of these on its own. It's still homework delivery, just well-written homework.
The route that gives Codex a real timeline
Shoty is a desktop video editor (Mac and Windows) with an agent chat built in. Pick ChatGPT · my subscription in the model picker and Shoty runs the official Codex CLI on your machine, signed in with your own OpenAI account, with no fee from Shoty for the agent itself.
- For each turn, Shoty opens a local MCP server and hands Codex 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 Codex is reading and editing a structure the way it reads and edits code, instead of hoping a script executed cleanly inside someone else's app. - When the cut is done, Shoty exports it as EDL, FCPXML or OpenTimelineIO, the formats Premiere Pro, DaVinci Resolve or Final Cut Pro open for the finish.
1. Ask for the part Codex is actually good at
Write a batch of clean, numbered filenames for these clips so the project reads in order, then cut the dead air out of the first five minutes.
Scripting-style thinking carries over well to a timeline it can actually touch.
2. Name what must not change on a VFX fix
Replace the wall behind the sofa in shot 2 with a rooftop at dusk. Keep the person, their pose and the camera's push exactly as they are.
3. Export for the host you're finishing in
Export this project as an EDL for Premiere Pro.
Where this still needs you
- Judging the cut. Codex can draft and execute fast; which beat actually lands is still an editor's call, and you can always grab the Shoty timeline and trim by hand.
- Approving generated shots. Anything sent to a video model costs credits, so set the run mode to review if you want to sign off before it renders.
- Anything outside Shoty's tools. A Codex script aimed at Premiere's own scripting layer directly is still a one-way push with no confirmation it worked; that limit doesn't go away, it's just not the route this guide is about.
Download the free Shoty editor and pick ChatGPT (Codex CLI) from the model picker. For the Claude Code version of the same setup, see Claude Code Premiere Pro.