Claude Just Learned to Fake Being a Video Editor (And It's Kind of Terrifying)
· Chirag Gadhvi
So here's a fun rabbit hole I fell into this week.
People are prompting Claude Opus 5.5 with one sentence — "make me a 15-second motion graphics showreel, go all out" — and getting back stuff that looks like it came out of a real studio. Camera pans, slick typography, transitions that actually make sense. No jank, no melting hands, none of the usual AI video tells.
Except it's not making a video at all. It's writing code.
Here's the actual trick, once you dig in: Claude writes one plain HTML file with a single function that paints exactly one frame when you hand it a timestamp — no animations, no timers, nothing that changes depending on when it runs. Then a headless browser opens that file and calls the function hundreds of times in a row, screenshotting each one like a flipbook. Ffmpeg stitches those screenshots together into an MP4, sometimes with a separately generated soundtrack layered under it.
So the pipeline isn't prompt → video. It's prompt → code → browser → frames → video. No video model involved anywhere. The model basically decided the fastest way to make a movie was to build its own tiny disposable movie camera first, use it once, and throw it away.
And because it's just code, Claude can look at the frames it just rendered and fix what's wrong with them — the same way it debugs a failing test. That's the part that actually got me. It's not just generating a finished thing, it's building and grading the tool that makes the thing.
Here's the post that kicked this whole trend off:
https://x.com/twoclipping/status/2103273003555402193
Read the thread — the creator even open-sourced the prompt template they used to get it. If you've been sleeping on what "AI-generated video" means in late 2026, this is the update.