showtime

_{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 · Works with · Gallery · How it works · The crew · Studio · Formats · Docs · Site · Requirements

Quick start

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. 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/<name>-<timestamp>/, 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.

Tip

Say "show me options first" (or "studio") and your agent opens a local board where you pick a concept, a look, a music bed and a storyboard before anything is built. Say "no crew" to keep the whole job in one session.

What's new in 0.4.1 (the list is below, and What's new has one sentence a feature):

• Seven looks and a shutter blur, no GPU needed. Fluted glass, tilt-shift, liquid metal, mesh gradient, god rays, marble and metaballs in showtime's own WebGL, and data-st-blur smears a fast move only on the frames it moves.
• Talking heads, dressed. Cards appear as the words are said (name tag, list, data callout, pull-quote, side panel), and a big word can stand behind the speaker, cut out on your CPU.
• A long recording to its best clips. showtime edit moments ranks a podcast, talk or panel's best moments on your machine, and showtime edit clips makes the ones you pick into captioned vertical clips, each through qa.
• Claude Design to MP4. showtime adopt <export.zip> turns a Claude Design animation into a 1080p video with its fonts copied in, ready for music, a voice and captions.
• Faster, on any machine. The encoder runs during the capture and an unchanged soundtrack is reused, so a 1 s fix takes 13-21 s instead of 31-54 s on a busy 6-core Intel Mac; without a GPU the browser count follows your cores, and a 30 s launch film renders in 17.6 s instead of 42.0 s on a 64-core machine with no GPU (FAQ).

On the behaviour scoreboard, which anyone can rerun, an agent scored 35/42 with showtime and 25/42 without.

Works with

showtime is a skill, a command line and an MCP server, so it runs in any coding agent that reads Agent Skills and can run shell commands. MCP adds typed tools on top, and the ten crew agents are an optional speed-up for hosts that have custom sub-agents.

Tested with. A real run passed: the agent installed showtime from this repository and made a 5-second test video ("make a 5-second test video that says hello", empty folder), ending in a final.mp4 whose showtime qa verdict had no FAIL.

Should work with any agent that supports Agent Skills: GitHub Copilot (CLI and VS Code), Gemini CLI, Antigravity, Cline, Kilo Code, Kiro, Zed, Goose, Amp, Factory Droid and Qwen Code. The files each one reads are packaged and were checked with the agent's own tools where possible, but no real video has been made in them yet. If you try one, an issue with what happened helps everyone. Exact steps for every agent, and what the tests covered: docs/agents.md.

Claude Code

/plugin marketplace add FavioVazquez/showtime
/plugin install showtime@showtime

Everything is included: the skill, the ten crew agents, the MCP server and the plugin settings (/config).

Any agent that supports Agent Skills

npx skills add FavioVazquez/showtime

This installs the skill for the agents you pick. Then run setup once from the installed skill folder (<skills folder>/showtime/bin/showtime setup), and add the MCP server if you want it (below).

Other agents

Agents often run in a sandbox that blocks a large download, so run setup yourself once, in a normal terminal (it prints the size first and resumes if interrupted):

git clone --depth 1 https://github.com/FavioVazquez/showtime ~/showtime
~/showtime/skills/showtime/bin/showtime setup      # Windows: ~\showtime\skills\showtime\bin\showtime.cmd setup
~/showtime/skills/showtime/bin/showtime doctor     # every line PASS (SKIP is fine)

Setup also writes the stable command ~/.showtime/bin/showtime (Windows: showtime.cmd), which keeps working when a plugin update moves the skill folder. In the commands below, showtime means that command. showtime install --agent <name> links the skill where the agent looks, writes the ten crew agents in the agent's own format and adds a showtime MCP server entry; it merges config files (one backup, never a replacement), and --print, --project and --uninstall are there too.

codex plugin marketplace add FavioVazquez/showtime
codex plugin add showtime@showtime
showtime install --agent codex --no-skill --no-mcp   # optional: the ten crew agents (~/.codex/agents)

git clone --depth 1 https://github.com/FavioVazquez/showtime ~/.cursor/plugins/local/showtime   # then restart Cursor
agent --plugin-dir ~/.cursor/plugins/local/showtime                                             # the CLI

devin plugins install FavioVazquez/showtime        # add --local to keep it off your Devin Cloud plugins
devin plugins info showtime                         # skill, 10 agents, MCP server "showtime"

showtime install --agent opencode

copilot plugin marketplace add FavioVazquez/showtime
copilot plugin install showtime@showtime

showtime install --agent gemini

git clone --depth 1 https://github.com/FavioVazquez/showtime ~/showtime
agy plugin install ~/showtime                     # skill, crew and MCP server

showtime install --agent cline      # skill + MCP server (no crew: Cline's sub-agents cannot use MCP)
showtime install --agent kilo       # skill; add the MCP server in Kilo's settings with the command it prints
showtime install --agent kiro       # skill, crew and MCP server
showtime install --agent zed        # skill; it prints the context_servers entry to paste into settings.json
showtime install --agent goose      # skill; it prints the extension block for config.yaml
showtime install --agent amp        # or: amp mcp add showtime -- ~/.showtime/bin/showtime mcp
showtime install --agent qwen       # Qwen reads skills only from ~/.qwen/skills

droid plugin marketplace add FavioVazquez/showtime
droid plugin install showtime@showtime

MCP only

Any client that starts local (stdio) servers can use showtime's MCP server on its own, without the skill. After setup:

{
  "mcpServers": {
    "showtime": { "command": "/home/<you>/.showtime/bin/showtime", "args": ["mcp"] }
  }
}

(Use the full path to that file in your home folder; on Windows it is showtime.cmd in %USERPROFILE%\.showtime\bin, written out in full.) Two more routes need no clone at all:

{ "command": "npx", "args": ["-y", "@faviovazquez/showtime-mcp"] }

is the same server from npm (@faviovazquez/showtime-mcp, also listed in the MCP Registry as io.github.FavioVazquez/showtime and on Smithery), and showtime-0.4.1.mcpb from the v0.4.1 release opens in Claude Desktop with a double click. Setup still runs once on your machine: the models and tools never travel inside a package. Long tools answer with a task id after about 20 seconds when a client stops calls early; the status tool reports progress and the result. Besides the tools that mirror the commands, guide reads a reference by the piece and receipt writes a job's receipt (tokens and cost are "not reported by this agent" through MCP). Ten core tools are listed by default (doctor, status, guide, new_project, render, check, qa, export_html, deliver_exports, receipt), which keeps the list short. Add "env": { "SHOWTIME_MCP_TOOLS": "all" } to the server entry to list the voice, music, sound-effect, transcription, stills and studio-board tools too; the .mcpb sets it for you. Some features have no MCP tool yet and run from the command line: adopt, footage cutout, edit cards, edit moments, edit clips, pr-video, review open and review notes, and export html's link-preview flags (showtime.json "share" works through export_html).

Now showing

_{▶ Watch the 0.2.0 launch film (40 s, plays on the showtime site; made with showtime, every frame from a real example, about the film, download).
Music: “With These Hands” by Scott Buckley, CC BY 4.0 (credits).}

Every example was made by an agent acting as a user, and ships with its project sources and a README that tells the story: the request, the assumptions, the commands, what the critic found and what changed. Click a preview to open the example. Each one has a card with its prompt and links in examples/. Previews are silent; the videos have sound.

Data and reports

Data story · 30 s 146 years of NASA temperature from a CSV. Every number on screen comes from the data.

Energy report · 60 s, narrated How the US power mix changed, from EIA data. Also an HTML video.

PDF to summary · 75 s, English + Spanish A two-page USGS PDF on Kīlauea 2018, with the agency's own footage, stabilized.

Explainers

How a heat pump heats a home · 45 s A procedural canvas film, narration fitted to the length, a synthesized score. Also an HTML video.	The same film, in Spanish · 51 s Spanish voice and on-screen text, every cut moved to the new narration. Also an HTML video.
A Wikipedia article, explained · 60 s, English + French The honey bee waggle dance, with real research footage. Also as HTML videos. (CC BY-SA, like its source.)	Why a circle's area is πr² · 70 s + Shorts cut A narrated Manim proof with real animated equations.
An explainer that stops and asks · 2:38, narrated The 2026 Nobel Prize in Physics: three questions that stop the HTML video until you answer.	Nobel Chemistry, in English and Spanish · 2:30 + 2:34 A lab-notebook explainer of the 2026 Nobel Prize in Chemistry, then every word of it in Spanish.

Product and brand

Launch video · 20 s A (fictional) notes app: hook cards, its landing page, a scripted recording of the real app.	showtime's own launch video · 30 s + square cut Real renders, real terminal output, narration made on the rendering machine.
Product promo, 1:1 · 20 s + 6 s bumper A museum's CC0 photos of a Christopher Dresser teapot, only facts from the record. Also an HTML video.	Brand motion pack · sting, lower thirds, stingers A 3D logo sting in three layouts, lower thirds with alpha for an editor, made in studio mode. Also as HTML.
Claude Design to MP4 · 12 s + a 20 s loop Two exported designs adopted as they are, sharp at 1080p, each on a music bed that ends on a phrase.

Footage and audio

Interview, tightened · 72 s, 9:16 + 16:9 A public-domain NASA interview cut by transcript, face-tracked to vertical, graded and captioned.	Podcast audiogram · 45 s, 9:16 A NASA podcast clip for Reels, TikTok and Shorts, with speaker names and captions.
Talking head, dressed · 55 s, 16:9 + 9:16 Cards that appear as the words are said: name tag, list, data callout, side panel, pull-quote, caption emphasis.	A long panel, its best moments · 3 clips, 9:16 A 58-minute NASA panel ranked by edit moments; three vertical clips with captions, each through qa.

Tutorials

Recorded tutorial · 50 s Recorded from a running app; each click lands on the word that names it.

Tutorial series · 2 × 90 s Two canvas episodes sharing one kit. Also as HTML videos.

Tutorial of a real app · 75 s + Shorts cut How to use the showtime studio board, recorded from the real board.

Social

Vertical short · 15 s, 9:16 Three shortcuts: a hook in the first second, karaoke captions, effects on every cut.

Travel slideshow · 45 s + 9:16 Eight CC0 photos cut to the music, with a live map inset. The vertical is a re-layout, not a crop.

Trailers and montage

Beat-synced montage · 20 s Public-domain NASA photos cut on the beat of a library track; its CC-BY credit written automatically.

Studio-mode trailer · 20 s Four concepts on a local board, picks and notes, a storyboard and an animatic, then the final.

Book trailer · 30 s + 15 s vertical teaser The War of the Worlds, from public-domain illustrations and lines from the novel.

Looks and motion

The showreel template in four shapes · 4 × 15 s showtime new showreel as it ships, rendered in four shapes with no edits.	Twelve looks, one project · 24 s loop One dom project in all twelve look signatures, the look changing every 2 s.
Seven looks, no GPU · 18 s demo The seven WebGL looks, one scene each, drawn in showtime's own WebGL on the CPU.	Shutter blur on fast moves · 7.5 s demo data-st-blur on the word that moves: smeared while it is fast, sharp when it lands.

For developers

	Open-source release video · 35 s, no voice What changes in people's code with Black 26.1.0's 2026 stable style: real before-and-after diffs, the install line and the changelog. Point showtime at a repo, a pull request or a changelog and it makes the same kind of video. (An unofficial summary, made as an example.)
	A pull request becomes a video · 40 s, one command showtime pr-video 7 on showtime's own pull request: the PR's title and words, the files it changed with their +/- counts, a real hunk and its URL, secrets masked, a copy under GitHub's 10 MB attachment limit and the Markdown to paste.

Two more kinds of developer video have a workflow but no example in this gallery yet: a repo explainer (what the code does, a map of it, one request traced through real files and lines, every claim tied to a file and a commit) and a paper explainer (claims tied to pages, figures shown only when their license allows, Manim for the math). Say "explain this repo" or give your agent a paper's PDF or arXiv link. For a pull request, showtime pr-video <N> reads it (with gh, or from GitHub's API for a public one) and renders a video under 10 MB to drag into its description (example 29). For release notes and pull requests with no agent at all, showtime release-video and the GitHub Action make a short film in CI.

_{All 22 examples, with their projects and full-quality videos, live in showtime-examples.}

Note

The HTML videos are single files you can open in any browser, offline: the same frames as the MP4, a player with chapters, keyboard shortcuts, links to a moment or to a part that loops, questions that pause the video until the viewer answers, and no network requests. Make one from any project with showtime export html. On GitHub, download the file to play it.

How it works

Motion graphics are written as HTML, CSS and canvas and rendered frame-exactly in headless Chrome: every frame is a pure function of time, so a render, its preview and its HTML video show the same picture. Math scenes use Manim, and real footage is cut by transcript with ffmpeg.

What runs where

showtime adds no cloud service of its own: no API keys, no accounts, nothing you make is uploaded. Every model and tool is downloaded once into ~/.showtime, the small ones at setup and the bigger ones the first time a video needs them. After that it goes online only when you ask for something from the web: public-archive media search (Openverse, Wikimedia Commons, NASA) and website capture fetch pages and files, and send nothing of yours.

Quiet, checked and on the record

The 0.2.0 benchmark showed where an agent's budget goes with showtime: images kept in its context, long command output and reference files read whole. 0.3.0 trims those without removing a check:

• Check first, then one render. showtime check (with the phone check and the look-repeat warning) runs before the full render, and a fix re-renders only the seconds that changed (render --from S --to S).
• Faster fixes (0.4.1). The encoder runs while the frames are captured and an unchanged soundtrack is reused: on a busy 6-core Intel Mac a 1 s fix spliced into a 15-30 s video went from 31-54 s to 13-21 s, and whole renders from 54-115 s to 56-81 s (best of 2, other jobs running).
• One picture per look. showtime look makes a single 1280 px composite of the key frames plus a brief for a disposable reviewer that answers in text; your agent never has to open the image itself. About 12 images per job is the budget (looking guide).
• Short output. Without a terminal, check, qa, doctor and render print the verdict, the findings with their fixes and the paths; the full report is in a file. --verbose prints everything.
• References by the piece. Every guide opens with its rules, and showtime guide <topic> [section] prints just that part.
• A receipt. Each job ends with receipt.md and receipt.json: the request as typed, assumptions, review rounds, full and partial renders, images made for looking, wall time, and tokens and cost when your agent's session log is named. Anything unknown says "not reported by this agent"; nothing is estimated. Claude Code costs are labelled API-equivalent, since a plan does not pay per video (format).

Every finished video gets the full review by default (quality mode: looks, qa and a critic round before delivery). Say "lean" (or run showtime config mode lean) for a cheaper draft pass without the critic, and "show me options first" for the full studio.

Benchmark

A small benchmark: one-sentence video tasks, one run each, scored by automatic checks, an AI judge that must prove it looked at every frame, and a blind vote by me. Round 4 compared showtime 0.3.0 in lean mode (the lighter review setting, which was the default when the round ran) with 0.2.0 in its default mode, plain Claude Code on Opus 5.5 and, for the launch video, an open-source tool built only for launch videos.

In my blind vote, 0.3.0 was preferred to 0.2.0 on 4 of 6 tasks and to plain Claude Code on 7 of 8, and its launch video beat the launch-only tool for the first time in four rounds. The AI judge preferred 0.2.0's polish on most tasks; that is why 0.3.0 ships with the full review (a critic round on every video) as the default, and that default was not part of the round. I'm showtime's author, so treat these as anecdotes, not a result. Every number, limit and loss is in the benchmark report, with each earlier version a click away; the method and the code to rerun it are in benchmarks/.

Behaviour scoreboard

A cheaper check anyone can rerun with one command: 14 one-sentence requests run through claude plugin eval, each with showtime and with no plugin at all (same model). Does the skill fire on video requests and stay out of unrelated ones, does it report a missing file or an unsupported claim instead of inventing around it, and does it keep its contract? Regex and tool-call checks first, a model grader only where a pattern cannot decide; tokens and cost per run, and every failure in plain words, are in SCOREBOARD.md.

claude plugin eval, 2026-10-05, showtime 0.4.0, agent claude-opus-5-5, judge sonnet, 3 runs per case per arm; median tokens per run 65.3k with showtime, 34.7k without; the whole run cost $36.00 at list price. Every case, every failure and how to rerun it: SCOREBOARD.md.

Meet the crew

Your agent is the director. It can hand parts of the job to ten specialist sub-agents that ship with the plugin. Every finished video gets a critic by default (quality mode); say "lean" to skip it (a video you will publish still gets one). A researcher joins when the video states facts or you will publish it, and scene builders when it is long. The rest come with studio mode. Each member gets a written brief, works only in its own folder, never asks you anything, never uploads, and reports back with a short status.

_{▶ Watch the crew at work (45 s, plays on the showtime site; made with showtime, about the film, download).
Music: “Artemis” by Scott Buckley, CC BY 4.0. Bee footage: Su et al. 2008, CC BY 3.0 (credits).}

Who hands what to whom

Let your agent cast it (the usual way). Studio mode brings in the company; for a quick video, your agent adds the critic on its own, and the researcher when the video states facts or you will publish it. Say "no crew" to keep everything in one session.

Let's make a launch trailer for this repo. Show me options first.

Or call one member yourself, by name (Claude Code syntax; in other agents, ask it to "spawn the researcher agent"):

@agent-showtime:researcher check the claims in narration.md against the README
@agent-showtime:critic showtime-out/<job>/review/round-1/CRITIC.md

The agents live in agents/; their briefs, in skills/showtime/references/crew/, work on any agent host, and the crew guide has the dispatch rules.

A fix is judged by preference, not by a score. After a fix, showtime review-pack --against best sets the new render beside the best one so far as a blind pair, and two fresh critics judge it, one in each order. showtime review-verdict applies the rule: the new render wins only when it is preferred both times; a tie or a split keeps the older one. There are up to three rounds. Before the job is marked delivered, every blocker and should-fix the critics raised is fixed or waived with a one-line reason (showtime review-respond), and the receipt lists each waiver (review guide).

Studio mode

Quick mode is the default: one request in, a video out. Studio is opt-in ("show me options first").

flowchart LR
  R["Your request"] --> Q{"Options first?"}
  Q -->|"no, the default"| QM["Quick mode"]
  Q -->|"yes, studio"| SM["Studio mode"]
  QM --> P{"Facts, or will you publish it?"}
  P -->|"yes"| RS["A researcher joins"]
  P -->|"no"| D["Checked by showtime qa"]
  RS --> D
  SM --> CR["The crew joins"]
  CR --> D
  D --> RC["A critic reviews it (say lean to skip)"]
  classDef st fill:#15100E,stroke:#E9B949,color:#F5EBDC
  classDef hot fill:#B3121F,stroke:#E9B949,color:#FFF7EC
  class R,Q,QM,SM,P,RS,CR,RC st
  class D hot

Quick mode is one sentence in and a video out; studio mode opens a local board first, then builds.

In studio you talk about facts and goals in chat; everything about look, sound and timing is shown on a board, a local page served on 127.0.0.1 with a token, with lettered options, one recommendation and buttons you click.

See example 09 and example 21, which is a tutorial of the board itself.

What you get

HTML videos

showtime export html writes one file that plays offline in any browser, with the same frames as the render. Press ? in the player for the key map. A link can open a moment (#t=18) or loop a part (#t=10-20; Shift + drag on the scrubber picks one), and questions listed in showtime.json pause the video until the viewer answers (guide).

What is in the box

Also: 30 motion components (seven of them WebGL looks), 26 transitions (15 CSS, 11 WebGL) and 6 themes, 12 look signatures that new dom, launch, short and data projects start in (a palette, a type pair and a motion feel, picked away from your recent videos; showtime signature), a showreel template for a dense 15-second reel, website capture (screenshots, copy, brand colours and fonts), scripted app recordings with smooth auto-zoom, cursor and keycaps, PDF import, CSV and JSON to charts, a brand kit, posters baked into frame 0, exports for YouTube, X, LinkedIn, Reels, TikTok, Shorts and square feeds, README loops (animated WebP and GIF, like the previews on this page), credits written automatically when an asset needs attribution, a look history so videos do not repeat, style references, adopting video code you already wrote or a Claude Design export (showtime adopt), and a receipt for every job.

showtime new dom my-video --duration 20     # a project from a template
showtime voice script my-video/narration.md -o my-video/voice --fit 18   # local narration, fitted to 18 s
showtime retime my-video --from-voice my-video/voice/timeline.json         # scenes follow the narration
showtime data import signups.csv my-video --x month --y signups --scene bars   # a CSV becomes a chart
showtime preview my-video                    # live player with scrubber and audio
showtime render my-video --preview           # fast draft
showtime render my-video -o final.mp4        # full quality
showtime qa final.mp4                        # PASS/WARN/FAIL: loudness, black/frozen frames, captions, platform
showtime deliver exports final.mp4 --targets youtube,reels,square
showtime export html my-video                # a single-file interactive HTML video
showtime look my-video                       # one composite of the key frames, for a quick visual check
showtime reference clip.mp4 --job my-job     # a video's pace, shots and type scale, as a brief (never its content)
showtime adopt my-page/                      # a page that already has seek(t) gets check, sound, qa and export
showtime adopt design-html.zip               # a Claude Design animation's HTML export to a 1080p video, its fonts local
showtime release-video notes.md -o my-video  # release notes to a ready-to-render project, no agent needed
showtime pr-video 123                        # a pull request to a video under 10 MB for its description
showtime review open my-job                  # a local page to leave notes on frames or stretches of the finished video
showtime edit cards suggest edit/transcripts/talk.json   # moments in a talking head for cards (name tag, quote, list)
showtime footage cutout talk.mp4             # the speaker cut out on the CPU: a video with alpha, a matte, a sheet
showtime edit moments my-job                 # a long recording's best moments for short clips, ranked locally
showtime edit clips my-job --pick m1,m3      # the picked moments as finished 9:16 clips, each through qa
showtime assets font --css "https://fonts.googleapis.com/css2?family=Anton" --copy-to my-video/fonts

New in 0.4.1

What's new has one sentence and a picture for each.

Look and motion

• Seven WebGL looks, no GPU needed: fluted glass, tilt-shift, liquid metal, mesh gradient, god rays, marble and metaballs. Each adds less than 50 ms to a 1080p frame at its default size (one browser on a 64-core machine without a GPU), renders the same frames with any number of browsers, and has a designed fallback where WebGL is missing (components § 7, the demo).
• Shutter blur. data-st-blur smears an element the way a camera shutter would, only on the frames it moves fast; it lands sharp (stage-api, the demo, the flash words of example 30).

Footage

• Cards over a talking head: a name tag, a list that builds as it is said, a data callout, a pull-quote, a side panel, anchored to the words so a re-cut moves them, and caption emphasis on key terms (example 23).
• A word behind the speaker. showtime footage cutout cuts a person out on the CPU (MODNet, Apache-2.0), and the EDL card behind puts a big word between the background and the speaker.
• A long recording to its best clips. showtime edit moments ranks whole-sentence moments by local signals (a hook, a complete thought, energy, laughter and applause, one topic) and showtime edit clips renders the picked ones as face-tracked 9:16 clips with captions, each through qa: a 58-minute panel took about 7 minutes end to end on a 64-core machine (example 24).

New ways in, and sharing

• Claude Design to MP4. showtime adopt <export.zip>: the artboard fills a 1080p frame with sharp text, its Google Fonts are copied in with their licences, and a looping design renders exactly one loop (adopt, example 28).
• Link previews. showtime export html --share-url <address> (or "share" in showtime.json) adds the tags that show a title, a description and the poster when the link is pasted; --folder exports are ready for GitHub Pages (example 25's HTML video).

Review and resume

• Notes on a stretch of time (Shift + drag on the notes page's scrubber), and showtime review notes names the scene and the elements under each note.
• Since you last looked. showtime status <job> lists the files you edited by hand, your unread notes and open findings, so your agent keeps your changes.
• The voice-over is heard back: showtime transcribes it on your machine and flags a name, an acronym or a number said wrong, with the fix to try; qa and the critic see it too. It runs when the local recognizer is installed: it arrives with the first transcription, or showtime setup --fetch parakeet-tdt-0.6b-v3-int8.
• check catches more: a fading text is judged at its clearest frame, caption_zone warns about anything where the captions go, a WebGPU page is tried again without WebGPU, and each look's cost is estimated.

Faster

• The encoder runs while the frames are captured, a finished browser takes over half of the largest part left, and an unchanged soundtrack is reused: on a busy 6-core Intel Mac a 1 s fix went from 31-54 s to 13-21 s.
• Without a GPU, the number of browsers follows the cores (one per 8 CPU threads, at least 3 from 6 threads up, at most 8), and waits stretch on a slow page instead of failing: on a 64-core Linux machine with no GPU a 30 s launch film went from 42.0 s to 17.6 s and a 15 s DOM page from 31.8 s to 16.4 s. Do I need a GPU?

The full list is in the changelog.

New in 0.4.0

Videos that ask, and notes on the finished video

• Videos that stop and ask. List questions in showtime.json and the HTML export pauses on that frame, asks, marks the answer, replies and plays on; the MP4 gets a "pause and think" beat with a countdown and the answer. A question can sit on a narration line, so a re-voice moves it with the line (guide, example 25).
• Notes on the finished video. showtime review open <job> serves a local page that plays the latest render: pause, click a spot or drag a box on the frame, type a note. Your agent reads them with showtime review notes, fixes, and replies on the same note.
• Range links in the HTML player: video.html#t=10-20 plays that part on a loop.

New ways in

• showtime pr-video <N | URL>: a pull request becomes a short video for its own description in one command, with a copy under GitHub's 10 MB attachment limit. A public PR works without a GitHub login, and values that look like secrets never reach the video (example 29).
• A storyboard from another skill becomes a project: showtime new <template> <dir> --from-storyboard FILE reads a Markdown table (Shot | Length | Visual | Narration, in any order, English or Chinese headers; examples 25 and 26).
• Go all out: the showreel tone. A "showreel" or "go all out" brief turns it on: 12-14 shots in 15 s, no technique twice, flash words allowed, the name landing late and short; qa judges density, the ending and repeats. The showreel template renders at 16:9, 9:16, 1:1 and 4:5 with no edits (example 30).

A stricter quality gate

• The critic watches as a first-time viewer before it reads the brief: for each part, does a newcomer know why it is there? Explainers default to a cold open with the stakes, a roadmap, bridges and a close that answers the opening.
• Findings gate delivery. A job is not marked delivered while a critic's Blocker or Should-fix is neither fixed nor waived (showtime review-respond --fixed | --waive), and every waiver keeps its reason in the receipt.
• A hearing pass next to the visual critic: music over the voice, a rushed or cut-off line, a long silence, a late or loud effect, a jump in level at a cut, music that stops dead.
• One delivery card with a mandatory Look: line saying what was opened, at what size, and what was seen.

Better-looking by default

• Twelve look signatures. showtime new dresses the page templates in one of twelve curated looks (palette at the contrast rules, a type pair, a motion feel), picked away from your recent videos (--look <id> to choose; example 32 shows one project in all twelve).
• No blank or late first frames after a cut or in a <video>: every video is drawn on a canvas in renders, and check warns late_first_frame.

Proof

• A behaviour scoreboard anyone can rerun (above): 35/42 with showtime, 25/42 without.
• A blind rematch on the round-1 showreel prompt (round notes): showtime 0.4.0 lost round 5; after the density fix its two takes ranked first and second in round 6, ahead of the plain take that had won round 1. One voter (me, showtime's author), partly blind: an anecdote, not a result.

Limits: the hearing pass and the checks measure the file; whether a video is good is still the critic's and your call. The full list is in the changelog.

New in 0.3.0

Quieter runs, full review by default

• Lean mode, when you ask for it. The full review stays the default; say "lean" (or run showtime config mode lean) for a lighter pass without the critic round. In both modes showtime look makes one composite image that a disposable reviewer reads (your agent does not), render says when a project was not checked first and names the cheaper --from/--to fix after a second full render, and check, qa, doctor and render print a short summary by default (--verbose for everything). Every reference opens with its rules (showtime guide <topic> prints them). No check was removed. In benchmark round 4, lean runs read a median of 4.5 images into the agent's context and made a median of one full render per job.
• showtime job init checks your setup and prints setup: ready or the failures with their fixes, so it is the one command to start with.

Better videos

• Variety guard. Each finished job's look (template, theme, palette, type pair, transitions, camera moves, music, structure, tone) goes into a local history that never leaves your machine (showtime history off turns it off). showtime check warns look_repeat when a project repeats one of the last five, with two concrete alternatives.
• Style references. showtime reference <video> writes a brief with the video's cut rhythm, shot lengths, how scenes change, palette, camera moves, rough type scale and loudness curve, and a contact sheet. The storyboard borrows the grammar, never the words, logos or shots; the credit "Style reference: ..." is written for you, and showtime qa fails a render that copies the reference's pictures (guide).
• Phone check. showtime check ends with phone check: PASS or FAIL with timestamps: each text held long enough to read (per language), a minimum type size at phone width (16:9 5 pt, 1:1 10, 4:5 11, 9:16 15) and nothing under a platform's buttons or at the edge. In qa, a failure is a warning, never a FAIL.
• Brand first for launches. showtime brand capture <repo|url> --job <job> takes the product's palette with roles, fonts, logo, wordmark, real copy (with file and line) and real UI before the storyboard, and showtime new launch applies it. A launch job with no kit says why (showtime brand skip), and check warns when it does not.
• Pairwise review. See the crew: a new version ships only if the critic prefers it in both orders.
• Fixes where agents tripped: a clip's frames no longer depend on the order the frames were asked for, retime --from-voice --total works when every scene is narrated, Manim silent films and --mix paths work, doctor warns when the showtime command on your path is not the agent's, and font errors name the exact missing characters and the fix.

New kinds of video

• Repo explainers and paper explainers (workflows repo-explainer and paper-explainer), described above.
• showtime release-video turns release notes, a CHANGELOG section or a PR description into a ready-to-render project with no agent: the notes' own words, reading-time holds, the people credited.
• A GitHub Action that renders a release or PR video on the runner, checks it, exports an HTML video and a copy under 10 MB, and uploads them (guide). It needs no API key unless you choose the mode that runs your own agent.
• showtime adopt <folder | page | script> takes a video someone already wrote as a function of time (an HTML page with seek(t), a canvas draw(t), a CSS-animated page, a Python frame function) and gives it showtime's checks, sound, captions, qa, HTML export and review, without a rewrite. The originals are never changed (guide).

Honesty

• Receipts. Every job ends with receipt.md, receipt.json and a line in share.txt (see above).

In progress (landing before the release):

• A fix to a few seconds (render --from A --to B --job <job>) splices into a complete new final: only those frames change, the audio is mastered again, and a span is never mistaken for the video.
• Every Manim template passes its own check, and a scene's first element is on screen at frame 0.

Limits: the phone check and the look history read the project files and cannot judge whether a video is good; a model reviewer's preference is steadier than its score but is still an opinion; tokens and cost appear only for agents that expose their session log (Claude Code and Codex, as numbers only), and everything else says "not reported by this agent". The full list is in the changelog.

New in 0.2.0