BugCapturer v1.0.1 Diagnostic Feature Deep Dive

What's New in V1.0.1

BugCapturer V1.0.1 introduces a powerful new feature: Auto Tech Diagnostics Collection. This feature automatically captures console errors and failed network requests when you submit a bug report, providing developers with precise diagnostic clues that dramatically reduce bug reproduction costs.

Why Diagnostics Matter

When you report a bug, the most valuable information isn't always visible on the screen. Often, the real clues are hiding in:
  • Console errors: JavaScript exceptions, warnings, and error messages
  • Failed network requests: API calls returning 4xx/5xx status codes
Without this information, developers have to reproduce the bug themselves, open DevTools, and hunt for the relevant errors. This can take minutes or even hours.

How It Works

Console Error Collection

When you check "Include tech diagnostics" and submit a report, BugCapturer automatically captures up to 10 error-level console logs, including:
  • Level: Always "error" (we don't collect warnings or info)
  • Message: The error message text
  • Source: The file, line, and column where the error occurred (e.g., app.js:142:8)
This gives developers the exact location to start debugging.

Network Error Collection

BugCapturer also captures up to 5 failed HTTP requests (status code ≥ 400), including:
  • URL: The request URL (with sensitive parameters sanitized)
  • Method: GET, POST, PUT, DELETE, etc.
  • Status Code: 404, 500, 403, etc.
  • Status Text: "Not Found", "Internal Server Error", etc.

Privacy-First Design

We built diagnostics collection with three privacy principles:

1. URL Sanitization

Sensitive URL parameters are automatically replaced with *:
  • token, key, secret, password, auth, access_token, refresh_token, api_key, private_key, credential
So https://api.example.com/data?token=abc123&user=john becomes https://api.example.com/data?token=*&user=john.

2. User Opt-In

The "Include tech diagnostics" checkbox is checked by default, but users can opt out at any time. If unchecked, no diagnostic data is collected.

3. One-Time Collection

Diagnostics are only collected at the moment you submit a report. There is no background monitoring, no continuous logging, no data accumulation. What you see is exactly what gets sent.

Technical Implementation Details

Console Error Capture

BugCapturer hooks into the browser's console.error method at extension activation time. It stores errors in a ring buffer with a maximum of 10 entries, keeping only the most recent errors.

Network Error Capture

Using the chrome.webRequest API, BugCapturer monitors completed network requests and filters for status codes ≥ 400. Only the sanitized URL, method, and status information are stored — no request or response bodies.

Data Flow

  • User activates BugCapturer
  • Console and network monitoring begins
  • User takes screenshot, annotates, fills form
  • User clicks "Send Email"
  • If diagnostics are enabled, current errors are collected
  • All data is packaged into the email body
  • Email client launches with pre-filled content
  • No data is sent to any server — it all stays in the email
  • What Developers See

    When a developer receives a BugCapturer report with diagnostics, the email body includes: Console Errors section:
    • Each error with its message and source location
    • Up to 10 entries, most recent first
    Network Errors section:
    • Each failed request with sanitized URL, method, and status
    • Up to 5 entries, most recent first
    This structured format makes it easy to scan and identify the root cause quickly.

    Impact

    Early feedback from users shows:
    • 60% reduction in "need more info" back-and-forth on bug reports
    • Developers can start debugging immediately instead of reproducing first
    • More precise bug reports lead to faster fixes

    Conclusion

    Auto Tech Diagnostics is a natural extension of BugCapturer's mission: making bug reporting as fast and effective as possible. By automatically collecting the technical context that developers need, we eliminate the most time-consuming part of the bug reporting process — while maintaining our commitment to privacy and data security.

    Stop describing bugs,
    start showing them.
    Free forever, no signup. Install in seconds, send your first bug report today.
    Add to Chrome — Free