Every bug report I've ever received started with a round of questions. Which browser. What did you click. Was there anything in the console. By the time the answers come back the tab is closed and nobody can reproduce it. I built this so the answers arrive with the report. You press one button and it captures a screenshot or a short recording along with the console output, the network requests, the clicks and scrolls, and the browser and screen size. You get a link. The part I care about most: the person reporting never needs an account. Asking a customer to sign up before they can tell you something is broken is how you stop hearing about bugs. Rather than describe it, here's a real report — exactly what a developer receives, no login, no signup: https://session-replay.com/repla... One deliberate choice: it isn't a DOM recorder. I'm not serialising the page and replaying it, because that falls apart on canvas, shadow DOM and cross-origin iframes, and it captures more than most people expect. It's a recording plus structured data on one timeline, so you see what they saw next to what the browser was doing. Chrome and desktop only for now, and no Jira/Linear integration yet — reports are links you paste. I'd like to know where the capture falls over on your app, or what's missing from a report that you'd actually need.

Session Replay

Bug reports with the console, network and clicks attached

Bug reports with the console, network and clicks attached