# Make a product demo video with Claude Code

Hand Claude Code one line. It installs a recorder in your repo, drives your real app, records it with zooms on each action, cuts the video and gives you a link.

By [Hongbin Li](https://www.hongbinli.com/) · Updated November 2026

Claude Code works through the commands it can run, so it makes a video when it has a tool that records. vosso is that tool: a command line and a set of skills that let the agent which built the feature also film it. This is the line:

```
Record a demo video of this app with vosso. The steps are at https://vos.so/agent.md. Give me the vos.so link when it's done.
```

Paste it into a Claude Code session opened in your app’s repo. The steps it names are a short file you can read first, at [vos.so/agent.md](https://vos.so/agent.md). It opens by telling the agent the few things it may ask of you, and to stop and tell you if anything asks for more.

[Watch Flowboard](https://vos.so/vos/26f1b32a-0244-4cce-968c-2b3fa58430a8)

A fresh Claude Code session, handed the one line in a web app it had never seen: the session replayed from its own log, then the demo it made and pushed.

## What Claude Code does with the line

Five things on your machine, in this order:

*What the agent line does in a Claude Code session, November 2026*

| What | Where it lands |
| --- | --- |
| Installs one dev dependency, @vosjs/cli | package.json, your lockfile, node_modules |
| Adds the vos skills | .claude/skills in the repo |
| Writes one marked block | AGENTS.md, or CLAUDE.md when that is the file your repo keeps |
| Records your app | A take folder in the repo: the footage, the cursor track, the click script and doc.json |
| Uploads the take, because the line asks for a link | Your account on vos.so, private until you publish it |

Nothing here adds a hook, changes a settings file or registers an MCP server. The block sits between two comment lines marked `vos:begin` and `vos:end`, and a second run replaces its own text and never yours. The whole account, with what to check yourself, is in the docs: [what your agent does](https://vos.so/docs/agents/what-your-agent-does).

## What the video is

Claude Code writes a click path for your app, and the command line walks it in a headless Chrome and records it with a track of the cursor. From that track a zoom is planned for each action. The agent then cuts the take as data: it reads where the clicks landed, trims the waiting, writes a caption per step, picks music, and checks its own frames before it hands the link back. Nothing is baked in, so you or the agent can change any zoom, word or cut afterwards without recording again.

The Flowboard demo was made this way in October 2026: a session with no knowledge of the app took under ten minutes from the line to the link, and the cut and the words in the film are its own.

## What leaves your machine

- Until the upload, nothing about you or your app goes anywhere. The recording runs locally and the command line sends no telemetry.
- The upload sends the take: the footage, `doc.json` and the click script. It lands private, and a key can never publish it.
- Signing in happens in your browser. The agent runs `vos login`, you approve a code on vos.so, and the agent never sees a password.
- Leave the last sentence off the line and the agent stops after opening the take for you. Nothing is uploaded.

## The skills, and the plugin

The skills are how Claude Code knows the craft and not only the commands. **product-video** records and cuts a demo of your app. **vos-cut** edits a recording you already have. **launch-kit** makes the set of videos a release needs. They land in `.claude/skills` when the line runs.

The Claude Code plugin is another way in, and Claude Code shows what it will install before you accept. It carries the same skills, one command and two hooks, both plain files that read your repo, print one line and never use the network. At session start, in a repo that holds a demo, it says what the demo is and the command that records it again. When a session ends, if you changed a file the demo’s click script touches, it says so. It never blocks.

## See the plan first, or take it back out

To see exactly what setup would write, without writing anything:

```
npm i -D @vosjs/cli
npx vos setup --plan
```

And to remove the skills and the marked block again:

```
npx vos setup --remove
```

## Behind a login, on localhost, or a Mac app

These are the three places where it matters that the recorder runs on your own machine: it opens what your machine can open. Each has its own short method, with a real take of each, on [recording localhost, a page behind a login, or a Mac app](https://vos.so/blog/record-a-demo-of-localhost-a-login-or-a-mac-app).

## When something else is the right tool

- **You want an animated film with no product on screen.** Type, shapes and motion drawn from code are a different craft, and Remotion and HyperFrames ship skills for it: [Claude Code video skills compared](https://vos.so/blog/claude-code-video-skills).
- **You want to record it yourself.** The [Chrome extension](https://vos.so/recorder/chrome-extension) records a tab by hand, with the same zooms and the same editor.
- **You are choosing between agent tools.** [The ones that make demo videos, compared](https://vos.so/blog/ai-agents-product-demo-videos).

## Frequently asked questions

### Can Claude Code record my screen?

It records your app, not your whole screen. Claude Code runs the vos command line, which opens your web app in a headless browser, or records one Mac app’s window, and drives it from a script. Nothing watches your desktop, and the take is a folder in your repo.

### Is there a Claude Code skill for product demo videos?

Yes. The vos skills install into .claude/skills in your repo: product-video records and cuts a demo of your app, vos-cut edits a recording you already have, and launch-kit makes a release’s set of videos. They ship in the package and as a Claude Code plugin.

### Can Claude Code make a launch video for my SaaS?

It can make the part that shows the product: it walks your real app, records it with zooms on each action, adds captions and music, and gives you a link. A video with no product on screen, made of animated type and graphics, is a different job, and a tool that draws from code suits it better.

### What does it install?

One dev dependency (npm i -D @vosjs/cli), the vos skills in your agent’s skills folder, and one marked block in AGENTS.md or CLAUDE.md. It adds no hook, changes no settings file and registers no MCP server. One command takes it all back out.

### Does anything leave my machine?

Not until you ask for a link. The recording runs locally and the command line sends no telemetry. The upload sends the take (the footage, the edit and the click script), and it lands private in your account; a key can never publish it.

### Does it work with Cursor or Codex?

The same line works in any coding agent that runs commands in your repo. The skills land in that agent’s own folder (.cursor/skills, .codex/skills, .github/copilot/skills or .agents/skills), and the steps it follows are the same file.

Something else? [hello@vos.so](mailto:hello@vos.so)

## Hand your agent the line

Free. The take is yours, in your repo, before anything is uploaded.

---

Source: https://vos.so/agents/claude-code
