---
title: "Record a narrated demo of an Electron app | tday.com"
description: "How your coding agent records a narrated demo of an Electron app with tday.com: launched with a scratch profile, or attached to a build you started."
url: https://tday.com/blog/record-a-demo-of-an-electron-app
markdown: https://tday.com/blog/record-a-demo-of-an-electron-app.md
last_updated: 2026-11-18
---

# How to record a narrated demo video of an Electron desktop app

How your coding agent records a narrated demo of an Electron app with tday.com: launched with a scratch profile, or attached to a build you started.

By the tday.com team  Published November 18, 2026  6 min read

## The short answer

Add tday.com's MCP server to your coding agent and ask it to record a demo of your Electron app. tday.com launches the app with a scratch profile and home folder, or attaches to a build you started with a remote debugging port, and films the app's own window. The agent records one narrated line at a time, and tday.com voices the lines and renders the video.

## Key takeaways

- An Electron demo needs nothing beyond what every demo needs: tday.com films your app's own window.
- tday.com either launches the app with a scratch profile and home, or attaches to a build you started with a remote debugging port.
- The agent clicks, types and scrolls the way it would in a web app, finding controls by role, name or visible text.
- The window guard blocks requests from the app's window that would change something off your machine. The main process is outside it, so the agent asks you first.
- Your git name, email, user name and machine name are swapped for a demo persona on screen.

![The first-demo screen zoomed in on its stages, with the checks No new branch, Its own data, Test keys only and Checked before it uploads.](https://tday.com/blog/first-demo-safety-check.webp)

A desktop app is harder to film than a web page. Your real profile is signed in, your notifications pop up, and the app remembers everything you did yesterday. tday.com records an Electron app the way it records a web app: your coding agent drives the app's own window, one narrated line at a time, and anything between the lines is cut.

## What you need

- A coding agent that supports MCP: Claude Code, Cursor, Codex or another MCP client.
- Node.js 18.17 or later, for `npx`.
- [ffmpeg](https://ffmpeg.org) on your `PATH`.

That is all for an Electron app: tday.com films the app's own window, so there is no browser or simulator to install. Before it starts anything, your agent runs a read-only safety check, `demo_check`, with the kind of demo it will record (`electron`), and tells you what it found. The list for every kind of app is in [your first demo](https://docs.tday.com/first-demo).

## Two ways to start the app

| Way | What happens |
| --- | --- |
| Launch | tday.com starts your app from its executable or its app folder, with a scratch profile and home, so the take never sees your own data or sign-ins |
| Attach | You start a build with a remote debugging port, and tday.com attaches to it and films the window you name |

Launching is the safer default: a scratch profile starts empty, like a new install. The agent can pass the app's arguments, its environment variables and what to wait for before recording. Attaching suits an app that needs a particular build or state you set up yourself.

A browser and its extension's side panel are attached the same way. If your product is a browser extension, the agent can film its side panel once it is open.

## Ask your agent for the demo

Connect tday.com once. **Record a demo** on the Demos page gives you a prompt with one install line, which adds the `tday` MCP server to your coding agent. The full setup is in [how to record a product demo with your coding agent](https://tday.com/blog/record-a-product-demo-with-your-coding-agent). Then ask in one sentence:

```text
Use tday.com to record a demo of <a feature> in our desktop app
```

Your agent reads tday.com's demo guide, runs the safety check and tells you its plan before it records. Keep its approval prompts on for the first run, so you see each command before it runs.

## How the agent drives the app

A take is a list of beats. Each beat is one line to say and the steps that line covers. In an Electron app, the steps are the same as in a web app: `open`, `click`, `type`, `select`, `hover`, `scroll`, `press`, `drag`, `upload` and `wait`.

The agent finds each control by its role and accessible name first, then by its visible text, and only then by a CSS selector. For a canvas with nothing to target, it can name a point in the window.

The footage of a beat holds until its line has had time to be said, and anything between beats is cut, so the agent's thinking time never shows. A beat whose step fails is not kept, and the agent records it again.

## The window guard and the main process

While an Electron demo records, requests from the app's window that would change something off your machine are blocked and counted. Reads, fonts and images still load. So when a click on **Send** or **Delete** makes its request from the window, that request does not reach a server off your machine. Whatever the app does elsewhere is not covered, as the next paragraph explains.

An Electron app also has a main process, and it can use the network outside the window. The guard does not see it. Your agent points the app at throwaway backends and asks you before it starts the demo. Letting the main process use the network is a setting it passes only with your OK.

The app's server, if it has one, runs with the keys it is started with. Give it test keys for payments, email and anything else it calls. [Keep demos safe](https://docs.tday.com/demo-safety) has the full list, and [is it safe to let a coding agent record your app](https://tday.com/blog/is-it-safe-to-let-a-coding-agent-record-your-app) explains why.

## Keep personal details off screen

In an Electron demo, your git name, email, user name and machine name are swapped for a made-up persona on screen. Your agent can swap anything else personal, such as teammates or customers, with `demo_fill`.

The agent signs in off camera, before recording starts, and types secrets as `$env:NAME`, so the value is never recorded. Anything that looks like a secret, in a line or on screen, blocks the upload until it is fixed.

An Electron app tday.com starts plays no sound. If you started the app yourself, tday.com mutes it while it records. macOS asks once for System Audio Recording permission for the app your agent runs in; if you say no, the demo still records, with the app's sound left on.

## What tday.com adds after the upload

tday.com voices each line, adds the cursor, camera, captions, title and end cards and music, and renders an editable demo on your **Demos** page. Only the take, a still from it and a record of its narration, steps and checks leave your machine, never source code. Recording changes no code: tday.com compares your repo's `git status` at the start and the end.

Every demo opens in tday.com's editor. Click a line on the voice row, change what it says, and choose **Regenerate this line**. When the app changes, ask your agent to record again: the new take becomes a new version of the same demo, so its share link and embeds keep working.

## Limits

- **It is a video.** Viewers watch it; they do not click through it.
- **One take holds up to 40 narrated lines and 10 minutes**, and one line up to 400 characters.
- **Not every desktop app is Electron.** A native Mac app is filmed off your screen instead, with no window guard and no persona swap. See [how to record a product demo on a Mac](https://tday.com/blog/record-a-product-demo-on-a-mac) for recording one yourself.

Every plan records desktop apps. Recording and rendering use no credits; the voiceover spends your plan's monthly credits, 10 a minute, charged by the second. The free plan has 5 saved demos and 100 credits a month. Every plan is on [pricing](https://tday.com/pricing).

## Frequently asked questions

### Do I need to install anything extra to record an Electron app?

No. Beyond Node.js, ffmpeg and a coding agent with tday.com's MCP server, an Electron app needs nothing more: tday.com films the app's own window.

### Will the demo use my own profile and data?

Not when tday.com launches the app: it starts with a scratch profile and home. If you attach to a build you started yourself, it films that build as it is, so give it demo data first.

### Can a click in the demo reach my real backend?

Requests from the app's window that would change something off your machine are blocked and counted while it records. The main process is outside that guard, so your agent points the app at throwaway backends and asks you before it starts.

### Can tday.com record a browser extension?

Yes. A browser and its extension's side panel are attached the same way as an Electron app, and the agent can film the side panel once it is open.

### Will the app play sound while it records?

An Electron app tday.com starts plays no sound. One you started yourself is muted while it records, after macOS asks once for System Audio Recording permission.

## Sources

1. [tday.com demos](https://docs.tday.com), tday.com docs
2. [Your first demo](https://docs.tday.com/first-demo), tday.com docs
3. [Demo tools reference](https://docs.tday.com/mcp-tools), tday.com docs
4. [Keep demos safe](https://docs.tday.com/demo-safety), tday.com docs
5. [Demo FAQ](https://docs.tday.com/faq), tday.com docs
6. [Plans and limits](https://docs.tday.com/plans), tday.com docs

## Have your coding agent record your first demo

One prompt in Claude Code, Cursor or Codex records a narrated demo of your app. tday.com voices, styles and renders it, ready for your docs. Free includes 5 saved demos.

[Make your first demo](https://docs.tday.com/first-demo) [See pricing](https://tday.com/pricing)

## Keep reading

- ![tday.com's Record a demo dialog on a feature, open on Record on device: Claude Code and Codex on Sam's MacBook Pro, and a Record on Sam's MacBook Pro button.](https://tday.com/blog/record-on-your-mac.webp)

    Guides  November 19, 2026  6 min read

    ### [How do I record a product demo when I am not at my computer?](https://tday.com/blog/record-a-product-demo-away-from-your-computer)

    Ask for a demo on tday.com from your phone or any device, and your own Claude Code or Codex records it on your Mac while you watch its terminal.

- ![A tday.com share page playing a demo titled Give every docs page its demo, captioned: and the same link plays the new version once it's ready.](https://tday.com/blog/share-same-link-new-version.webp)

    Guides  November 19, 2026  6 min read

    ### [How do I embed a product demo video on my website, Notion or Confluence?](https://tday.com/blog/embed-a-product-demo-video-on-your-website)

    Paste an iframe on your website or docs, or paste the share link in Notion, Confluence or GitBook. The MDX and HTML snippets, and who can watch.

- ![tday.com's Record a demo dialog on the Demos page: Copy prompt, buttons that open Claude Code, Cursor, Codex and VS Code Copilot, and what happens before the agent records.](https://tday.com/blog/record-a-demo-dialog.webp)

    Guides  November 19, 2026  5 min read

    ### [How to make a demo video for every release without a video team](https://tday.com/blog/demo-video-for-every-release)

    Demo videos fall behind weekly releases because recording is a separate job. Have the coding agent that built each feature record its demo instead.

---

## For AI agents

- Every page on tday.com is available as Markdown: add `.md` to its address (https://tday.com/index.md for the home page), or request it with `Accept: text/markdown`.
- Site index: https://tday.com/llms.txt. Every page in one file: https://tday.com/llms-full.txt.
- Docs: https://docs.tday.com (index for agents: https://docs.tday.com/llms.txt).
- To record a narrated demo of an app from a coding agent, install tday.com's MCP server once with `curl -fsSL https://tday.com/install.sh | bash`, then ask the agent to record a tday.com demo.
