Your agent shipped it.Now it gets a trailer.

Cutscene makes short, code-rendered launch videos for your app. Ask Claude Code or Codex (inside Conductor, too). Your agent answers Cutscene’s questions from your code and sends only what you approve. Your source never leaves your machine.

Install once$ npx skills add https://cutscene.dev -g

Then ask your agentMake a launch video for this app with Cutscene.

Private beta: your agent will ask for your CUTSCENE_TOKEN on first use. Read the docs →

How it works

The whole thing is one scene.

FADE IN:

INT. CONDUCTOR WORKSPACE — LATE NIGHT

A repo glows. Tests pass. The feature shipped an hour ago. Nobody has made the launch video.

YOU

Make a launch video for this app with Cutscene.

YOUR AGENT

(calling create_video)

On it. Cutscene sent eleven questions: pitch, features, colors, fonts, logo, a few screens.

The agent reads tailwind.config.ts, app/layout.tsx, the landing page. Locally. It pulls out hex values, font names, the hero copy.

YOUR AGENT

Here’s the package. Eleven answers, one logo, three screenshots with demo data. No source files. Ship it?

YOU

Ship it.

CUT TO:

EXT. AN ISOLATED SANDBOX — CONTINUOUS

A director model sets the tempo and lays scenes on the beat. Each scene becomes a React component. A score is synthesized note by note. Every scene is rendered as a still, inspected, fixed.

CUTSCENE

(V.O.)

Twenty seconds, 1080p, original music. Every word and color is a prop, not a hardcoded string.

Eighteen minutes later, an MP4 opens on your screen.

FADE OUT.

Privacy

A closed set, by design.

Your agent is the only one in the room with your code. Cutscene gets a call sheet, not the script.

CALL SHEETPRODUCTION: YOUR APPDAY 1 OF 1

On set sent after you approve

A one-line pitch and 3–5 shipped features
Brand colors as hex values, font names
Your logo file
Screenshots you approve, with demo data
Plain-language descriptions of key screens
The call to action and a public URL

Closed set never sent

Source code — not a file, not an excerpt
Config, lockfiles, .env files, keys
Customer data or database contents
Internal URLs, git history, issues
Anything you strike from the package

Scene breakdown — the eleven questions your agent answers
#	Question	Your agent looks in
01	In one sentence: what does the product do, and for whom?	README, landing page hero copy, package description
02	3–5 headline messages or features. Only things that are real and shipped today.	landing page sections, feature flags that are on, changelog
03	Who is the audience and what tone fits?optional	landing copy voice, marketing pages
04	Brand colors as hex with roles. Dark or light product?	tailwind config, CSS variables, theme tokens
05	Font families for headings, body and code.	next/font or @font-face, tailwind fontFamily
06	The logo — SVG preferred, plus a light-on-dark variant if one exists.	public/, assets/, app/icon.*
07	2–5 screenshots of the key screens, with demo data.optional	run the app locally, or existing marketing shots
08	Layout, components and labels of each key screen — described, not pasted.optional	the page and component files for those screens
09	End-card call to action and URL.	primary button, deployment domain
10	Anything the video must not claim or show.optional	ask the user
11	Length in seconds (10–30, default 20).optional	ask the user

Behind the scenes

Made in code, frame by frame.

SHOT 01
Direct
A director model reads your answers, picks a concept and tempo, and lays 5–7 scenes on a beat grid.
SHOT 02
Build
Each scene is a React component. Every word, color and timing is a typed prop, never hardcoded.
SHOT 03
Score
An original track is synthesized note by note in Python, with hits on your transitions. No stock music.
SHOT 04
Review
Stills of every scene are rendered and inspected; clipped text and weak frames get fixed before the 1080p render.

For agents

Built to be called, not clicked.

Cutscene is a remote MCP server with an agent skill on top. Every page here also answers in Markdown.

endpointhttps://cutscene.dev/mcp

transportstreamable HTTP · stateless · bearer token

toolcreate_video(product_name, brief, product_url?) — Opens a job and returns the questionnaire.

toolupload_url(job_id, question_id, filename) — A one-off signed URL (30 min) and a ready curl command for a logo or screenshot.

toolsubmit_answers(job_id, answers) — Saves text answers; reports what's still missing.

toolstart_video(job_id) — Starts the render once every required answer is in.

toolget_status(job_id) — Progress while rendering; the video URL, report and usage when done.

llms.txt skill index SKILL.md server card server.json ai-catalog

Private beta.

Cutscene is invite-only while we tune the director. Videos are free for invited users during the beta. If you have a token, you’re two lines away from your first cutscene.