# Record a demo of localhost, a page behind a login, or a Mac app

An agent can record all three when the recorder runs on your own machine: it opens what your machine can open, signed in as you choose, with what is private covered before a frame is saved.

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

A recorder that runs on someone else’s servers cannot open your localhost, has to be handed a credential to get past your sign-in, and cannot film an app on your Mac. The vos command line runs in your repo, beside your coding agent. That one fact is why these three work. Here is how each is done, and a real take of each.

## The three, side by side

*How vosso records localhost, a signed-in page and a Mac app, November 2026*

|  | How it is recorded | What you do once |
| --- | --- | --- |
| An app on localhost | A headless browser on your machine opens the dev server’s address | Start the dev server |
| A page behind a login | The same browser, carrying a session you signed in to, or the state your tests produce | Sign in once, or point at your tests’ state file |
| A Mac app | The app’s own window, recorded alone with the cursor’s path, on macOS 14 or later | Grant Screen Recording, and Accessibility for a scripted take |

## An app on localhost

Nothing special is needed. The recorder is a program on your machine, so `http://localhost:3000` is an address like any other:

```
vos record --actions actions.json --url http://localhost:3000 --out take
```

The script, `actions.json`, is the click path: go here, click this, type that. Your agent writes it from the app’s own code. See [record with the CLI](https://vos.so/docs/record/record-with-the-cli) and [the script’s reference](https://vos.so/docs/cli/actions-json).

The one case that cannot reach localhost is a recorder that is not on your machine. vosso has one of those too, for a machine with no browser (`vos record --hosted`), and it refuses a private address in words: a dev server needs a tunnel or a preview deployment there.

[Watch Neon Canyon](https://vos.so/vos/6dff6e4f-e0e8-4489-9556-0d93268335bf)

A game built from one prompt and played at localhost:5173, filmed across the Claude app, Terminal and Chrome and joined into one cut.

## A page behind a login

Work down this list and stop at the first that holds. It is ordered by what it costs you:

1. **No wall at all.** A demo mode, a local server with auth off, a preview deployment. Use it when the feature looks the same there.
2. **The state your tests already make.** If your end-to-end tests sign in and save a storage state, hand that file to the recorder with `--storage-state`. It needs no person, so an agent looks for it before asking you anything.
3. **Steps before the camera.** A `setup` block in the script signs in to a local or seeded account before recording starts, with the password read from your shell, so the sign-in is never in the video.
4. **Sign in yourself, once.** `vos session open` opens a plain Chrome window; you sign in the way you always do, close it, and takes are recorded in that session with `--session`.

A session is yours and stays on your machine. It is never copied into the take and never uploaded.

[Watch Create an API key](https://vos.so/vos/6f34f3b6-13b3-422e-b77d-1e61c05788fa)

A demo behind a login, made by a Claude Code session signed in as a demo account: the key was masked before the first frame and revoked when the take ended.

## Keep what is private out of the frame

A signed-in product shows your name, your email, sometimes a key. Two things in the script deal with that before a frame exists:

- **A mask** hides a selector before the first frame and keeps it hidden across page loads, so the real value is never in the footage or the file. It blurs by default, and can swap an identifier (an email, an account name) for a stand-in. A blur added later in the editor is not a fix: the value would still be in the recording.
- **A spend guard** marks a step that costs something real: a purchase, credits, a message sent. A rehearsal hovers it and never presses it, and the recorder presses it only when you confirm that step by name.

The recorder also lists what the picture holds of yours (a name, an email it can read on the page) with the one line that masks each. Your name and photo are your call: it tells you, and you decide.

## A Mac app

On macOS 14 or later the command line records one app’s window alone, without the system pointer, and saves the pointer’s path beside it, so the take gets a drawn cursor and zooms like a page does:

```
vos look --app "Calculator"
vos record --app "Calculator" --actions actions.json --out take
```

`vos look` lists the app’s controls, each with a selector by role and name. A scripted take presses the real app with your pointer and keyboard, so leave the machine alone until it ends; it stops at the first step that misses. Record a second copy of the app with a scratch project, never the window you are working in. See [record a desktop app](https://vos.so/docs/record/record-a-desktop-app).

It is one window at a time, on a Mac, from a terminal. It is not a recorder you click, and it does not run on Windows or Linux.

[Watch Claude Design](https://vos.so/vos/f6f586fb-8101-4ad5-98f9-e39eb9b7bd1c)

A Mac app driven by a script, its window recorded alone, with the account covered before a frame was saved.

## When a different tool is the right one

- **The page is public and you have no machine to run on.** A hosted recorder is simpler: nothing to install. vosso’s is `vos record --hosted`, and other tools offer the same shape; [they are compared here](https://vos.so/blog/ai-agents-product-demo-videos).
- **You want to record a Mac app by hand.** A desktop recorder with a record button is the right tool; [the options are here](https://vos.so/alternatives/screen-studio).

New to this? Start with [making a demo video with Claude Code](https://vos.so/agents/claude-code).

## Frequently asked questions

### Can an AI agent record a demo of an app running on localhost?

Yes, when the recorder runs on the same machine. The vos command line starts a headless browser beside your dev server and records it there, so localhost is just another address. A recorder that runs on someone else’s servers cannot reach your localhost; vosso’s own hosted recorder refuses a private address for that reason and asks for a tunnel or a preview deployment.

### How do I record a demo of a page behind a login?

Sign in once in a real browser window the command line opens (vos session open), or hand it the signed-in state your tests already produce (--storage-state). The take is then recorded as that account. The session stays on your machine and is never uploaded.

### How do I keep my email or an API key out of the video?

Mask it in the script. A mask hides a selector before the first frame is recorded and keeps it hidden across page loads, so the real value is never in a frame or in the file. A blur added afterwards in the editor is not the same: the value would still be in the recording.

### Can an agent record a Mac app, not a web page?

Yes, on macOS 14 or later: vos record --app records one app’s window alone, without the system pointer, with a track of the cursor so zooms are planned as on a page. A script names the app’s controls by role and name. It uses your real pointer and keyboard while it runs, so leave the machine alone until it ends.

### What stops the agent from clicking something that costs money?

A step that spends something real (a purchase, credits, a message sent) carries a spend guard in the script. A rehearsal hovers it and never presses it, and the recorder presses it only when you confirm that step by name.

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

## Hand your agent the line

Free. The recorder runs in your repo, and nothing is uploaded until you ask for a link.

---

Source: https://vos.so/blog/record-a-demo-of-localhost-a-login-or-a-mac-app
