showtime in your coding agent

showtime is a skill, a command line and an MCP server. Any agent that reads Agent Skills and can run shell commands can use it; MCP adds typed tools on top, and the ten crew agents are an optional speed-up for hosts with custom sub-agents. This page gives the exact install for each agent; the README has the short version.

Tested means the agent installed showtime and made a real video with it: the request "make a 5-second test video that says hello" in an empty folder, ending in a final.mp4 whose showtime qa verdict had no FAIL. Should work means the files it reads are there and were checked with the agent's own tools where possible, but no real video was made in it yet.

Tested on Linux x64 (Ubuntu 24.04) on 2026-09-28.

Setup: your agent runs it, once#

showtime renders on your machine, so it needs its tools and models in ~/.showtime: about 0.73 GB to download on Linux x64 and 0.53 to 0.59 GB on macOS and Windows, 1.4 to 1.8 GB once installed (showtime setup --estimate prints yours and showtime setup --plan every download; bigger pieces such as the transcription model (about 490 MB) arrive the first time a video needs them, with their size announced, and showtime setup --full fetches them all now). On your first request your agent finds that setup is missing, tells you the size and time, and runs showtime setup once you say yes.

Some sandboxes block that download by default: Cursor's and Antigravity's, and Codex's workspace-write until you allow network access (see their sections below). When yours does (showtime doctor fails home writable or network), run setup yourself once, in a normal terminal:

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)

Or ask your agent to install into the project folder instead, which the sandbox can write: SHOWTIME_HOME=.showtime showtime setup (PowerShell: $env:SHOWTIME_HOME=".showtime"; showtime setup) (Troubleshooting).

Setup also writes the stable command ~/.showtime/bin/showtime (Windows: showtime.cmd), which keeps working when a plugin update moves the skill folder. It runs the newest showtime that has run on this machine; between two copies of the same version it keeps the installed one (a plugin or a skill in an agent's skills folder) over a checkout, and otherwise the one it already runs, so running another checkout never moves it. showtime below means that command, or the skill's own bin/showtime.

Review mode, the same in every agent: quality (the default) reviews every finished video with a critic round before delivery; ask your agent for "lean" or run showtime config mode lean (or set SHOWTIME_MODE=lean; MCP clients: the new_project tool's mode) for a cheaper draft pass.

showtime install#

For agents that do not install plugins from this repository, one command puts each piece where that agent looks for it:

showtime install --agent <name>              # for your user
showtime install --agent <name> --project    # into the current project only
showtime install --agent <name> --print      # show what it would write, change nothing
showtime install --agent <name> --uninstall  # remove what it added, nothing else
showtime install --list                      # agents it knows

It links the skill folder where the agent reads skills (only where it does not see one already), writes the ten crew agents in the agent's own format, and adds a showtime MCP server entry launched as ~/.showtime/bin/showtime mcp. Config files are merged, never replaced: the original is kept once as <file>.before-showtime, and a file it cannot parse (JSON with comments, YAML) is left alone with the entry printed for you to paste. Run it again after updating showtime.

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).

Claude app#

In the Claude desktop app: Customize → Plugins → Add marketplace, enter FavioVazquez/showtime, then install showtime from it. Commands run in the app's sandbox, behind a proxy that can answer 403 for Hugging Face and GitHub LFS. showtime setup works there anyway: when a model's own host is blocked, the file comes from showtime's model mirror (release assets under the models-v1 tag of this repository) and is checked against the same sha256. The mirror holds the default install's and first-use models (Kokoro, YuNet, Whisper small.en, Parakeet v3, the word aligner, Silero VAD, the denoise models, the default SoundFont); opt-in extras such as --with asr-turbo and Piper voices are not mirrored. SHOWTIME_MODEL_MIRROR points at another mirror: a base URL, or a folder holding the files under their mirror names (skills/showtime/lib/st/mirror.json lists them); off turns the mirror off.

The same proxy also blocks the hosts real music and sound effects come from (opengameart.org, scottbuckley.com.au, incompetech.com, archive.org, upload.wikimedia.org, bigsoundbank.com, kenney.nl), so a video's soundtrack and sound effects would otherwise be silently missing. The audio mirror (release assets under the audio-v1 tag) covers the music catalog, the sound-effect packs and the core/extended library tiers the same way: SHOWTIME_AUDIO_MIRROR picks another mirror or folder, off disables it.

OpenAI Codex#

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)

Codex reads the root plugin.json and mcp.json (Agent Plugins 1.0): the skill appears as showtime:showtime and the MCP server starts from the plugin folder. Codex plugins cannot carry sub-agents, hence the optional second command; Codex only starts them when you ask ("spawn the scriptwriter agent").

Sandbox: renders write to ~/.showtime and setup needs the network. In the default workspace-write sandbox, add to ~/.codex/config.toml:

[sandbox_workspace_write]
network_access = true
writable_roots = ["/home/<you>/.showtime"]

On Ubuntu 24.04 Codex's own sandbox may not start at all ("bwrap: setting up uid map: Permission denied"); that is the distribution restricting unprivileged user namespaces, not showtime. The test above ran with --sandbox danger-full-access on a throwaway machine for that reason.

Headless: codex exec --skip-git-repo-check "make a 5-second test video that says hello".

Cursor#

Editor: put a clone where Cursor loads local plugins, then restart Cursor.

git clone --depth 1 https://github.com/FavioVazquez/showtime ~/.cursor/plugins/local/showtime

CLI (agent): load the same folder with --plugin-dir:

agent --plugin-dir ~/.cursor/plugins/local/showtime
agent -p --force --trust --approve-mcps --plugin-dir ~/.cursor/plugins/local/showtime "make a 5-second test video that says hello"

Cursor reads .claude-plugin/plugin.json: skill, crew agents and MCP server all load. Without the plugin: showtime install --agent cursor (skill in ~/.agents/skills, agents in ~/.cursor/agents, MCP in ~/.cursor/mcp.json). Cursor's sandbox limits network to sandbox.json, so run setup in a normal terminal first.

Devin#

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"

Devin reads .claude-plugin/. Crew agents work in the CLI and Devin Desktop, not in Devin Cloud. Devin asks before each MCP tool by default (allow mcp__showtime__* in its permissions to skip that). Headless: devin -p "…" --permission-mode dangerous --respect-workspace-trust false < /dev/null.

OpenCode#

showtime install --agent opencode

The skill goes to ~/.agents/skills/showtime, the crew to ~/.config/opencode/agents (mode: subagent) and the MCP server to ~/.config/opencode/opencode.json. Check with opencode agent list and opencode mcp list (showtime: connected). Headless: opencode run --auto "…"; the test used one of OpenCode's free models and the showtime MCP tools (doctor, new_project, check, render, qa).

GitHub Copilot#

CLI:

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

VS Code: run Chat: Install Plugin From Source with https://github.com/FavioVazquez/showtime (plugins the CLI installed also appear in VS Code). Copilot reads the root Agent Plugins manifest; the crew agents come from com.github.copilot/agents/. Without the plugin: showtime install --agent copilot.

Gemini CLI#

Gemini CLI now serves paid API keys and Gemini Code Assist Standard/Enterprise.

showtime install --agent gemini

This adds the skill (~/.agents/skills), the crew in Gemini's format (Gemini tool names, timeout_mins: 60) in ~/.gemini/agents, and the MCP server in ~/.gemini/settings.json. The repository is also a Gemini extension (gemini extensions install https://github.com/FavioVazquez/showtime): it brings the skill and the MCP server, but Gemini then prints an "Error loading agent" line for each of the ten Claude-format crew files it cannot read; the install command above avoids that. Gemini stops a shell command after 300 s without output: showtime prints a progress line every 45 s.

Antigravity#

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

or, without the plugin: showtime install --agent antigravity (skill in ~/.gemini/antigravity-cli/skills, crew in ~/.gemini/config/agents, MCP in ~/.gemini/config/mcp_config.json; agy agents and agy mcp list show them). Antigravity's terminal sandbox has no network by default: run setup in a normal terminal.

Cline#

showtime install --agent cline

The skill goes to ~/.cline/skills/showtime and the MCP server to the Cline CLI's ~/.cline/mcp.json. In the VS Code extension, add the same entry under MCP Servers > Configure MCP Servers (the command prints it), or let Cline follow llms-install.md. Cline's sub-agents cannot use MCP, so no crew is installed.

Kilo Code#

showtime install --agent kilo

The skill goes to ~/.agents/skills. Add the MCP server in Kilo's MCP settings with the command it prints (~/.showtime/bin/showtime with the argument mcp).

Kiro#

showtime install --agent kiro

Kiro reads skills only from ~/.kiro/skills, so the skill is linked there; the crew goes to ~/.kiro/agents/*.json (each loads the skill as a resource) and the MCP server to ~/.kiro/settings/mcp.json.

Zed#

showtime install --agent zed

The skill goes to ~/.agents/skills/showtime (Zed does not read nested skill folders; this link is flat). Zed's settings.json usually has comments, so the command prints the context_servers entry to paste instead of editing it. Zed has no custom agent files.

Goose#

showtime install --agent goose

The skill goes to ~/.agents/skills; paste the printed block into ~/.config/goose/config.yaml, or run goose configure > Add Extension > Command-line Extension with the command ~/.showtime/bin/showtime mcp.

Amp#

showtime install --agent amp        # or: amp mcp add showtime -- ~/.showtime/bin/showtime mcp

Factory Droid#

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

Factory translates the .claude-plugin/ layout. Without the plugin: showtime install --agent factory.

Qwen Code#

showtime install --agent qwen       # Qwen reads skills only from ~/.qwen/skills

Any Agent Skills client#

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).

MCP only#

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

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

(Windows: C:\\Users\\you\\.showtime\\bin\\showtime.cmd.) Two routes need no clone: from npm (@faviovazquez/showtime-mcp, also in the MCP Registry as io.github.FavioVazquez/showtime), {"command": "npx", "args": ["-y", "@faviovazquez/showtime-mcp"]} (see packages/npm/README.md), and showtime-0.4.6.mcpb from the v0.4.6 release, which Claude Desktop opens with a double click. Setup still runs once on your machine, because the models and tools never travel inside a package. Long tools answer with a task id after about 20 s when a client stops calls early; the status tool reports progress and the result.

The MCP server has a guide tool that reads a reference by the piece (its rules, one section, or the lines that mention something), so a client without the skill does not have to load whole files, and a receipt tool that 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). 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: adopt (a Claude Design export too), footage cutout, edit cards, edit moments, edit clips, pr-video, review open and review notes, and export html's --share-url and --share-image (showtime.json "share" works through export_html). An agent with a shell runs them as showtime <command>; a client with MCP only cannot reach them yet.

In CI: the GitHub Action#

To make a release or pull-request video on a runner, with no agent and no API key, use the showtime GitHub Action. Its agent mode runs a coding-agent command you configure, with your own key as a secret; only the plumbing of that mode is tested here, not a particular agent.

View or edit docs/agents.md on GitHub