---
title: "Record a product demo when you are away from your Mac | tday.com"
description: "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."
url: https://tday.com/blog/record-a-product-demo-away-from-your-computer
markdown: https://tday.com/blog/record-a-product-demo-away-from-your-computer.md
last_updated: 2026-11-19
---

# How do I record a product demo when I am not at my 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.

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

## The short answer

Turn on Demos from anywhere in tday.com for Mac, then ask for a demo on tday.com from your phone, another computer, or a coding agent through the tday.com MCP server. Your own Claude Code or Codex records it on your Mac, in its own browser, with nobody at the computer. You can watch its terminal and type into it from wherever you are.

## Key takeaways

- Set it up once on the Mac: install tday.com for Mac, sign in to Claude Code or Codex, add your repo and turn on Let tday.com start demos on this Mac.
- Ask from the Record a demo dialog on a feature or docs page, from your phone, or with four MCP tools such as tday\_record\_on\_mac.
- The agent's terminal is live in both directions. On a phone you type in a message box and get keys like esc, enter, the arrows and ^C.
- The agent cannot change your code, records a separate copy of your app, and asks before it uses shared or live data.
- tday.com for Mac must be open. A run is stopped after 90 minutes, and a demo asked for while the app is closed fails after 30 minutes.

![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)

You do not need to sit at your Mac to get a demo recorded. With [Demos from anywhere](https://docs.tday.com/demos-from-anywhere), you ask for a demo on tday.com from any device. Your own Claude Code or Codex then records it on your Mac.

The agent runs on your own Claude or Codex subscription. It records the feature in its own browser, so someone can keep using the Mac while it works. The demo counts against your plan like any other demo.

If you have not used a coding agent to record a demo before, start with [how to record a product demo with your coding agent](https://tday.com/blog/record-a-product-demo-with-your-coding-agent). This post covers the remote part.

## Set it up once

Do this on the Mac that should record:

1. Install [tday.com for Mac](https://docs.tday.com/mac-app) and sign in. Download it from [tday.com/download/mac](https://tday.com/download/mac), drag it to **Applications** and open it. **Sign in** opens your browser to approve the app, so there is no password to type.
2. Install Claude Code or Codex, and sign in to it in a terminal once.
3. Open **Demos > On this Mac**. In **Demos from anywhere**, click **Add a repo** and choose your copy of the product's repo. It must be a git repo whose remote is the repo connected to your brand in tday.com.
4. Turn on **Let tday.com start demos on this Mac**.

Leave tday.com for Mac open. A demo can only start while it is open. If you ask for one while it is closed, the request waits 30 minutes and then fails with a note to open the app.

## Ask for a demo

You have three ways to ask.

**On tday.com.** Open a feature, or a docs page's sections, and open **Record a demo**. With a Mac ready, **Record on (your Mac)** is the first option. If your Mac has both agents, pick one, then click it. The dialog follows the run as it checks the app, starts it, records, reviews and uploads. It ends with **Open in Studio**. **Stop** ends the run at any point.

**From your phone.** Ask the same way on tday.com in your phone's browser. **Open full view** gives you the run's own page, which also works on a phone.

**From the CLI or MCP.** The [tday.com MCP server](https://tday.com/blog/mcp-server-that-records-product-demos) has four tools for this, and the CLI calls the same tools:

| Tool | What it does |
| --- | --- |
| `tday_list_macs` | Lists your Macs: whether Demos from anywhere is on, whether the app is open, its agents and repos. |
| `tday_record_on_mac` | Records a demo on a Mac. Name `featureIds` or `docsSectionIds`. |
| `tday_get_mac_run` | A run's status and step, and its Studio link once it succeeds. |
| `tday_stop_mac_run` | Stops a run. |

In `tday_record_on_mac`, you can leave out `deviceId`, `agent` and `brandId` when there is only one of each. From a terminal:

```bash
npx --prefix ~ -y @tday-com/mcp@latest call tday_list_macs
npx --prefix ~ -y @tday-com/mcp@latest call tday_record_on_mac '{"featureIds":["<feature id>"]}'
npx --prefix ~ -y @tday-com/mcp@latest call tday_get_mac_run '{"runId":"<run id>"}'
```

A feature's id comes from `tday_list_features` or `demo_features`. From a coding agent somewhere else, you can just ask: "Record a demo of the invoice reminders feature on my Mac."

## Watch and answer the agent from anywhere

While the run goes, you see the agent's own terminal, exactly as it looks on your Mac. It is live in both directions.

On a computer, click the terminal and type. You can answer the agent, approve something it asks, or steer it, as if you were at your Mac.

On a phone, type in the message box under the terminal and tap send. Your message reaches the agent as one message, even if it has several lines. A row of keys above the box gives you what a phone keyboard lacks: esc, enter, tab, the arrows and ^C to interrupt the agent.

The first time Claude Code opens a repo folder, it asks whether you trust the folder. Answer it from the same terminal.

Once the demo is uploaded, **Open in Studio** appears while the agent's session stays open. Type `/exit` to end it, or it ends by itself a few minutes after the upload.

On the Mac, tday.com for Mac opens a run window with the same terminal and a **Stop** button. It opens without taking focus, so it does not interrupt anyone using the Mac. Click **Show** in **Demos from anywhere** to bring it back.

## What runs on your Mac and what leaves it

tday.com for Mac starts the agent in your repo with only tday.com's demo tools. It tells the agent you may not be at the computer, so it should make its own choices and ask only when it must.

- **Ids only.** The request names features and docs sections by id. Their titles, and anything else a teammate could type into tday.com, never reach the agent as instructions.
- **No code changes.** Claude Code runs without its file-editing tools, and Codex runs in its workspace sandbox. The agent starts a separate copy of your app with its own data, and the demo tools check the repo is unchanged at the end.
- **It asks instead of guessing.** If the app would use shared or live data, the agent asks for your OK before it records.
- **Only you can type into it.** The terminal opens only for your own signed-in tday.com session, never for an API key or the MCP server.
- **One run at a time.** The Mac is kept awake while it records, and a run is stopped after 90 minutes.

What leaves your Mac is the recorded footage of your app, once it passes tday.com's checks. While the run goes, the terminal is relayed to your browser through tday.com. Anything the agent shows there, including code it prints, passes through tday.com and is kept for a few hours so the page can redraw it. The full log stays on your Mac, under **Show the last run's log**.

To stop it all, turn off **Let tday.com start demos on this Mac**. Demos still waiting for that Mac are cancelled.

### If a run fails

| Message | What to do |
| --- | --- |
| Your Mac did not pick this up | Open tday.com for Mac on that Mac and try again. |
| Claude Code (or Codex) is not signed in on this Mac | Run `claude` (or `codex`) once in a terminal on the Mac and sign in. |
| ... hit its usage limit on this Mac | Wait for your Claude or Codex limit to reset, or switch agents. |
| Add your copy of (repo) in tday.com for Mac | Add that repo in **Demos from anywhere** on the Mac. |
| ... ended without uploading a demo | Scroll back in the terminal, or open **Show the last run's log** on the Mac. |

## Frequently asked questions

### Can I record a product demo from my phone?

Yes. Ask for the demo on tday.com in your phone's browser, and your own Claude Code or Codex records it on your Mac. Open full view gives you the run's page, with a message box and keys such as esc, enter, the arrows and ^C.

### Does tday.com for Mac need to be open?

Yes. A demo only starts while tday.com for Mac is open. A demo asked for while it is closed waits 30 minutes, then fails with a note to open the app.

### Can someone keep using the Mac while it records?

Yes. The agent records the feature in its own browser, and the run window opens without taking focus.

### Can the agent change my code during a remote run?

No. Claude Code runs without its file-editing tools and Codex runs in its workspace sandbox. The demo tools check the repo is unchanged at the end.

### How long can a remote run take?

A run is stopped after 90 minutes. Only one run happens at a time, and the Mac is kept awake while it records.

## Sources

1. [Demos from anywhere](https://docs.tday.com/demos-from-anywhere), tday.com docs
2. [tday.com for Mac](https://docs.tday.com/mac-app), 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

- ![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.

- ![tday.com's editor with a narration line selected and the voice track on the timeline.](https://tday.com/landing/demos/editor-line.webp)

    Guides  November 18, 2026  6 min read

    ### [How do you record a product demo on a Mac?](https://tday.com/blog/record-a-product-demo-on-a-mac)

    Record a product demo on Mac with built-in tools or tday for Mac. Capture your screen and voice, then trim, edit and share the take in Studio.

---

## 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.
