The agent that makes the video
Setting up an open-source video production pipeline your coding agent directs end to end
You describe a video in one sentence and the agent runs research, script, scene plan, assets, edit and render — pausing for your approval at three gates and telling you the cost before it spends anything. There is a genuine zero-key path: free narration, free archival footage, free composition. One correction to the guide this came from: the project is AGPL-3.0, not MIT, which matters a great deal if you plan to build a business on top of it.
Claude Code is the orchestrator — there is no autonomous “press go” mode. The agent pauses for your approval at the script, scene plan and asset stages, and tells you costs before spending. Nothing is uploaded or published anywhere: “publish” means a local export folder. The guide this is built from was verified by cloning the repo at commit 08e2151 (5 Sep 2026), running the setup, and reading the agent guide and pipeline files.
What it actually is
An open-source video production system where your AI coding assistant is the director. You describe a video; the agent reads a pipeline manifest (YAML) and a set of stage “director skills” (Markdown), then calls the project’s Python tools to research the subject, write the script, plan the scenes, generate or fetch visuals, narrate, add music and captions, and render through Remotion or HyperFrames plus FFmpeg.
Eleven pipelines existed at the verified commit — animated explainer, documentary montage, cinematic, talking head, clip factory and more — and the current repository lists twelve. Every creative decision comes back to you for approval.
The guide states MIT twice. It is not: the repository ships the GNU Affero General Public License v3, both at the commit the guide was verified against and on the current default branch, and the project’s own README carries an AGPLv3 badge. The difference is not cosmetic — AGPL’s network clause means that if you run a modified version as a service for other people, you owe them your source. Fine for personal use; read it properly before building a product on it.
One sentence in, one file out
What works today, and what is still optional
What you need
Install it
The setup target creates the virtualenv, installs the Python requirements, installs the Remotion composer via npm, installs free Piper TTS, warms the HyperFrames cache, and copies the example environment file.
No make? The manual equivalent
On Windows PowerShell the README gives the equivalent. If npm install fails with ERR_INVALID_ARG_TYPE, use npx --yes npm install instead.
Connecting it to the agent
Nothing to install into Claude Code — the repository already contains its configuration. Open the folder and start the agent.
To see the real capability envelope at any time — what your particular keys unlock — ask the agent “what can you make with my current setup?”. The onboarding skill answers that directly rather than guessing.
Your first video, stage by stage
The fastest path is the zero-key animated explainer.
The zero-key first run
Straight from the project README — works with no API keys at all. Prefer real footage? Say so: “documentary montage, use real footage only, no narration.” The agent then pulls from Archive.org, NASA, Wikimedia and any free stock keys you added.
The copy-paste prompt
The long-form version, with the budget and no-publish rules stated explicitly.
Prompts worth trying
Nothing here auto-publishes; every one of them ends at a local file.
Where the video ends up
Project names are kebab-case from the title, e.g. why-the-sky-is-blue. The projects folder is git-ignored. A demo target renders zero-key demos, and the optional storyboard board shows the same folder live in your browser.
What it costs
Provider prices come from the project README and change — check your own provider. The figures below were re-checked against the README rather than copied.
config.yaml sets a $10 total cap, asks for approval on any single action over $0.50, and requires approval before any new paid tool. The default mode only warns on overrun — change it to a hard cap if you want the run to actually stop. Keys live in .env, which is git-ignored. All of that is genuinely built in, but the system stops being free the moment you add generation APIs.
Troubleshooting
Quick-start checklist
Verified against the project at commit 08e2151 (5 Sep 2026): cloned, set up, and read against the README, agent guide, config and pipeline definitions. The demo render was the only step blocked, and only by a sandbox without network access. Everything above was re-checked against the current repository before publishing — the cost figures, budget thresholds and zero-key tool list all hold; the licence did not.