Repro — Capture & replay frontend bugs

Capture a frontend bug once, then replay it. One click records screen, console, network, actions and storage to find the bug.

Repro is a bug reproduction and session replay recorder for developers and QA teams. One click records everything happening in the browser tab — screen video, console logs, network requests, clicks and keystrokes, storage changes, and performance metrics — so you can replay the exact moment a bug happened and see why. It's a flight recorder for your web app that turns "can't reproduce" and "works on my machine" into a single shareable recording. Reproducing a front-end bug is the hard part. By the time you've read the bug report, the console has scrolled away, the failing network request is gone, and the state that caused it has changed. Repro captures the whole picture the first time it happens, so you never lose a reproduction again. What Repro captures in every recording Screen recording of the tab, streamed to disk as it records so memory stays flat even during long debugging sessions. Console logs — every log, warning, and error, with full arguments and stack traces (no more "[object Object]"). Network requests — every request with method, status, timing, headers, and request/response bodies. JSON is pretty-printed and browsable as a collapsible tree. User actions — clicks, typed input, key combos, and page navigations, so you have the exact steps to reproduce the bug. Storage changes — before/after diffs of localStorage, sessionStorage, cookies, and IndexedDB. Performance metrics — FPS and JS heap over time, Core Web Vitals (LCP, CLS, FCP, TTFB), and long tasks that blocked the main thread for more than 50ms. Page HTML & CSS at capture time, so the markup and styles behind the bug are preserved too. Replay mode: debug by watching it happen again This is where Repro earns its name. Instead of scrubbing through a video and guessing, open a capture in Replay mode and watch the screen video, console, network, storage diffs, and performance chart move together in perfect sync. Click any log or network request to jump the video to that instant. Click a long task to see exactly what blocked the main thread. Jump straight to the first error. The entire debugging timeline is at your fingertips. Why developers and QA teams install Repro Turn "can't reproduce" into a shareable recording. Send a colleague a single file that shows — and proves — the bug. Debug faster. Stop re-running the app hoping the bug appears again. Capture it once, then study it as long as you need. Nothing slips away. The failing request, the console error, the state change, and the on-screen result are all captured together and lined up in time. Write great bug reports effortlessly. Export a self-contained report and attach it to Jira, GitHub, Linear, or any issue tracker. Built for real debugging workflows Keyboard shortcuts to start, stop, and pause recording without breaking focus. Markers to flag important moments while recording so you can find them instantly later. Screenshots — grab the visible tab or pull a frame straight from the video, with a preview before you add it to the report. Global search across console and network, plus filters by type and status. Trim before export, so you share only the relevant window. Rename captures to something meaningful instead of a raw page title. Light and dark themes, and a Captures library to revisit, import, and manage past recordings. Export and share bug reports Self-contained HTML report you can open in any browser. ZIP bundle with the report, raw data, and video. HAR export for use in other network and debugging tools. Optional Google Drive upload (off by default) that produces a shareable link to the bundle and the video. Private by default Everything is stored locally on your machine. Recordings save to your Downloads folder or a folder you choose. Cloud upload is entirely opt-in — if you never turn it on, nothing ever leaves your computer. Built for AI-assisted debugging (MCP) Repro can write a structured data.json alongside each recording and ships an optional local MCP server. Point your AI assistant (Claude, Cursor, or any MCP client) at your captures and it can read the errors, failed requests, slow requests, timeline, storage diffs, and even the page HTML/CSS — then help you find and fix the bug. Install Repro, hit record the next time something breaks, and never lose a reproduction again.