Auto-file bugs to GitHub issues with console logs and network requests
Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS…
In plain words
This browser extension helps teams report bugs more efficiently by automatically capturing console logs, network requests, session replay, timestamps, URLs, browser details, OS information, and device specs. Designed for product managers and QA teams, it streamlines bug reporting to GitHub issues with just a few clicks, eliminating manual data entry and providing developers with comprehensive reproduction details needed for faster debugging.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS and device specs, and wifi speed. With this extension, it’s faster than the old-school way to report bugs (a few clicks, plus no switching tabs). And, for the developer receiving the bug reports, it should be faster to debug because all the information is right there. We started with a Chrome extension and soon we’re going to build extensions for other browsers too. (Which should we add next? We’re thinking Firefox). We built this in react, typescript, mobx, and graphql. It’s privacy-focused: everything happens locally on your browser until you choose to share, and you can even select which specific websites you want the extension to run on in settings. Today we shipped an integration with GitHub - meaning it’s now just a few seconds to create a really good GitHub issue. I hope you check it out and I hope it helps bring about the end of bad tickets for you and your team! If you have any suggestions or questions, please let me know here!
Does the same job
all alternatives →
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com
Launched alongside, November 2022
the whole month →
- TC
I made a thing! In 2014, I was holding a stack of iPhones and thought to myself: "Hey, if I had each phone display a playing card, I could click a button and they'd shuffle themselves" I pared that idea all the way down to this: trading cards made of e-ink displays. Right now, each card costs me about $20 each, but with only a bit more scale, I think I can get that down to $10. In doing this project, I learned how to design electronics and circuit boards. I learned Rust and wrote my first driver, I upped my CAD skills, 3D printed, and did my first resin casting. I generated the images on the…
Dev tools · 2022 · wyldcard.io
