Debug Logs Catcher

Debug Logs Catcher is an internal Enreach tool built to make it trivial for QA, support, and developers to file actionable bug reports against the myXpad / myIstra front-ends. It attaches the Chrome DevTools debugger to a tab on demand and records everything you need to reproduce, share, or diagnose an issue — without leaving the browser. How to use: 1. Open the site you want to debug (any http/https tab). 2. Click the extension icon in the toolbar to open the popup. 3. Click Start — Chrome shows its native "started debugging this browser" banner. 4. Reproduce the issue in the tab. The counters update in real time. 5. Click Stop when you are done. 6. Click Export to download a gzipped JSON file with the capture. The extension only runs on http/https pages. Chrome blocks debugging on its own pages (chrome://, chromewebstore.google.com, other extensions) — the popup shows a friendly notice on those tabs. What it captures while attached: • WebSocket frames sent and received, with payload and timing • Network requests and responses (URL, method, headers, request and response body, status, size). Bodies are captured for data content types up to a configurable size limit; page assets and binary responses are skipped • Console output and uncaught exceptions. Call arguments are serialized via the Chrome DevTools Protocol to a configurable depth (default one level plus a preview of the next): primitive values verbatim, nested objects/arrays expanded, own enumerable properties only, no getters invoked • Environment metadata: /build.json if served, plus the decoded payload of the first JWT bearer token seen (tenant, user, server context) Other features: • Auto-capture domains — list the hosts you debug regularly and the extension attaches automatically the next time you visit them. The extension asks Chrome for permission once per domain, granted by you through Chrome's native prompt. No site is accessed without your explicit consent. • Add current site — one click on the popup adds the current tab's host to the Auto-capture list, asks Chrome for permission, and you are set up. • Redaction by default — sensitive headers (Authorization, Cookie, Set-Cookie, X-Application, X-Csrf-Token, X-Xsrf-Token) and Bearer … tokens are stripped from exports; secret-bearing fields in bodies, console objects and the decoded JWT are masked by key name (passwords fully, API keys / tokens / session ids partially). Disable in Settings if you control the recipient. • Gzipped JSON export — click Export for a compact .json.gz, or Shift+click for raw .json when you need to read it directly. • Bounded buffers — capped at 5 000 WS frames, 10 000 console entries, and 5 000 network requests so a long session does not blow up memory. • Per-tab badge — shows when capture is running on tabs other than the active one, so you do not forget the debugger is attached. • Theme-aware UI — the popup and the options page follow your system light or dark theme. Everything stays on your computer. The extension makes no network call of its own, has no analytics, and the publisher never sees your data. Source code and privacy policy: https://github.com/JulienAndre26/debug-logs-catcher.