DebugTrail: Browser Debugger & Error Recorder

Browser debugger & error recorder. See what happened, even when DevTools wasn't open.

See what happened, even when DevTools wasn't open. DebugTrail keeps a rolling record of the last 30 minutes of browser activity, on your machine. You never press record. When something breaks, you open DebugTrail, follow the trail back, and save the few minutes that matter. DebugTrail debugs after the fact. It does not set breakpoints or step through code. DevTools does that, and does it well. DebugTrail solves the other half of the problem: the bug that already happened, while the console was closed, that nobody can reproduce on demand. WHAT IT RECORDS • Console warnings and errors, with safely serialized arguments (log, info and debug are optional) • Uncaught JavaScript errors and unhandled promise rejections, with stack traces and source locations • console.assert failures and console.trace • Network requests: method, URL, status code, duration, resource type, initiator, cache hit, and Chrome's network error string • Failed requests, 4xx and 5xx responses, and network-level failures • Slow requests, using a threshold you choose • Missing scripts, stylesheets, images and fonts • Page navigation, reloads, and single-page-app route changes • Which button or link you clicked, never what you typed HOW YOU INVESTIGATE • Recent, what just happened, newest first. No filter to configure before you can see anything. • Timeline, one searchable record of console, network, page and user events • Event details, timestamp, page, tab, frame, status, duration, message, stack • Related events. What else was recorded in the same tab moments either side SUSPICIOUS ACTIVITY, WITHOUT GUESSWORK DebugTrail marks 5xx responses, 401/403 rejections, request failures, unusually slow requests, uncaught exceptions, unhandled rejections, endpoints that failed repeatedly, bursts of errors, and navigations that followed an error. These are fixed rules, not AI. Each means the same thing every time, and DebugTrail never claims to have found the cause, only what happened nearby. FOR QA AND BUG REPORTS Something broke? Save the last 30 seconds, minute or five minutes as an incident. Saved incidents keep their evidence even after the rolling buffer moves on, and export as a report with the environment, timeline, console errors, network failures and related events, ready to paste into Jira, Azure DevOps or GitHub. Export as an HTML report, JSON, HAR, a Markdown bug report, or CSV. HAR files open in Chrome DevTools and any standard network viewer. Reports can be narrowed to API requests only, so a page's scripts, styles and images do not bury the request flow you are reading it for. Anything that failed or was slow is always included, and the report says what it left out. PRIVACY • Everything stays on your device. No account, no backend, no analytics, no telemetry. • DebugTrail makes no network requests of its own. The release build fails if any network call appears in the shipped bundle. • Never records request or response bodies, headers or cookies. • Never records anything you type. Only clicks and form submissions are observed, and login and payment forms are skipped entirely. • No screenshots and no video, so a report cannot leak whatever else was on screen, and no screen-capture permission is requested. • Values that look like tokens, keys or passwords are replaced with [redacted] before anything is written to disk. • Site access is optional and requested only when you grant it. A fresh install records nothing. • The rolling buffer is capped by default: the last 30 minutes, and at most 5,000 events. Change the duration or clear it any time. • Privacy Mode pauses everything with one toggle. PERMISSIONS, PLAINLY • Site access, required to observe activity on the sites you choose. Optional, requested at runtime, revocable at any time. • webRequest, to record request status, timing and failures. Observe-only; DebugTrail cannot modify, redirect or block any request. • scripting, to install the console recorder on the origins you granted. • storage, to save your preferences locally. • sidePanel, for the main interface. • activeTab, lets you allow one site at a time from the toolbar icon. DebugTrail does not request access to your history, cookies, bookmarks or downloads, and does not use the debugger API. WHAT IT MAY MISS DebugTrail records what Chrome exposes to an extension, which is a lot but not everything. It is a safety net, not a guarantee. It cannot see anything that happened before you granted access to a site, pages that replace the console before DebugTrail loads, request or response bodies and headers, payload byte sizes, or browser internal pages, the Chrome Web Store and local files. Where information is not available, it says so rather than guessing. KEY FEATURES: 1. A rolling record of the last 30 minutes, you never press record 2. "What just happened?" answers the question you actually arrive with 3. Save the last 30 seconds to 5 minutes as an incident you can export 4. Deterministic suspicious-activity markers; no AI, no guessing at cause 5. Clicks and SPA route changes, so you see what led up to the failure 6. One searchable timeline of console, network, page and user events 7. Export to HTML, JSON, HAR, Markdown or CSV, filterable to API requests only 8. No screenshots, no video, no upload, no account 9. Secrets redacted before anything is written; login forms never described 10. Light, dark and system themes; keyboard accessible