showtime

https://github.com/user-attachments/assets/638bfa30-522f-4e7c-ab9e-e77f364e7dc9

The 0.4.1 showreel: 55 seconds, rendered by showtime 0.4.1 in 2 min 23 s on a 64-core CPU with no GPU; seven real showtime films, then the features behind them ( about the film ). Download the showreel (full quality, 107 MB). Music: “Supernova” by Scott Buckley, CC BY 4.0 . Footage: NASA (public domain); photo: “Godafoss 3” by Tord Dellsen, CC0 ( credits ).

A local video studio for your coding agent. Describe a video. Your agent directs. Your machine renders.

Motion graphics, voice-over, music, sound design, captions, footage editing and platform exports, with no cloud AI services, no API keys and no uploads. Works in Claude Code, Codex, Cursor, Devin, OpenCode and any agent that supports Agent Skills .

Quick start · X-ray · Works with · Gallery · How it works · The crew · Studio · Formats · Docs · Site · Requirements

Quick start

New here? Make your first video: a 5-second test that checks the install and shows every step a bigger video goes through.

1. Install the two prerequisites (details in Requirements): uv and Node.js 24 or 22 LTS (20 or newer works). Restart your coding agent afterwards so it sees them.

2. Add showtime to your agent. In Claude Code:

/plugin marketplace add FavioVazquez/showtime

/plugin install showtime@showtime

Using Codex, Cursor, Devin, OpenCode or another agent? Works with has the exact install for each, and npx skills add FavioVazquez/showtime covers any agent that supports Agent Skills.

3. Ask for a video:

Make a 20-second launch video for this repo, with a voice-over and upbeat music.

The first time, your agent checks what is missing, tells you the download size and time (about 0.5 to 0.75 GB to download and 1.4 to 1.8 GB in ~/.showtime once installed, depending on your system, usually 2 to 6 minutes; outside that folder only uv's and npm's download caches change) and runs setup once you say yes. If your agent's sandbox blocks the download, run setup once in a terminal (Troubleshooting). Bigger pieces (the transcription model, Manim, music tracks) come the first time a video needs them, announced with their size. After that, a request in Claude Code looks like this:

An illustration of a session in Claude Code; other agents show the same steps in their own style. The card's figures are example 01's; render time depends on your machine.

Your agent states its assumptions in one line (it asks only when a request is genuinely open), shows you a first look (stills or a fast draft) before the full-quality render, then checks the result with showtime qa. Every request gets its own folder, showtime-out/ - /, with final.mp4, poster.jpg, share.txt, exports/ and work/. Nothing is ever overwritten. Questions about cost, GPUs, disk, languages or what leaves your machine: the FAQ. Something went wrong: Troubleshooting. A word you don't know: the glossary.

[!TIP]

Two separate settings. Quick or studio decides how much your agent asks before building: quick (the

default) states its assumptions and starts; studio (say "show me options first") shows a concept, a look, a

music bed and a storyboard on a local board first. Quality or lean decides how much it checks afterwards:

quality (the default) has a critic review every finished video; lean skips the critic unless the video is going

to be published. Say "no crew" to keep the whole job in one session.

What's new in 0.4.6 (the list is below, and What's new has a short paragraph for each):

• `check` reads the text a page draws on its own canvas. Text outside the phone's safe box, text too small to read and text over other text are found between its samples and on any canvas, not only the film API's.
• X-ray on a phone and in sync. At 9:16 the sound strip and the part labels sit where a phone shows them, a new 16:9 project passes its own check, and with "xray".offset_frames the strip and the piano, drums and guitar follow the recording's clock.
• Fixes. export html --interactive packs a page's own fonts, xray verify reads the marker on a draft render, installed files match the repository byte for byte, and setup --home brings its own ffmpeg.

What's new in 0.4.5 (the list is below, and What's new has a short paragraph for each):

• X-ray from data and from a recording. showtime xray import turns event times measured in a data stream into a film; xray analyze takes a WAV with no picture.
• A live page that says what it knows. How the events were measured, your own steps, and what sharing the page shares.
• A shorter skill router. Six families instead of one row per feature, with a routing eval for contributors.
• Safer and smoother. footage trim -o writes the file you name, the embed takes only safe addresses, and living diagrams type properly on a phone.

What's new in 0.4.4 (the list is below, and What's new has a short paragraph for each):

• X-ray. Film a real thing doing its thing and showtime draws its inside on the frames its own sound says; a score, a guitar tab or a drum sheet from the sound; a receipt that reads the finished film back.
• A live page you play. Pads that play the real clip with its sound, your keyboard typing on the typewriter, drag to scrub, #hit4 links, the request that made it, and an embed.
• Living diagrams you touch. Type on a typewriter, follow a key press to the screen, drag the heat pump's weather.

What's new in 0.4.3 (the list is below, and What's new has a short paragraph for each):

• Living diagrams. showtime new diagram explains a system over time as an isometric figure that builds itself: parts arrive in the order that explains them, and flows, packets and labels move through them.
• Live figures. showtime export html --interactive turns the same scene into one offline page people poke: hover a part, pick a step, turn a knob, and the numbers answer (try one).
• A recap of your agent's session. showtime recap --latest turns a Claude Code session into a 30-60 s narrated film of what the agent did, built only from allow-listed facts, never the transcript's text.
• A failing test as a bug-report video. showtime repro turns a Playwright trace into a narrated film of the steps and the failure, with a Markdown summary for the issue; typed values are never shown.
• Steadier renders, quieter cuts. Every render worker now captures from a page set up like the first one; recap and repro pick their music per session or test, and generated videos no longer put a sound on every cut.

On the behaviour scoreboard, 14 one-sentence requests were run 3 times each (42 runs). The same model did the right thing 35 times with showtime and 25 times without. The cases check that it starts on video requests and stays out of others, that it is honest about missing inputs and unsupported claims, and that it keeps to the plan and the delivery card. Anyone can rerun it.

X-ray

Film a real thing doing its thing, a typewriter typing or a music box playing, and showtime draws its inside moving on the exact frames the clip's own sound says: on the object as the camera moves, or beside it, as a dark radiograph or a light blueprint. Instruments get their music written out from the sound too (a score, a guitar tab, a drum sheet), and every film ends with a receipt that proves it.

An Underwood 315 typing, seen through. Clip: Erik Pålsson / Sounds of Changes, CC BY 3.0 .

Say "X-ray this clip of my typewriter" to your agent, or run the three steps yourself:

showtime xray analyze clip.mp4 --jo