Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

Your coding agent can record the demo video of the feature it just built

Most developer-led teams ship faster than they can film. The feature is done, the PR is merged, and the demo video is still a to-do: someone has to open a screen recorder, click through without a typo, record a voiceover

Most developer-led teams ship faster than they can film. The feature is done, the PR is merged, and the demo video is still a to-do: someone has to open a screen recorder, click through without a typo, record a voiceover and cut the dead air.

We build tday.com, and our bet is that the coding agent that wrote the feature should also record its demo. Here is how that works, and what it can and cannot do.

How it works

tday.com ships an MCP server (@tday-com/mcp) for Claude Code, Cursor, Codex and other MCP clients. Once it is connected, the ask is one sentence:

Use tday.com to record a demo of the new invite flow

The agent then:

  1. Runs a read-only safety check (demo_check) of your env, seed command, ports and tools, and tells you what it found.
  2. Starts a separate demo instance of your app on a free port, with throwaway data. Your own dev server is never restarted.
  3. Records the demo as beats: one narrated line plus the clicks and typing it covers. Anything between beats is cut, so the agent's thinking time never shows. A beat whose step fails is not kept.
  4. Shows you the take and its checks on a local review page, and uploads it.

tday.com then voices each line, adds the cursor, camera, captions, title and end cards and music, and renders a demo you can edit. Only the video, a still from it and a record of its narration, steps and checks leave your machine, never source code.

Here is one, 57 seconds long: https://tday.com/2fgqcs5a

What it records

  • Web apps, in a 1440x900 browser at 2x, so the camera can zoom in and stay sharp
  • Terminal tools: a real shell, filmed as a clean terminal window, with setup commands run off camera
  • Electron apps, launched with a scratch profile and home, or attached to a build you started
  • iPhone apps in the iOS Simulator, or on a real iPhone on a cable
  • Android apps on the emulator
  • Mac apps

Safety

Letting an agent drive your app on camera raises fair questions. The defaults:

  • While a web or Electron demo records, requests from the app's window that would change something off your machine are blocked and counted.
  • Your git name, email, user name and machine name are swapped for a demo persona on screen (web, Electron and terminal).
  • Sign-in happens off camera, and secrets are typed as $env:NAME, so the value is never recorded. Anything that looks like a secret, on screen or in a line, blocks the upload.
  • Recording changes no code: git status is compared at the start and the end.

What it cannot cover: your app's server runs with the keys it starts with, so give the demo test keys for payments, email and anything else it calls.

Keeping demos current

When the feature changes, ask the agent to record again. The new take becomes a new version of the same demo, so its share link and docs embeds keep working. On paid plans, tday.com also lists the demos a merged pull request may have put out of date.

Try it

The free plan has 5 saved demos and 100 credits a month, about 10 minutes of voiceover. Docs: https://docs.tday.com

I would love feedback from anyone who tries it, especially on apps that are awkward to demo.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.