Skip to content

A local video studio for your coding agent. Describe a video in one sentence: your agent directs, your machine renders. Claude Code, Codex, Cursor, Devin and more. No API keys, no uploads.

23.7 KB
Raw Blame

What's new

What each release changes for you, newest first, one sentence a feature. The changelog has every change and the reason for it.

0.4.6

check reads the text a page draws on its own canvas

check used to measure only the film API's text, at its sample times. Now every text a page paints on any canvas (fillText, strokeText) is followed on the whole timeline: text outside the 9:16 safe box (a safe_zone warning with its span), text too small for a phone (tiny_text), and text drawn over other text, canvas or DOM (text_overlap, with when it starts and ends). A counter whose number changes is one text. Text layered on purpose can say so with F.text(..., {layer: true}), F.layer or ST.layer. A probe that could not run (cut_probe_failed, webgpu_probe_failed) is now a warning, so such a check never reads as clean.

X-ray on a phone

At 9:16 the X-ray template's sound strip sits above the counters inside the safe box, and the part labels are 44 px in a column at the safe box's edge, ordered so no two leaders cross; the drawing sits between the columns and never moves. The 9:16 layout change leaves 16:9, 4:5 and 1:1 as they were. A project made with 0.4.5 keeps its own copy of the template: start a new one with showtime new xray to get the layout. A new 16:9 project passes its own check, and the strip's label fits a long mechanism word.

X-ray in sync with an offset clip

With "xray".offset_frames (the clip starts some frames into the film), the sound strip's ticks and caret, track_until, and the piano, drums and guitar mechanisms follow the recording's own clock. The drawing kit gives a mechanism k.rt and k.frameAt(t) for its own drawings.

X-ray tools

xray verify reads the sync marker on a --preview or --scale render. The receipt says what "the original" is when the clip's sound is a rendering of data. export html --interactive packs the fonts a page names in its own <style>, and export html run from inside a job writes into that job. xray import refuses a JSON file with too many object keys, and a word in a strength column, before it does any work.

Small fixes

Installed files match the repository byte for byte on every OS. showtime setup --home X installs ffmpeg into X even when a default install exists. Space or Enter on a focused control of a living diagram no longer also fires the scene's key. The X-ray embed element takes a file: address only on a page opened from disk. showtime assets icon suggests the right name at once for a misspelled one. A page address with a malformed % escape no longer stops the page runtime in preview.

What changes for you

  • check --strict fails when the first-frame-after-cut walk or the WebGPU probe could not run (it was info).
  • check, qa --platform reels and the phone check can report new text_overlap, safe_zone and tiny_text warnings on an existing project that draws its own canvas text.
  • <showtime-xray src="file:..."> on a web page shows the poster; a page opened from disk still loads the film.
  • xray import refuses a word in a strength column (on any row, the ones the time map drops too) and a JSON file with more than 1,600,000 colons.
  • export html --interactive run from inside a job writes into that job, not a new showtime-out/ folder.
  • setup --home X downloads its own ffmpeg into X instead of using the default install's.
  • Space or Enter on a focused control of a living diagram presses the control only.
  • The repository's files are checked out exactly as stored (* -text).

For contributors

scripts/check_release.py now refuses a bullet repeated in the unreleased CHANGELOG section, a file name Windows reserves, a credential-shaped literal in a shipped file, a merge-conflict marker left in a file, a routing case that does not read its own guide, a workflow guide with no line in references/index.md, and a .gitattributes line git ignores.

0.4.5

X-ray from data

showtime xray import <events.csv|json> --job <job> --time-map SLOW,T0 turns event times measured in data (the peaks of a signal, a sensor log) into an X-ray film. Film time is (t_data - T0) x SLOW, each event lands on its frame, and --source names the sound the film plays so xray verify can check it. The live page's commands then start with xray import.

X-ray of a recording with no picture

xray analyze takes a WAV: the events land on a frame grid (30 fps, or --fps), and the page draws the picture side. xray notes takes one too, always at 30 fps.

The live page says what it knows

It states how the events were measured, the sound or a data stream and its note ("xray".measured lets you say it yourself), and shows your own steps when "xray".made.commands lists them. The export warns about a command that would not run or a local path. The page, the gallery and the guide also say what sharing a page shares: its prompt and commands, the whole xray block, the source's name and sha256 and, from data, the events file's name, sha256 and columns.

The skill routes by family

SKILL.md sends a request to one of six families (something that happened; a product, repo, site or paper; an idea or a system; numbers; your own media; a format) in 1,200 words or fewer, and flags live in the guides and --help. The skill also loads now for an interactive figure or living diagram for a web page, and a logo sting, lower third or title goes straight to the transparent render for an editor (render --alpha). Contributors get a routing eval (benchmarks/routing-eval/, one case per workflow guide) and a release check that wants a case for each new guide.

footage trim -o writes the file you name

An existing file is refused unless you pass --overwrite, and -o naming the input clip is refused whatever its spelling. Without -o nothing changes.

The embed element takes only safe addresses

<showtime-xray src> loads a relative, http(s) or file: page and nothing else, in a frame that may run its own scripts and nothing more.

Living diagrams on a phone

The Type field takes a paste or an input-method burst 200 characters at a time, keeps a Chinese, Japanese or Korean composition until you commit it, works with Android Backspace and no longer zooms the page on iOS. Letters, Space, Enter and Backspace pressed on a focused slider, button or link are no longer typed on the board.

Small fixes

An X-ray project without notes passes showtime check. The heat pump's tags show what the scene computes (63 °C, not 70 °C). Recap finds a session's files under a Windows 8.3 folder name. A screenshot that hits its time limit now says when the browser was stuck.

0.4.4

X-ray: film a real thing and see its inside

A typewriter filmed on a desk, its typebars, ribbon and escapement drawn in glowing lines on the machine itself as it types, with the receipt: 19 of 19 events on their frame, audio 0.0 ms from the original.

Film something doing its thing (a typewriter, a music box, a guitar, a drum kit) and showtime finds every event in the clip's own sound and draws the inside moving on exactly those frames: on the object as the camera moves, beside it or as an isometric diagram, in a dark radiograph or a light blueprint. showtime xray analyze measures, showtime new xray --mechanism <object> starts from a library of six mechanisms (typewriter, music box, switch, piano, guitar, drums), showtime xray notes writes a score, a guitar tab or a drum sheet from the sound, and showtime xray verify reads the finished film back for a receipt: "19 of 19 events on their frame · audio 0.0 ms from the original" (guide, xray, the gallery).

A live page you play

showtime export html <xray project> --interactive writes one offline page of the same film: pads under the picture play the next hit from the real clip with its sound, your keyboard types on the typewriter, dragging scrubs, and #hit4 links to a moment. The page shows the request that made it (--prompt) and the commands, and embeds with <showtime-xray> or an iframe. On the site, every film in the gallery plays live in place.

Living diagrams you touch

A figure's scene can now take typing, a click on a part and a drag on a part. showtime new diagram --example typewriter is a typewriter you type on, --example computer follows a key press from the keyboard to the screen, and the heat pump's outdoor unit drags to change the weather (guide).

0.4.3

Living diagrams: a system that explains itself

The Enter loop at work: your machine with the terminal, Claude Code, Bash and a permission check, a request flying up to a glass cube labelled cloud.

showtime new diagram draws how something works as an isometric figure that builds over time: parts arrive in the order that explains them, flows, packets and state changes move through them, labels land when their part matters, and the camera chooses what to look at, in a light, dark or white theme. --example enter (a coding agent's loop), --example market and --example econ-lab start from finished scenes (guide, diagram, the demo).

Live figures people poke

The economics live figure: households, firms and a central bank on a board; the cost-shock step runs, the rule's strength turns from 1.5 to 3, and the readouts change from inflation +1.28 to +0.84.

showtime export html <project> --interactive writes the same scene as one offline page with no player: hover a part to light it and read its value, pick a step to run it on the board, turn a knob and the numbers answer at once. Keys, deep links to a state, reduced motion and a phone layout come with it, and showtime check walks every state before you share it (html-export § Live figure, try one).

A recap of your agent's session

Red to green, from a Claude Code session: one red test run, then two green ones, and 12/12 test files passed.

showtime recap --latest turns a Claude Code session into a 30-60 s narrated film of what the agent did, made from the session log on your machine through an allow-list of facts (repository-relative paths, program names, test counts, git stats), never the transcript's own text; nothing renders until you have read script.md (guide, recap, the demo).

A failing test as a bug-report video

A failing Playwright step: the page says Welcome back, Ada; expected

showtime repro turns a failing Playwright test into a narrated video of its steps and the failure, slowed down, with repro.md to paste into the issue; typed values are never shown or spoken (guide, repro, the demo).

Steadier renders and quieter sound

Every render worker now captures from a page set up like the first one, so a busy machine no longer ships bare frames from a worker whose page opened short (render). Recap and repro pick their music per session or test (a rerun keeps it, --music pins it; a catalog track is downloaded once from its creator's site, nothing is sent, and SHOWTIME_OFFLINE=1 keeps it all local), and generated videos no longer put a sound on every cut (--cut-sounds adds a soft swoosh back); the transition sounds are softer everywhere.

How showtime is built

A new page on the site, how showtime is built, is the crew's operating manual: who does what, and how a task becomes a merged pull request or a film. The site and the repository now share one link-preview image.

0.4.2

Render a film in chapters, with one soundtrack

showtime render --chapters plans the pieces from your chapters (or the film's acts), --chapter N --job J renders one, and --join --job J joins them and builds the soundtrack once for the whole video, so there are none of the loudness steps (2.6 and 0.7 dB) that joining separately mastered sections gave. Every seam is checked against a master before the file is named final.mp4, and after a whole render or a join a later fix to one chapter re-renders exactly its frames. On one machine a whole render is faster: use chapters for a second machine (not measured), a later fix of one chapter, or a long film (render § Speed).

A browser window resized late no longer ruins a render

Under heavy load a whole capture lane of a normal render could come out at the wrong size: with 3 workers, 7 of 40 renders on a 6-core Intel Mac with a GPU had a wrong lane, and 0 of 30 do after the fix (the same fix makes --scale 2 real on a Mac). A page that gets the wrong size is set again and the frame captured again, and render.log says so (render).

More browsers without a GPU, and a frame that never comes

Without a GPU, --workers auto now uses CPU threads - 2 from 8 threads up (at most 8): on an 8-thread machine without a GPU, auto now picks 6 browsers instead of 3. A frame that never comes no longer stalls a render (when the browser reports its processes' work; otherwise the 10-minute cap stays): it is drawn again in a new browser (render) or ends the check with an error. A WebGL canvas that loses its context on the GPU renders again without the GPU (--gpu off) instead of shipping white (without a GPU, render names the canvas and its white frames) (FAQ).

Narration that fits, and more local voices

showtime voice script narration.md -o voice --fit 15 --estimate says up front whether the narration can fit before it synthesizes a single line, and extra local voice engines load by name, with doctor no longer failing on Kokoro when you chose another (voice).

Help when something goes wrong, and a first video step by step

A first-video guide, a troubleshooting page by symptom and a glossary are new, showtime doctor ends with a link to the troubleshooting page when a check fails, and the site's docs start on "Start here" (your first video, troubleshooting, glossary).

0.4.1

Seven looks, no GPU needed

White marble with flowing veins, then metaballs gathering into one coral blob

Fluted glass, tilt-shift, liquid metal, mesh gradient, god rays, marble and metaballs are drawn in showtime's own WebGL, each adds less than 50 ms to a 1080p frame at its default size (one browser on a 64-core machine without a GPU), and each has a designed fallback where WebGL is missing (components § 7, the demo).

Shutter blur on fast moves

A card punched in from three times its size, then SNAP. whipped in twice: sharp on the left, smeared by the shutter blur on the right

Mark the element that moves with data-st-blur and it smears the way a camera shutter would, only on the frames it moves fast, and lands sharp (stage-api § Shutter blur, the demo).

Cards over a talking head, and a word behind the speaker

The word FASTER appears behind a NASA scientist as she says it, its last letter tucked behind her head

Name tags, a list that builds as it is said, a data callout, a pull-quote or a side panel appear as the words are said, and a big word can stand behind the speaker, cut out on your CPU (editing § 9, example 23).

A long recording's best moments, as short clips

A vertical clip from a NASA panel, with bold captions: follow your dreams, somewhere amazing

showtime edit moments ranks the best 20-60 s moments of a podcast, talk or panel on your machine, and showtime edit clips turns the ones you pick into vertical clips with captions, each checked by qa: a 58-minute panel took about 7 minutes end to end on a 64-core machine (editing § 10, example 24).

Claude Design to MP4

An adopted Claude Design export: an amber counter climbs to 1,234 as four bars grow

showtime adopt <export.zip> turns a Claude Design animation's HTML export into a 1080p video with sharp text, its Google Fonts copied in with their licences and exactly one loop of a looping design, ready for music, a voice and captions (adopt § From Claude Design, example 28).

Faster renders, and no GPU needed

The encoder runs while the frames are captured, an unchanged soundtrack is reused, waits stretch on a slow machine instead of failing, and without a GPU the number of browsers follows your cores: on a 64-core Linux machine with no GPU a 30 s launch film rendered in 17.6 s instead of 42.0 s, and a 1 s fix took 13-21 s instead of 31-54 s on a busy 6-core Intel Mac (render § Speed, FAQ).

Link previews for HTML videos

showtime export html --folder --share-url <address> (or "share" in showtime.json) adds the tags that make a pasted link show a title, a description and the poster frame, and the folder is ready for GitHub Pages (html-export § Sharing and hosting, example 25's HTML video).

Notes on a stretch of time, naming what they point at

On the notes page (showtime review open <job>), Shift + drag on the scrubber marks a stretch, and showtime review notes names the scene and the elements under each spot or box and the scenes a stretch covers, so your agent fixes the right thing (review § 6).

Since you last looked

Edit a job's files by hand, leave notes or pick on a board, and showtime status <job> tells your agent what changed since it last looked, so it keeps your edits instead of writing over them (FAQ).

The voice-over is heard back

After the voice-over is made, showtime transcribes it on your machine and flags a name, an acronym or a number the voice said wrong (a name spelled "Open A I" was heard as "OpenI"), with the fix to try (voice § Pronunciation fixes). It runs when the local recognizer is installed: it arrives with the first transcription, or showtime setup --fetch parakeet-tdt-0.6b-v3-int8. A word you listened to and found right is cleared in showtime.json.

check catches more before the render

showtime check judges a fading text at its clearest frame, warns when something sits where the captions go (caption_zone), tries a WebGPU page again without WebGPU, estimates each look's cost (look_budget) and flags blur on text being read (render).

Site fixes

On the site, search finds names such as pr-video and every part of a long page, a placeholder such as <title> in a guide shows as text instead of hiding the rest of the page, and every page has a link preview.

0.4.0 (5 October 2026)

  • Videos that stop and ask. List questions in showtime.json and the HTML export pauses on that frame, asks, marks the answer and plays on; the MP4 gets a "pause and think" beat (example 25).
  • Notes on the finished video. showtime review open <job> plays the latest render on a local page where you click a spot or drag a box and type a note; your agent reads the notes, fixes and replies.
  • Range links. video.html#t=10-20 plays that part of an HTML video on a loop.
  • A pull request becomes a video. showtime pr-video <N | URL> makes a short video for the PR's description, with a copy under GitHub's 10 MB attachment limit (example 29).
  • A storyboard table becomes a project. showtime new <template> <dir> --from-storyboard <file> reads a Markdown table of shots (example 26).
  • Go all out. A "showreel" brief turns on a dense tone, and the showreel template renders at 16:9, 9:16, 1:1 and 4:5 with no edits (example 30).
  • The critic watches as a first-time viewer, and its Blockers and Should-fixes must be fixed or waived before a job is marked delivered.
  • A hearing pass reports music over the voice, cut-off lines, long silences and jumps in level.
  • Twelve look signatures. New projects start in a curated palette, type pair and motion feel, picked away from your recent videos (example 32).
  • A behaviour scoreboard anyone can rerun: an agent scored 35/42 with showtime and 25/42 without.

The README has the longer 0.4.0 summary.

Earlier releases

The README summarises 0.3.0 (quieter runs, full review by default, style references, the phone check) and 0.2.0 (every coding agent, a lighter first run, a real music catalog). Everything else is in the changelog.