Feature

Steps to reproduce, written by the browser.

Nobody outside your team writes good steps to reproduce a bug. They write “it does not work”, and then you spend two days guessing. So the widget keeps the last fifty things the person did and sends them with the report, along with the browser, the screen and the time zone they were on.
Start freeNo credit card required.
attached to every bug report
Chrome 131 · macOS 15.1 · 1440 × 900 @2x · Europe/Madrid · dark
Page loaded in 1.4 s

48  navigate   /pricing
47  click      button "Start free trial"
46  navigate   /signup
45  submit     form#signup
44  navigate   /onboarding/team
43  click      a "Skip for now"
42  click      button "Create project"   ← report filed here

What gets recorded

Actions, not keystrokes

The distinction matters, both for what you get and for what you have to declare in your privacy policy. The widget records that a button was pressed. It never records what was typed into the field next to it.
Clicks, with the visible label
A CSS selector, plus the text on the button or link — so "clicked Apply code" reads as English rather than as div > div > button:nth-child(3).
Form submissions
Which form was submitted, and when. Never a single character of what was in it.
Page changes
Including client-side navigation, so a single-page app shows a real path rather than one URL for the whole session.
Browser, screen and time zone
Browser and version, operating system, window and screen size, pixel density, language, light or dark mode, and page load time.

Why it exists

“Cannot reproduce” is usually missing context, not a missing bug

A report closed as not reproducible almost always means the person was on a different browser, a narrower window, another time zone, or arrived by a route you never tried. All four of those are in the trail. We wrote more about the shape of a report an engineer can act on in this post on steps to reproduce.

Held in the browser

Nothing leaves the page until they press send

The trail lives in the visitor’s own tab and is thrown away when they close it. There is no background upload, no cookie and no identifier that could follow anyone between sites — the field-by-field list is on the widget data page.

FAQ

Questions

Does this record what people type?
No. The widget stores which element was clicked and which form was submitted, identified by a CSS selector and, for buttons and links, their visible text. The contents of any field are never read, never stored and never sent.
How is this different from session replay?
Session replay records everyone continuously and reconstructs a video. This keeps a short list of actions in the visitor own browser, sends it only if they file a report, and discards it when they close the tab.
How far back does the trail go?
Up to fifty steps, kept as a ring buffer. On a page somebody has had open all afternoon you get the most recent fifty rather than the first fifty, which are almost always the ones that matter.
Can I turn the technical collection off?
Yes, per project, with one switch. With it off, reports arrive with the description and contact details only: no steps, no browser details and no JavaScript errors. Nothing else about the widget changes.

Look at your own trail.

Click around this page, then open the widget and send a report. The steps you just took will be sitting inside it.

Start freeRead the docs