Launching today
BugShot
Discover, fix, capture, and report bugs in one shot
107 followers
Discover, fix, capture, and report bugs in one shot
107 followers
Catch a bug and file a complete report from Chrome's side panel. Captures, console/network logs, and environment attach automatically. Or tweak the CSS live and send the before/after side by side. AI drafts it for you. Free, no account, straight to your tracker.
It would be awesome if Bug Shot could automatically generate clear reproduction steps from the captured session. That would make it even more valuable.
BugShot
@bernard_lewis
I love this suggestion because it's exactly where I think bug reporting should go.
BugShot already records your interactions as a structured timeline, and the AI Draft feature turns that into a title, description, and reproduction steps.
The hard part isn't capturing everything—it's knowing what to leave out. Right now it mainly looks at the last ~20 actions, so it's great at explaining what happened right before the bug, but not yet at distilling a longer session into the few steps someone else can reliably follow.
I'd love for BugShot to get there.
The no account requirement is a great touch .Curious does it support recording user interactions leading up to the bug as well?
BugShot
@alan_gregory
Yep! BugShot starts recording interactions as soon as it's running, so by the time you decide to report a bug, the history is already there.
It captures things like clicks, typing, toggles, dropdowns, drags, and navigation, then lines those up with the console and network logs so developers can see what you did alongside what the app was doing.
We were pretty careful about privacy, too. Passwords and payment fields are masked before they're ever stored, and we don't record cursor coordinates—just the elements you interacted with.
One limitation today: the action timeline is only attached when you record a video, not when you capture a screenshot. A few people have asked for that already, and I think it makes sense to support both.
This is a great idea. I do have a couple questions. You mention CSS editing in realtime. Who is the target audience for this feature? Would they know the cascading impact of such a change? A higher level CSS change could break or alter other areas of the site. Also, does it work with minified or compiled CSS? If so how does the actual line number of the CSS update get communicated back to the developer? You mention the network traffic at the time of the bug is attached, this to me is the most interesting part. Is a HAR file being attached? Is it parsed with data analysis? In my world CSS is rarely the case but the underlying dependencies, APIs or libraries are. The HAR analysis could really help debug the issue. Great work, I like where this is going.
Sinhyeok — the redaction thread with Hakan and the OAuth-proxy answer to Gal are exactly the kind of detail that builds trust here. I'm coming at this from the other side of your usual user, though: WinBidIQ's customers are federal-contracting SMB owners, not developers, and when one of them hits a bug they don't know what a console log is — I get "it's broken" over email and have to reproduce it myself with no repro steps. Is there a lightweight capture flow a non-technical external user could trigger — a link they click, describe the issue in plain English, and it still grabs console/network/environment for me — or is BugShot built around the reporter already having the extension and knowing what they're looking at?