Overview
Capture failed requests, errors and user actions from a failing web app, and turn them into an AI debugging prompt or bug report.
BugLens is a DevTools panel for debugging web apps. Open DevTools, choose the BugLens tab, start a session and use the app: BugLens records what went wrong, in order, next to what you did. WHAT IT CAPTURES • Failed API and REST requests (HTTP 4xx/5xx and network failures) with headers, payloads and responses • API errors hidden inside HTTP 200 responses, where the protocol reports them: GraphQL errors, JSON-RPC and tRPC errors, SOAP faults, gRPC-Web and Connect status • WebSocket connections: messages sent and received, close codes and errors • Server-Sent Events (SSE) streams: events, errors and reconnects • Console errors, uncaught exceptions and unhandled promise rejections • Clicks, form submissions and page navigations, so each failure shows the action that likely caused it WHAT YOU CAN DO WITH IT • Generate Prompt – a short, precise debugging prompt for Claude or another AI assistant, built from the captured evidence, including the exact page URL • Generate Bug Report – a QA-ready report with environment, steps to reproduce, the failing request and errors • Copy as cURL (bash, Windows cmd or PowerShell), Copy Request, Copy Response, Copy Headers • Resend a failed request, or replay a WebSocket or SSE stream, and compare the original result with the current one • Reproduce – repeat a saved session step by step; BugLens shows the original result next to the current one (Reproduced, Behavior Changed or Could Not Reproduce), even after button text or layout changed • Session History – your last 10 sessions, with names, summaries and reproduction steps OPTIONAL DEEP CAPTURE Off by default. When you turn it on (it asks for the browser's debugger permission), BugLens also captures WebSockets opened by Web Workers, every Server-Sent Event, and the exact bytes of gRPC-Web requests so they can be resent. The browser shows a debugging bar while it is on. PRIVATE BY DESIGN • No servers, no accounts, no analytics. Nothing is sent anywhere. • Secrets (authorization headers, cookies, API keys, passwords, tokens) are redacted from everything you copy, and from saved History. • Form field values and keystrokes are never recorded. HOW TO USE 1. Open the page you want to debug. 2. Open DevTools (F12) and select the BugLens tab (it may be under ».) 3. Press Start session, name it, and reproduce the problem. 4. Open a failure, then Generate Prompt, Generate Bug Report, Copy as cURL or Resend. BugLens works in the DevTools of the tab you are inspecting and records only while a session is running.
Details
- Version0.1.0
- UpdatedSeptember 29, 2026
- Size156KiB
- LanguagesEnglish
- Developer
Email
hlearn2022@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
BugLens has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
BugLens handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
