How to edit video with Codex: the three routes and the setup that works

Search for “edit video with Codex” and you get a handful of tutorials, each built on one stack: a Remotion project, an agent skill, or a vendor’s plugin. None of them explains the part that decides whether it works for you, which is how Codex connects to the thing doing the editing. This guide covers that part, with every setting checked against OpenAI’s documentation on October 12, 2026.

Can Codex edit video?

That distinction matters more than the model. With code, Codex produces a new file each time and never sees a timeline. With a plugin, it works inside someone else’s cloud. With an MCP editor, it edits a project that stays open in front of you. The rest of this guide is about choosing between those and setting up the one you pick.

What are the three ways to edit video with Codex?

The routes differ in where your footage goes and in what Codex can check before it tells you it is done.

Code is the route in most viral posts. Codex reads a transcript, writes an ffmpeg command or a Remotion component, and renders. It is free beyond your Codex plan and very flexible. The cost shows up later: one author who edited a whole video this way wrote, as a professional video producer,

Cloud plugins hand Codex a vendor’s editing tools. CapCut ships an official one, and our guide to connecting Claude and Codex to CapCut covers how it works, including the network check that blocks sign-in in the United States. You get the vendor’s templates and effects, and your footage lives on their servers.

A desktop editor over MCP exposes its timeline to Codex as tools: add a clip, cut a range, caption, export. The project stays open, so you can watch, undo, or change something yourself and ask Codex to carry on. Rushilo, which we make, is built this way; so are a few others.

How does Codex connect to an MCP server?

According to OpenAI’s MCP documentation:

• A local (STDIO) server needs a command, and can take args, env and cwd. A remote server uses a url and signs in with OAuth.
• You can add a server from the terminal with codex mcp add <name> --env VAR=VALUE -- <command>, or in the desktop app under Settings, MCP servers.
• /mcp inside Codex, or codex mcp list, shows which servers are connected.
• A project can carry its own .codex/config.toml, used only in projects you have marked as trusted.

MCP servers are not the same as plugins or skills. A skill is a set of instructions Codex reads; a plugin can bundle skills and MCP servers together. OpenAI’s plugin docs note that plugins work in the desktop app and the CLI, but the IDE extension does not support them. A plain MCP server in config.toml works everywhere.

How do you set up Codex with a video editor, step by step?

These steps use Rushilo as the example. The Codex side is identical for any local MCP video editor; only the block you paste changes.

1. 1Install Codex (the ChatGPT desktop app or the Codex CLI) and sign in with your ChatGPT plan or an API key.
2. 2Install Rushilo and open it. It has to stay open while Codex works, because Codex talks to the running app.
3. 3In Rushilo, choose Connect agent and copy the Codex block. It already points at your install, so do not type it by hand.
4. 4Paste it into ~/.codex/config.toml and save.
5. 5Start a new Codex session and run /mcp. You should see rushilo listed as connected.
6. 6Try one small edit first: one clip, one cut, and ask Codex to look at two frames around the cut to prove it landed. Then move to the full video.

[mcp_servers.rushilo]
command = "<path to Rushilo, filled in by the app>"
args = ["<path, filled in by the app>"]
env = { ... }
tool_timeout_sec = 3600

If the server does not appear, restart Codex and open a new session; Codex reads the config when a session starts.

Why does Codex stop in the middle of a render?

We hit this ourselves while building Rushilo’s Codex support. With the default, Codex gave up on long tools after a minute and could try again, starting the same work twice. That is harmless for an export and expensive if the tool is a paid transcription call on your own API key. The fix is one line: set tool_timeout_sec for your video server. Rushilo’s copied block sets 3600 seconds, an hour.

What will Codex ask permission for?

By default Codex runs in a sandbox with no network access and writes limited to your workspace, according to OpenAI’s approvals and security docs. MCP tools are handled separately: destructive MCP tool calls always ask for approval when the tool marks itself as destructive, and each server can set an approval mode such as asking only for writes.

For video this is a sensible default. Let Codex read the project, the transcript and frames freely, and approve the steps that change or delete things. A good editor makes every change undoable anyway; in Rushilo, your edits and Codex’s share one undo history, and Codex can save a named version before a big change.

Which ChatGPT plans include Codex, and how fast does editing use your limit?

OpenAI’s Codex pricing page lists Free, Go, Plus, Pro, Business, Enterprise and Edu, and API key access. Some guides still say you need a paid plan; the official list says otherwise, with different usage limits per plan. Two practical points:

• OpenAI says every MCP server adds context to your messages and uses more of your limit, and suggests turning servers off when you are not using them.
• Video editing is mostly cheap work for the model: reading a transcript and issuing cuts. The expensive part is anything that sends images back, such as asking to see frames. Ask for frames at decision points, not after every cut.

Your editor can add its own costs. Rushilo charges nothing per edit: it is $99 once, captions can run on your computer for free, and anything that calls a paid service, such as a voiceover, uses your own key.

How do you make Codex check its own edit?

Codex will tell you an edit worked whether or not it did. The fix is to give it a way to look. An editor that returns frames as images lets Codex check its own cut; a transcript lets it check that it removed the right words. A short verification habit catches most mistakes:

1. Ask Codex to read the word-level transcript before cutting, and to cut by words, not by guessed times.
2. After each batch, ask for one frame just before and one just after a cut.
3. Before export, ask it to list every cut with its timestamp so you can spot-check two or three.

The author of one popular Codex editing guide found the model “will generally do the minimum amount of editing required by your prompt”, so be specific: say how long pauses may be, which words to keep, and what the final length should be.

When should you not use Codex for video?

When the edit is about taste. Pacing a story, choosing the best take by feel or cutting to music are decisions Codex makes poorly from a transcript. The pinned answer in r/VideoEditing to “isn’t there an AI that magically edits everything?” is still the honest one:

Where Codex earns its keep is the repetitive part: cutting silences and retakes, captioning, resizing one video for several platforms and syncing pictures to a voiceover. A comment on the most popular Codex editing thread in r/codex put the demand plainly:

That is exactly the work to hand over. Keep the creative calls for yourself, and use an editor where you can see what Codex did and take over at any point. The setup guide covers connecting Codex, Claude Code and other agents to Rushilo.

Patel, O. (2026, October 12). How to edit video with Codex: the three routes and the setup that works. Rushilo. https://rushilo.com/blog/edit-video-with-codex

About the author

Om Patel

Founder, Rushilo

Om Patel is the founder of Rushilo, a desktop video editor driven by the user's own AI, and of BigIdeasDB, a research platform that reads real complaints and reviews to help founders validate products. He writes Rushilo's research articles with the same method: primary sources, dated numbers and the words real users write.

• X (Twitter)
• BigIdeasDB