Debug Logs Catcher
- 32 users
- 5.001 rating
- #10,551in Developer Tools
Internal Enreach tool: capture WebSocket, console, network, and environment metadata from a tab. Export gzipped JSON.
by Julien Andre · 1 listing
- Users
- 32
- #10,551 of 31,410 in category
- Rating
- 5.00
- 1 rating · median 4.63
- Version
- 1.2.0
- 49.48 KiB · Manifest V3
- Access
- Low18/100
- 4 permissions
Description
As written by the publisher on the storeDebug 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
- Open the site you want to debug (any http/https tab).
- Click the extension icon in the toolbar to open the popup.
- Click Start — Chrome shows its native "started debugging this browser" banner.
- Reproduce the issue in the tab. The counters update in real time.
- Click Stop when you are done.
- 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
- postMessage traffic delivered to the tab's windows (sender origin, sender/receiver relation, payload) — invisible in the Network panel, essential to debug an iframe integration. Recorded by a listener in a DevTools isolated world: it only listens, and the page cannot see it
- Cross-site iframes included: each one runs in its own process, and the extension attaches to it within the same capture
- 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.
- Pause and resume — Stop works as a pause: Start resumes the capture in the same buffer, and every gap is recorded in the export with its reason. If Chrome itself ends the capture (e.g. when a password manager's menu appears in the page), the popup says why.
- 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, postMessage payloads and the decoded JWT are masked by key name (passwords fully, API keys / tokens / session ids partially), and a JWT found anywhere else in a string is partially masked too. 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, 5 000 network requests and 5 000 postMessages 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.
Ratings and reviews
Split of the 1 written reviews we hold1 written review we hold
Track Debug Logs Catcher on Radar
This page shows the listing as it is today. Add it to Radar and get one email when it changes.
- Users and rating
- Store text and screenshots
- Permissions it asks for

Debug Logs Catcher, in plain words
What it is, what to use instead, what it can access and how to fix it.
Debug Logs Catcher at a glance
Debug Logs Catcher is a Developer Tools extension by Julien Andre with 32 users. Chrome Web Store users rate it 5.00 out of 5 from 1 rating, which is still a small sample. By users it sits in the top half of Developer Tools extensions.
- By users
- #10,551of 31,410 in Developer Tools
- Rating
- 5.00category median 4.63
- Access
- Low18 of 100
Debug Logs Catcher alternatives
Closest by what they do · users as the store shows themIs Debug Logs Catcher safe?
Debug Logs Catcher asks for 4 permissions. 3 of them give wide access.
Permissions show what it could do, not what it does. See the full permission list.
debuggerTake full control of pages through the debuggertabsSee the address and title of every open tabwebNavigationFollow every page you open
Every permission Debug Logs Catcher asks for
4 permissions · 3 sensitive · Low access overallBrowser permissions · 4
- Take full control of pages through the debugger
debugger - See the address and title of every open tab
tabs - Follow every page you open
webNavigation - Save its own settings
storage
Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.
Debug Logs Catcher not working?
What recent reviews say
Store reviews from the last 90 daysNo new reviews were posted in the last 90 days, so there are no fresh complaint signals.
Common fixes
Try them in this order- 1Update Chrome and the extension
- 2Turn it off and on in chrome://extensions
- 3Reload the page
- 4Turn other extensions off in case two clash
Still stuck? Contact the maker or try an alternative.
Know when a listing changes
Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.