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.

Before any of them: setup, once, in a normal terminal#

showtime renders on your machine, so it needs its tools and models in ~/.showtime: about 770 MB on Linux x64, 560 to 610 MB on macOS and Windows (showtime setup --plan prints your exact list; bigger pieces such as Whisper for transcripts arrive the first time a video needs them, with their size announced, and showtime setup --full fetches them all now). Agent sandboxes often block that download, so run setup yourself once:

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. showtime below means that command, or the skill's own bin/showtime.

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

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.2.0.mcpb from the v0.2.0 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.

View or edit this page on GitHub