tracebug.dev · Developer Tools
5 items
Capture a browser bug — replay, console, network — into one local report your AI agent (Claude, Cursor) reads and fixes. Free. Capture → Know the cause → Create GitHub issue in 5 seconds. TraceBug is a free, zero-backend debugging assistant that turns "the page is broken" into a complete, developer-ready bug report — automatically. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHY TRACEBUG ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Every bug report opens with: 🔍 Possible Cause (high confidence): API POST /orders failed with 500 after clicking 'Place Order' 📋 TL;DR: TypeError on /checkout when clicking 'Place Order' button No logs to dig through. No guessing. Just clarity. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT IT CAPTURES — AUTOMATICALLY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Click + element context (tag, text, selector, aria-label, test-id) • Form inputs (passwords auto-redacted) • Navigation (route changes) • API calls (URL, method, status, response snippet on failure) • Console errors, unhandled promise rejections, stack traces • Full page screenshots with auto-naming • Environment — browser, OS, viewport, device, connection • Session timeline with millisecond-precision timestamps ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ HOW IT WORKS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1. Click the extension icon → toggle TraceBug ON 2. Use the website normally — TraceBug records silently 3. When a bug happens, press Ctrl+Shift+B (or Cmd+Shift+B on Mac) 4. Review the auto-filled report — root cause, steps, errors, network failures, screenshot 5. Click "Open in GitHub" → opens a new issue in your repo, pre-filled ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHO IT'S FOR ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Frontend developers fixing UI bugs without opening DevTools • Indie hackers shipping SaaS — debug faster, ship faster • Small teams reporting bugs without back-and-forth • QA engineers — zero typing, auto-filled reports with everything a dev needs • PMs and clients who can't read stack traces but want to report bugs properly ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT MAKES IT DIFFERENT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ vs Sentry / LogRocket / FullStory: ✓ 100% free, no subscription, no account ✓ Zero backend — works on ANY website instantly ✓ Privacy-first — your data never leaves your browser ✓ Deterministic root-cause engine — no AI APIs, no tracking ✓ 2-click bug capture vs. 10+ clicks in dashboards ✓ One-click GitHub issue vs. dashboards you never check ✓ Open source (MIT) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PRIVACY & SECURITY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • All session data lives in your browser's localStorage — nothing is uploaded anywhere • Sensitive fields (passwords, tokens, credit cards, SSNs) are auto-redacted before storage • Sensitive query params in URLs (api_key, token, secret, auth) are replaced with [REDACTED] • No analytics, no telemetry, no third-party scripts • Open source — audit the code at github.com/prashantsinghmangat/tracebug-ai ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EXPORT FORMATS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • GitHub Issue (one-click — opens pre-filled issue in your repo) • Jira Ticket (priority, labels, markup auto-generated) • PDF Report (print-optimized) • JSON / Plain Text (for custom pipelines) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ TECHNICAL DETAILS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Works on any website (http/https) • Zero impact on page performance — events are buffered in memory, flushed asynchronously • Fetch + XMLHttpRequest intercepted safely (never breaks your requests) • Failed network response bodies captured up to 10KB, binary responses skipped • Compatible browsers: Chrome, Edge, Brave, Opera ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LINKS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Live demo: https://tracebug.dev • GitHub: https://github.com/prashantsinghmangat/tracebug-ai • npm (for developers): https://www.npmjs.com/package/tracebug-sdk • Issues / feedback: https://github.com/prashantsinghmangat/tracebug-ai/issues Built by an indie developer who was tired of bad bug reports.
Jul 30, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.