Bugpilot

Hit record, reproduce the bug, hit stop. Bugpilot packages console, network, and DOM context as an AI-readable Markdown report.

You hit a bug in your web app. You open Claude or ChatGPT to ask for help. Without Bugpilot, here's what happens next: → You screenshot the console → You screenshot the network panel → You copy-paste the error message → You describe what you clicked, in plain English → The AI asks follow-up questions because it's missing context → You go back to DevTools, screenshot more, paste more → Repeat until the AI has enough to actually help With Bugpilot, here's what happens instead: → Click Record in the Bugpilot popup → Reproduce the bug in your app → Click Stop → Click "Copy as Markdown" → Paste into your AI → The AI has the full picture: console errors, network requests, DOM state, user actions, even React component state — all in one structured document That's the whole product. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT BUGPILOT CAPTURES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Console events — errors, warnings, logs with timestamps and stack traces. Network requests — URLs, methods, status codes, response previews. The kind of detail you'd dig out of DevTools, packaged automatically. DOM state — outer HTML at the moment of capture plus the click target that triggered the error. Your AI sees what the user actually clicked. User actions — every click, every form input, every navigation. The reproduction steps, recorded for you. Framework state (Pro) — React component tree, props, and hook states at the moment of failure. Your AI sees the props that caused the bug, not just the stack trace. Screenshots (optional) — WebP frames at record start, on console errors, and at stop. Off by default. When enabled, each frame is linked by metadata to the timeline event that triggered it, so your AI can match image to moment. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AUTOMATIC REDACTION — ALWAYS ON ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Before anything is stored, Bugpilot redacts these patterns: - Passwords - Email addresses - Credit card numbers (including partials, via Luhn validation) - JWT tokens - API keys - Authorization headers - URL tokens Redaction can't be disabled. Sensitive values are replaced with [REDACTED:type] markers in the output. The unredacted value never persists. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PRIVACY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Everything runs locally in your browser. - No accounts - No servers - No telemetry - No tracking - No analytics Bugpilot has zero infrastructure that could see your captures. Your debugging data stays on your machine until you choose to paste it into your AI assistant. The only data that ever leaves your browser is your email address, sent to our payment partner ExtensionPay if and when you purchase Pro. ExtensionPay's privacy policy applies to that data. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BUILT FOR DEVELOPERS USING AI CODING TOOLS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Bugpilot is built for the way modern developers actually work — pair programming with Claude, debugging with ChatGPT, refactoring with Cursor. Pro tier picks the right format for each assistant: - Claude XML — structured for Claude's strengths - OpenAI JSON — structured for ChatGPT and o1 - Reddit-friendly Markdown — for forum posts and issues - Single-file HTML — self-contained, shareable reports - Markdown + JSON .zip — bundles for ticket attachments Plain Markdown works for Cursor, Lovable, v0, Bolt, Gemini, and any AI that reads code. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PRICING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Free forever: - Full capture engine (console, network, DOM, user actions) - Automatic redaction (7 patterns, always on) - 10-session capture history - Markdown export - Download .zip with screenshots Pro lifetime — $28 one-time: - 5 AI-optimized export formats (Claude XML, OpenAI JSON, Reddit-friendly Markdown, single-file HTML, Markdown+JSON .zip) - Framework state capture (React component tree, props, hook states) - Unlimited capture history - Priority email support No subscriptions. No recurring billing. 14-day no-questions-asked refund. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ABOUT THE CHROME YELLOW BANNER ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ When Bugpilot is recording, Chrome shows a yellow banner: "Bugpilot started debugging this tab." That's Chrome's transparency feature, not a warning. It tells you the extension is using the debugger API to capture network requests. It only appears during active recording. It disappears the moment you click Stop. We think transparency about what extensions can see is a feature, not a bug. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Bugpilot is built by Rooverr Technologies LLC. Privacy: https://bugpilot.roo360.com/privacy Refund policy: https://bugpilot.roo360.com/refund-policy Help: https://bugpilot.roo360.com/help Contact: bugpilot@roo360.com bugpilot.roo360.com