Making video with coding agents

Free lesson

What Claude Code and Codex are

Lesson 1 of 10 in Making video with coding agents.

Checked against the makers' documentation on 26 September 2026.

What is Claude Code? · Claude
Introducing the Codex app · OpenAI
Lesson

Claude Code, from Anthropic, and Codex, from OpenAI, are the same kind of tool. Each one works inside a folder on your computer, where it reads the files, runs commands in your terminal and edits code, and each stops to ask before doing anything its settings do not already allow. That is what separates them from a chat window. A chat window sees only what you paste into it and hands back text for you to copy, run and paste again, while an agent runs the script itself, reads the error and tries a fix, so the round trip of copying between two windows is gone.

A session runs in a loop you can watch. You open a terminal in a project folder, start the agent and describe the job in ordinary sentences. It reads the files it thinks are relevant, says what it plans to do, and then works through the plan one action at a time, printing each command and each edit as it goes, and it stops to ask whenever an action needs your permission. Take a job this module builds up to. You have a CSV of twelve shots and want each one rendered on Veo Lite, retried after a server fault and saved under its shot number. The agent writes the script, runs it in a dry-run mode that prints the twelve requests and their cost without sending them, because your brief asked for one, and waits for you to say go.

Both come in several forms that share one engine. Claude Code runs in the terminal, as an extension for VS Code, Cursor and the JetBrains editors, in the Code tab of the Claude desktop app, and in a browser at claude.ai/code, where the work happens on Anthropic's machines against a GitHub repository instead of on yours. Codex runs in the terminal as the Codex CLI, as an extension for VS Code, Cursor and Windsurf, inside the ChatGPT desktop app, and in the cloud at chatgpt.com/codex. This course uses the terminal versions. They show every command before it runs, and the settings you write apply to every form that runs on your own machine.

Each agent also reads a file of standing instructions from the project folder before your first message. Claude Code looks for CLAUDE.md and Codex for AGENTS.md, and both are plain Markdown notes you write yourself. A video project's file might say where the keys live, which model and resolution to use for drafts, how finished clips are named, and that nothing which spends money runs without a person's yes. Write it once. Every session then starts from the same rules instead of from whatever you remembered to type that morning, and a colleague who opens the folder gets those rules too.

Permissions are where the two differ most. Codex starts with a that cuts off the network and keeps writes inside the project, and in a folder without git it suggests read-only. Claude Code on a Pro, Max or Team plan starts in auto mode, where a second model reviews each action instead of you, while on Enterprise or an API key it starts in manual mode and asks. Both let you widen or narrow what they may do in a settings file, and both show a prompt when an action falls outside it. Read those prompts before you approve. For a folder of scripts that spend money, the setting that matters most is the one deciding whether a render command can run without you.

Neither is free for this work. Claude Code needs a paid Claude plan or a Claude Console account, and Anthropic's pricing page lists Pro at $20 a month ($17 a month if you pay $200 for the year) and Max from $100 a month for five or twenty times Pro's usage, with Claude Code drawing on the same allowance as your chats, counted in five-hour windows with weekly limits on top. Codex comes with ChatGPT Plus at $20 a month and Pro from $100, while the Free and Go plans list it in the desktop app only, subject to rollout. Either agent can run on an API key instead. That bills per token, at $2 per million input tokens and $10 per million output tokens for Anthropic's Sonnet 5, and OpenAI's page says an API key loses Codex's cloud features.

chat windowyou paste codeit writes textyou run it, paste the erroryou carry every stepcoding agentyou write a briefit reads the filesit runs a commandit reads the resultit asks before anything notallowed
A chat window against a coding agent: in a chat you paste code, copy the answer, run it and paste the error back, carrying every step; an agent reads the files, runs a command and reads the result itself, asking before anything it is not allowed to do.
An ink drawing seen from above of a storyboard on a desk, a small robotic arm placing film canisters into a row of slots, and a hand resting on a large red stop button.
The agent does the handling. Your hand stays on the stop button.

Side by side

Claude Code and Codex, row by row

Claude CodeCodex
Instructions file it readsCLAUDE.md in the project folder and the folders above it, plus your own ~/.claude/CLAUDE.md.AGENTS.md, from ~/.codex/AGENTS.md and then one per folder, from the top of the git repository down to where you started.
Cheapest plan that includes itClaude Pro, $20 a month, or $17 a month paid for the year. The free plan has no Claude Code.ChatGPT Plus at $20 a month. The Free and Go plans list it in the desktop app only, subject to rollout.
How a new session startsAuto mode on Pro, Max and Team, where a classifier model approves each action. Manual on Enterprise and on an API key.It suggests Auto in a git folder, editing inside the project and asking before the network, and read-only in a folder without git.
What it may touch by defaultWhatever auto mode allows, and its default list includes reading .env and sending credentials to their matching API.Network off and writes kept inside the project. In our throwaway folder it still read .env without asking.
Where your login livesSaved after a browser sign-in. Type /status to see the account and the method in use.In ~/.codex/auth.json as plain text, unless config.toml sets cli_auth_credentials_store to keyring. codex login status shows the method.
If an API key is in your shellIt asks once about ANTHROPIC_API_KEY, and after a yes it bills that key at API rates even though you pay for a plan.It uses a key only if you log in with one, such as by piping OPENAI_API_KEY into codex login --with-api-key. That bills per token and drops the cloud features.
Version on npm, 26 September 20262.1.283, as @anthropic-ai/claude-code0.157.1, as @openai/codex

Prices from claude.com/pricing and OpenAI's Codex pricing page, and versions from npm, read on 26 September 2026. The defaults were tested on 25 September. Both tools ship new versions most weeks.

What to do it with

  • Claude CodeSubscription

    An agent that reads a whole repository, edits files, runs the tests and explains what it changed.

    Bad at It is fast enough to make a large mistake quickly. Work on a branch, read the diff, and never let it push. Watch the starting mode: on Pro, Max and Team plans it opens in auto mode, which Anthropic's own list says may read a .env file and send the key in it to the API that key belongs to. Switch it off.

  • CodexSubscription

    A coding agent that runs locally in a sandbox, reading a project, editing files and running commands; also in the ChatGPT desktop app, IDE extensions and the cloud. Included with ChatGPT Plus ($20) and Pro (from $100), or billed per token with an API key.

    Bad at By default its sandbox still lets commands read `.env`, and it passes every environment variable (keys included) to commands unless `ignore_default_excludes = false`. Docs and CLI disagree in places, and tutorials go stale fast (the `untrusted` approval policy is retired).

  • ClaudeFree tier, paid above it

    A language model that writes, edits, reads long documents and runs tools, including agents that work inside a codebase.

    Bad at It is agreeable by default, so it will improve a bad idea instead of telling you it is bad. Ask it to argue against you and the quality of the answer changes.

  • ChatGPTFree tier, paid above it

    General assistant with image generation, data analysis and web access in one window.

    Bad at Its default voice has become recognisable enough that readers now spot it, which is a brand problem if you ship it unedited.

The whole tool directory

The words, in plain language

Coding agent
A program that reads your files, runs commands and edits code on your machine, asking first.
Surface
One of the places the same agent runs: a terminal, an editor, a desktop app or a browser.
Permission prompt
The agent stopping to ask before an action its settings do not already allow.
Plan usage
Agent work paid for by a monthly subscription, from an allowance that resets every five hours.
API billing
Agent work paid for per token from a developer account, separate from any subscription.
CLAUDE.md and AGENTS.md
Plain notes kept in the project folder, which Claude Code and Codex read before your first message.
Sandbox
A fence the operating system puts round the agent's commands, limiting the files and network they can reach.

Why it matters

An agent earns its place in the plumbing around generated video. Batch scripts, retry logic, file naming, contact sheets, ffmpeg cuts and cost logs are dull, precise work that it does well and that a designer rarely wants to learn by heart. It adds nothing to the prompt itself, and left alone it may tidy your carefully weighed camera language into something plainer. Keep the words yours. Let the agent build the machine that sends them.

The money traps are specific. If ANTHROPIC_API_KEY is set in your shell, Claude Code asks once whether to use it, and after a yes it bills that key at API rates even though you pay for a subscription; the docs add that a key from a disabled organisation then makes sign-in fail. Codex keeps its login in a plain text file at ~/.codex/auth.json unless you tell it to use the system keychain. Subscription limits are shared. A long agent session on Pro draws on the same five-hour allowance as your chats in the Claude app, so an afternoon of scripting can use up what your writing needed.

Pick one and learn it properly. The two are closer than their marketing suggests, and everything in this module works in both. People who use both argue about which writes better code, and for this work the plan you already pay for matters more than that argument. The costlier mistake is trusting either one unwatched. An agent allowed to run renders on its own can decide a take looks wrong and make it again, and Veo bills every clip it actually generates, so a loop nobody is reading can spend a day's budget before anyone looks up. This module holds one line throughout. The agent writes the script, runs it dry and explains what it will spend, and a person presses go on anything that costs money.

The rest of the module builds a working video crew from these two tools. You install one and run a first session, then write the standing-instructions file for a video project and learn to brief an agent so that it never has to guess. From there the agent turns a shot list into a batch of renders, lays the takes out on contact sheets so you can judge them side by side, and cuts and joins clips with ffmpeg. MCP servers come next. They add tools the agent can call by name, such as searching the Hugging Face Hub. The module finishes on checking exactly what the agent changed, and on keeping your keys and your money out of its reach.

Elsewhere


Type
technique
Period
ongoing

Check what stuck

Elsewhere in the library

Hear about new courses.

Leave an email and we will tell you when something new lands. We do not write often.