This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Repro records a bug as video plus the console, network, storage and performance data behind it, then replays them on one timeline — scrub to the moment it broke and see the request that caused it. The report is a DevTools panel, not a log list: Console, Network, Actions and Performance reveal themselves as the video plays. Copy any request as HAR to seed a test. Trim the clip and the logs slice to match. Captures stay in your browser. No account, no upload, free.
Hey Product Hunt 👋
Every frontend team has the same argument on repeat:
QA: "The save doesn't work sometimes."
Dev: "It works on my machine—send me the steps."
QA: sends a screen recording of a spinner
Dev: "What was the network doing?"
Nobody knows, because DevTools is never open when the bug happens. And by the time anyone opens it, the state that caused it has been refreshed out of existence. Ticket closed as cannot-reproduce. Two sprints later, a customer hits it, and it comes back with a priority label.
That's the actual gap. Bug reporting got solved years ago — plenty of good tools attach a video and a log dump to a ticket. Bug reproduction didn't. Because the bugs that survive to production are almost never "an error was thrown." They're ordering two requests race and the slower one wins. A debounced autosave lands after the explicit save and quietly overwrites it. A response comes back 200 OK with an errors array in the body and every monitoring tool in the stack decides everything is fine.
You cannot see that in a video. You cannot see it in a list of logs beside a video. You need both on the same clock, and you need to scrub.
So Repro's report IS a DevTools panel—video on the left, Console / Network / Actions / Performance / Application on the right, revealing as the video plays. Drag to 0:06 and the network list shows what was in flight at 0:06. Exactly.
Three things that came out of using it on real bugs:
• Copy HAR at any scope, so the capture that proved the bug seeds the test
• Trim the clip and the LOGS get sliced to match—4 minutes becomes the 8 seconds someone will actually read
• An MCP server so Claude or Cursor can read a capture straight off your disk: errors, request bodies, storage diffs, DOM, and CSS. Plus, on-device triage in the report itself (Chrome's Gemini Nano—no key, no API call)
And the constraint I designed around from day one: captures live in IndexedDB on your own machine. No account, no upload. If your company's answer to "can we send a recording of production to a third party?" is a six-week conversation with legal, that's who this is for.
Free. Nothing to sign up for.
Two things I'd genuinely like to hear:
What's the bug that beat you? The intermittent, cannot-reproduce kind—I collect these, and they drive the roadmap.
What's missing? Jira/Linear integration is the top request so far, and I want to know which one to build first.
I'm here all day.
No comment highlights available yet. Please check back later!
About Repro — Capture & replay frontend bugs on Product Hunt
“Replay any frontend bug as a DevTools session”
Repro — Capture & replay frontend bugs was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #50 on the daily leaderboard. Repro records a bug as video plus the console, network, storage and performance data behind it, then replays them on one timeline — scrub to the moment it broke and see the request that caused it. The report is a DevTools panel, not a log list: Console, Network, Actions and Performance reveal themselves as the video plays. Copy any request as HAR to seed a test. Trim the clip and the logs slice to match. Captures stay in your browser. No account, no upload, free.
Repro — Capture & replay frontend bugs was featured in Chrome Extensions (52.8k followers), Productivity (659.6k followers) and Developer Tools (518.5k followers) on Product Hunt. Together, these topics include over 253.4k products, making this a competitive space to launch in.
Who hunted Repro — Capture & replay frontend bugs?
Repro — Capture & replay frontend bugs was hunted by Aditya Kumar Tiwari. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Repro — Capture & replay frontend bugs stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Aditya Kumar Tiwari