Features / Ask your tape
Chat with your session replay data
The dashboard question nobody asks because it means opening a dashboard. Now it's just a question.
What it does
- Answers cite the tape, not a vibe Every answer names the session and the timestamp it came from, so “there’s a problem on checkout” is followed by a link that opens exactly where the problem happened, not a summary you have to trust.
- Same console, past history included Ask from the deck page’s chat panel and pick up a previous conversation instead of re-asking from scratch — the panel is New/History, not a single disposable prompt box.
- Reads across many sessions in one question “Any problems today?” isn’t answered by one tape. The assistant scans across the day’s sessions for the ones with errors, rage clicks, or abandonment, and reports back the pattern, not just an instance.
- The same reasoning your agent gets over MCP This is the human-facing version of the exact same underlying query surface your coding agent uses over MCP — ask here to explore, connect MCP when you want an agent to act on the answer.
Most session-replay tools answer one question well: “show me this specific recording.” They answer a much more common question badly, or not at all: “did anything go wrong today, and where?” That question requires reading many sessions, not one, and reading is exactly the part nobody has time for.
Ask solves that by putting the question in a chat box instead of a filter sidebar.
What it’s actually doing
Type “did any users have a problem today?” and the assistant doesn’t paraphrase a dashboard metric back at you. It queries the same event data your MCP server exposes to agents — sessions with errors, rage clicks, dead clicks, abandoned forms — and reads the transcripts of the ones that match. The answer it gives back names a specific tape and a specific second, because that’s what it actually looked at to produce the answer.
That distinction matters more than it sounds. A dashboard tile that says “errors: 14” is a count. An answer that says “checkout failed for six people between 2 and 3pm, here’s tape 3E71 at 0:19” is a lead you can act on immediately, because the next click opens the recording at the exact frame.
Why this beats scrubbing video yourself
Nobody opens a session replay tool and watches forty minutes of footage looking for the interesting five seconds. In practice, most recorded sessions never get watched at all — they sit as an insurance policy for the day something goes wrong and somebody finally goes looking.
Ask inverts that. Instead of recordings waiting for a human to have a reason to open one, you ask the reason first, and only the sessions that answer it ever get opened. The video still exists and still matters — see Replay & transcripts — but it stops being the first thing you have to sit through.
Where the history matters
The chat panel keeps a history, on purpose. “Signup drop-off, this week” and “rage clicks on pricing” are questions worth re-asking as the week goes on, and a saved thread means you’re extending a line of inquiry instead of re-explaining the context every time. It’s built as an ongoing conversation with your own data, not a single-shot query box.
When to reach for MCP instead
Ask is for you, in the dashboard, exploring. If the question is really “an agent should notice this on its own and go fix it,” that’s a job for the MCP server — same underlying data, but wired into Claude Code or Cursor so the loop closes without you asking anything at all.