Bugpilot
Bugpilot is a Chrome extension that captures browser state including console errors, network requests, DOM, clicks, and screenshots, exporting as AI-ready Markdown. It runs 100% locally with no servers, accounts, or telemetry. Free forever, with a one-time $28 Pro option offering additional features like React component state.
Bugpilot: Turn errors, DOM, + screenshots into an AI-ready Markdown | Product Hunt
Bugpilot
Launched this week
Turn errors, DOM, + screenshots into an AI-ready Markdown
85 followers
Turn errors, DOM, + screenshots into an AI-ready Markdown
85 followers
Visit website
Chrome Extensions
•
Testing and QA software
Built for vibe coders using Claude and ChatGPT. Bugpilot captures your whole browser in one click — console errors with stack traces, network requests, DOM state, clicks, and screenshots — then exports it as clean, AI-ready Markdown your assistant can actually read. 100% local: no servers, no accounts, no telemetry, always-on redaction. Pro adds React component state, 5 AI-optimized export formats, and unlimited history. Free forever, $28 one-time, 14-day refund, no subscription.
Overview
Reviews
Alternatives
Built with
Team
More
Free
Launch tags:Chrome Extensions•User Experience•Developer Tools
Launch Team / Built With
Subscribe
Promoted
Maker
📌
Hey Product Hunt, I'm Malindu, building Bugpilot solo out of Colombo. Like most of you, I build with Claude and ChatGPT now. But the AI writes the code, and I'm still the one who has to test it. So I'd open Chrome DevTools, click around, and there's almost always a bug or two waiting. Then comes the part I started to dread: explaining it back to the AI. Screenshot the console, copy the error, describe what I clicked, paste it all in, get a fix, test again, find another bug. Back and forth, every time. Two things bothered me about that loop. It ate my time, and it ate tokens. I was pasting walls of messy logs just to give the AI enough to work with. So I built Bugpilot for myself. Record, reproduce the bug, Stop, Copy. It captures the whole browser, console errors with stack traces, network requests, DOM state, clicks, screenshots, and hands the AI clean Markdown instead of a screenshot dump. Less of my time, fewer tokens. It runs 100% locally. No servers, no accounts, no telemetry. Nothing leaves your machine. It's been useful enough for me that I figured it might help some of you. Free forever, Pro is a one-time $28. Try it out. And if you find it useful but can't afford Pro, DM me and I'll send it to you for free. Would love to hear what breaks or what's missing.
Report
2d ago
@malindu_perera great idea! will test it!
Report
1d ago
The token argument is underrated. Everyone talks about the time wasted re-explaining bugs to the AI, but pasting walls of raw console logs also burns context window for nothing. Clean structured Markdown instead of a screenshot dump is better for me and for the model.
The "DM me and I'll send Pro for free" offer says a lot about how you're building this. Respect.
One thing I'd want to know: how does the always-on redaction decide what's sensitive? Auth tokens in network requests are the obvious one, but what about things like emails in API responses?
Installing the free version today. Good luck with the launch, Malindu.
Report
18h ago