BugScribe: Bug Reporter for QA & Developers

Capture console errors, failed network requests, steps and a screenshot, then write the bug report in one click. 100% local.

BugScribe is a one-click bug report generator for QA engineers, testers and web developers. It captures the JavaScript console errors, failed network requests, user steps and screenshot behind a bug, and turns them into a clear, ready-to-paste bug report in seconds. Stop retyping "what happened" into Jira, GitHub Issues or Slack. Open the page that is broken, click BugScribe, press Analyze page, and reproduce the problem. BugScribe records what actually went wrong while you work. WHAT BUGSCRIBE CAPTURES • Console errors and warnings: uncaught exceptions, unhandled promise rejections and the messages Chrome writes itself (blocked requests, CORS and certificate problems, deprecations), the same list the DevTools console shows • Failed network requests: URL, method, HTTP status (404, 500 and so on), network errors and timeouts • Steps to reproduce: your clicks and page navigation, written in plain words • A screenshot of the page, plus browser, operating system and viewport size • Iframes and workers too, including cross-site ones WHAT YOU GET • A bug report draft with a title, steps to reproduce, expected and actual result, environment details and the top issues ranked for you • An exact preview of what will be included, with every section switchable • Copy as Markdown to paste into GitHub, Jira, Linear or Slack • Download the report with its screenshot, or export the full log as PDF or Word PRIVATE BY DESIGN • Nothing is uploaded. No server, no account, no analytics. Everything stays on your device. • It records only the tab you analyze, and only until you stop. It does not run in the background on other sites. • Secrets are masked before anything is stored: tokens, JWTs, card numbers, API keys, sensitive URL parameters and (by default) email addresses • Typed values and password fields are never recorded, and request or response bodies are never read • Block specific sites in Settings and wipe all data with one click WHO USES IT • QA and manual testers filing reproducible bug reports • Front-end developers debugging console and network errors in production or staging • Support teams who need engineers to see what the customer saw • Teams in regulated or privacy-sensitive work who cannot send screenshots and logs to a cloud service HOW IT WORKS 1. Open the page with the problem and click the BugScribe icon. 2. Press Analyze page. BugScribe reloads the page once so nothing from its load is missed. 3. Reproduce the bug. Errors, warnings and failed requests are counted live. 4. Press Report this bug, review the preview, and copy or export it. GOOD TO KNOW • While BugScribe analyzes a tab, Chrome shows a bar saying "BugScribe started debugging this browser". That is Chrome's standard notice for access to the same data DevTools uses. It disappears when you press Stop capturing. • BugScribe cannot analyze Chrome's own pages or the Chrome Web Store. • Local AI report writing with Ollama, still entirely on your machine, is planned for a future version. Questions or feedback: wasifraza909@gmail.com Privacy policy: https://bugscribe-silk.vercel.app/privacy.html