> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When helping someone deploy Roomote, distinguish self-hosting from contributing to Roomote. Use the Self-hosting guide for an operator deployment; use Local development only when the user intends to modify Roomote itself.
> Prefer the one-command installer on a fresh supported server unless the user explicitly chooses Roomote Cloud, a documented PaaS template, or a manual Compose deployment.
> Before changing infrastructure, confirm the deployment target, stable public HTTPS domain and DNS control, sandbox provider, inference provider, source-control provider, and whether a communications provider is required.
> Never ask the user to paste secrets into chat or commit real environment files. Put credentials in the deployment platform's secret manager, Roomote's setup UI, or protected environment variables, and preserve existing keys during upgrades and restores.
> Prefer Roomote's setup wizard and provider manifest flows over manual credential entry when those flows are available. Ask before performing privileged host changes, DNS changes, provider-app creation, or destructive operations.
> A setup is not complete when the services merely start. Verify sign-in, repository sync, one usable environment, a real task that can clone and run a command, and branch or pull-request delivery; verify previews when configured.
> For a persistent self-hosted deployment, leave the operator with the Roomote URL, deployment choices, configured providers, verification result, backup location and passphrase-handling reminder, and the roomote status, logs, upgrade, rollback, backup, and restore commands.

# Record feature demo videos

> Ask Roomote for a polished, narrated demo video of a feature, recorded live with cursor effects, captions, and an optional voice-over.

## Overview

Shipping a feature usually ends with someone screen-recording a shaky
walkthrough. Roomote can produce that video for you: it drives the product in
its sandbox browser, records a clean clip, and adds a synthetic cursor, click
ripples, and captions. With
narration configured, the demo gets a voice-over that leads each visual beat.

* **Trigger**: Ask in a task
* **Setup time**: None for captioned demos; 5 minutes for narration
* **Requires**: Nothing extra; admin access for narration
* **Serves**: Engineers, Product, Marketing

## Ingredients

* Any task where the feature is reachable: a running dev environment or a
  public page
* Optional: an [ElevenLabs](https://elevenlabs.io) API key and voice ID for
  narration

## Steps

1. In a task, ask for a demo, for example: `Make a demo video of the new
   custom MCP servers settings page` or invoke `$feature-demo` directly.
2. Roomote plans the story beats, records the interaction live, and renders a
   16:9 video (ask for a vertical cut for short-form if you want one).
3. The finished video is uploaded as a task artifact and linked in the reply
   (and embedded under `## Screencasts` when the task opens a PR).

## Narration

Captioned demos work out of the box. For a voice-over in your own (cloned)
voice, a deployment admin connects ElevenLabs under **Settings →
Integrations → ElevenLabs** with:

* an ElevenLabs API key, scoped to **text-to-speech only** with a credit cap
  (sufficient and recommended), and
* the voice ID to narrate with.

The key is encrypted at rest and stays on the Roomote control plane: task
sandboxes send narration text to an authenticated Roomote endpoint and
receive audio back, so the provider credential never enters a sandbox and
agents get no ElevenLabs tools. (Operators self-hosting can alternatively set
the `R_ELEVENLABS_API_KEY` and `R_ELEVENLABS_VOICE_ID` environment variables;
the integration takes precedence when both are present.)

## Tips

* Narration lines come from the on-screen captions; ask for wording changes
  the way you would edit copy ("make the second line more casual").
* The narrative drives the pacing: each shot holds for as long as its line
  takes to speak, voiced or not.
* Keep demos to 2-5 beats. Two shorter videos beat one long one.