“Steps to reproduce” becomes a twenty-second clip.
Record your screen and voice from the browser and get a shareable link.
- Who it is for
- Your own team, mid-flight: testers dogfooding before a release, and anyone who has ever tried to describe a visual bug in a sentence.
- The situation
- Written repro steps are a translation of something you just watched. They lose the timing, the exact click order, and the thing on screen you cannot name. Recording what happened skips the translation.
Four steps, and you only do the first one.
- 01Hit record in the browser
Your screen and your voice together, so what you say lands next to what you did.
- 02Snapshot the moment it happens
Grab snapshots mid-recording and circle exactly what you mean, without stopping the take.
- 03Get a shareable link
Drop it straight on the task. The clip is the repro step.
- 04It is a signal, not just a video
The recording is transcribed and read against the project's goals, so a session becomes bugs, regressions and rough edges rather than a file someone has to watch.
- Testers running an iOS or Android emulator capture what they see over screen-share, so mobile work goes through the same surface.
- Recording a walkthrough for a stuck user works the same way — record a quick tour inside your own app and send the link.
What it is called inside the product.
Every capture route works in every project — a template only decides which one you reach for first. These are the ones this surface gives you.
Capture your screen and your voice together, so what you say lands next to what you did.
The same five hops, whichever door it came through.
Nothing along this chain is a summary. Each anchor keeps its offsets into the transcript, so the action item at the end still points at the words that were said.
- 01Capture
One recording, upload, paste, or widget submission.
- 02Signal
It lands as a timestamped transcript with the recording attached.
- 03Anchors
The lines that answer a goal get pulled out verbatim and tagged.
- 04Insights
Anchors group into a finding, often spanning more than one goal.
- 05Backlog
Findings become action items, each linked back to its evidence.
2 projects reach for this first.
Every workspace is seeded with all six projects, so none of this is a choice you make on day one. These are the ones whose capture card puts this surface at the top.
Your team dogfoods and captures issues before users hit them.
Record a walkthrough and turn it into notes on how it works.
Also available in Meeting memos and User testing.
Try it on your own product.
Create a workspace and the projects are already there, goals and capture order set up. Nothing to configure before your first capture.