Recording tours

A tour is a recorded walkthrough of a flow in your app. You record it once by clicking through it yourself; SupaMaus replays it step by step for real users, and keeps it working as your UI changes.

Record a tour

1. Install the extension. Add "SupaMaus — AI Cursor for the Web" from the Chrome Web Store.
2. Connect it to your workspace. Go to admin.supamaus.com → Settings → Connect extension — one click.
3. Open your app in the tab you want to record, in the same browser.
4. Click Record in the extension's side panel.
5. Click through the flow. Each click becomes a step. Before you click, a hover preview shows exactly what will be captured (element type and name), so you know what you're recording before it's recorded.
6. Click Done when the flow is finished.
7. Review the steps in the side panel — edit titles and instructions, delete any mis-clicks.
8. Publish.

Multi-page flows

Recording survives navigation. If your flow moves across pages, keep clicking — the recorder picks back up on the new page and keeps appending to the same tour.

Crash recovery

If your browser or the extension closes mid-recording, SupaMaus keeps the draft. The next time you open the side panel, you'll be offered Recover last recording? for up to 24 hours after the interruption. After that window, the draft is discarded.

What happens after you publish

A published tour lands in your admin dashboard Library as an inactive draft — it is not shown to any user until you activate it. Review it, then flip it on when you're ready.

Each step is captured with several targeting strategies at once (accessible role and name, CSS selector, visible text, position), so a tour keeps finding its target even after small UI tweaks — you don't have to re-record every time a class name or layout shifts.

Once a tour is active:

• A nightly verifier replays every tour in a clean browser.
• If a step breaks, SupaMaus proposes a healed target for one-click review in your Inbox — rather than letting the tour fail silently in front of users.
• Users see a trust line on tours that are currently verified: "Verified guide · updated Xd ago."

Tours recorded by agents

Tours don't have to be recorded by hand — an AI agent can drive your app and record a tour the same way a person would. See Agents & MCP for how to wire that up.

Tours are half the picture

Tours teach the guide how to do things. For facts — pricing, policies, limits, FAQs — feed it your docs on the Knowledge base page. The guide blends both in its answers: a matching tour becomes "let me walk you through it," and factual questions get answered from your content, with sources.