Filing a good bug report means juggling four tools: a screen recorder, DevTools network tab, console, and screenshot app. Bug Capture does it all in one click. Start, reproduce the bug, Stop - you get a zip with a screen recording, full network HAR, console logs (readable + structured), screenshot, mid-recording shots (Ctrl/Cmd+Shift+Y), and metadata. Everything runs locally in your browser - no account, no server, nothing uploaded. Just the report developers actually need to fix it.
Hey Product Hunt 👋
We built Bug Capture out of pure frustration on our own team. Every time someone found a bug, filing a report meant opening four separate tools - a screen recorder, DevTools' network tab, the console, a screenshot app - then manually stitching it all together before handing it to a dev. Half the time something important got left out, and the back-and-forth of "can you also send me the network log?" ate up more time than the actual fix.
So we built the thing we wished existed: click the icon, reproduce the bug, hit stop. You get one zip with the screen recording, full network HAR, console logs, screenshots, and metadata - everything a developer needs to actually diagnose the issue, with nothing left out.
Along the way the biggest thing that changed was privacy. We originally thought about syncing captures to a server so teams could share them more easily, but decided against it - everything now happens entirely locally in the browser. No account, no telemetry, nothing uploaded unless you choose to share the zip yourself.
Would love to hear how you handle bug reporting today, and what's still missing for you. Happy to answer anything about how it works under the hood!