Make a 36-second cinematic short film by scripting Blender headless

Leonxlnx had Claude Code (Opus 5.5) build, render, edit and score a 36-second CGI short in Blender 5.2 entirely from Python on a laptop iGPU, from one prompt and a few rounds of notes.

Done withClaude CodeinGitHub· Nov 8, 2026

What they did

GitHub user Leonxlnx gave Claude Code running Opus 5.5 a single brief for a short film and then a few rounds of feedback. Claude Code drove Blender 5.2 in headless mode through Python on a laptop with an AMD Radeon 780M integrated GPU. Every object, material, light and camera move is generated by script, with no downloaded models or textures: clockwork gears, a hypercar that assembles itself, a canyon, a temple and a desk. Five builder agents worked on the five acts in parallel, a director agent critiqued each act, and a second pass applied the fixes. The edit, colour grade, transitions and sound mix are also Python, using numpy and ffmpeg, cut to a 120 BPM music grid. A script scores each still for clipped highlights and crushed blacks.

How it went

The result is a 36-second 1080p film released on GitHub with the full source, shot list, brief and the agents' iteration logs. Not everything made it: a heavier cloud pass froze the GPU and was dropped, and three shots were cut from the edit. Fast shots were rendered at 83% resolution and 16 samples, then upscaled, to keep render time manageable. Rendering every shot takes many hours on the integrated GPU.

Worth knowing

Running several EEVEE renders at once crashed the laptop with a blue screen, so all Blender runs go through a lock that allows one render at a time. Settings were tuned for that one machine. The audio is not in the repo because its licence does not allow redistribution.

Try it

With Claude Code· 5 parts to fill in

Make a short film of about [length in seconds] about [idea or story beats] using Blender in headless mode, driven only by Python scripts. Write a brief and a shot list first and show them to me before building anything. Generate every model, material, light and camera move in code; do not download assets. Split the work into [number] acts, build them in parallel, then critique each act and apply fixes. Run only one render at a time on my [GPU], and check each still for clipped highlights before moving on. Assemble the edit and sound mix with ffmpeg using [music track]. Stop after each act and wait for my notes.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related