Bug Context Capture

Miniback’s biggest advantage is that every bug report arrives with the technical context you need to reproduce it — no back-and-forth with the user required. The widget automatically captures what happened in the browser and attaches it to the feedback.

⚡ What gets captured

• Console logs — log, warn, error, info messages (all plans)
• Network requests — method, URL, status, duration, headers/bodies (all plans, opt-in per project)
• Interaction breadcrumbs — the user’s clicks, inputs, form submits, navigation, and JS errors (all plans)
• Screenshots with annotations — optional, user-drawn (Builder and Studio)
• Environment — page URL, browser, OS, device, and screen size (all plans)

Console Logs

The widget intercepts the browser’s console and records recent messages, so you see exactly what the app logged leading up to the report.

Captured:

• Log levels: log, warn, error, info
• Message content and a timestamp for each entry

Where to view: open a feedback item → Console Logs section.

Console logs are captured on all plans, including Hobby.

Network Requests

Network capture records the HTTP requests the page made (via fetch and XMLHttpRequest), so you can see failing API calls, slow endpoints, and error responses behind a bug.

Captured per request:

• Method, URL, status code, and duration
• Request and response headers and bodies (with sensitive values redacted — see Redaction Rules below)

Where to view: open a feedback item → Network Logs section.

Enabling network capture

Network capture is opt-in per project because it records request and response bodies:

1. Go to your project page
2. Open Widget Customization → Capture
3. Toggle Enable network logging on

A privacy warning is shown when it’s enabled, reminding you that headers and bodies are recorded (and auto-redacted).

Redaction Rules

When network capture is on, Miniback automatically redacts sensitive data before it’s stored or transmitted. Every new project starts with sensible defaults, and you can add your own rules.

Default redacted headers:

authorization, cookie, set-cookie, x-api-key,
api-key, x-auth-token, x-csrf-token

Default redacted body keys:

password, token, secret, apiKey, api_key,
accessToken, refreshToken, sessionId, apiSecret

Adding custom rules:

1. Go to your project page → Widget Customization → Capture
2. Under Redaction Rules, add:
   • Redacted Headers — header names to strip (case-insensitive), e.g. x-custom-token
   • Redacted Body Keys — JSON keys to strip from request/response bodies
3. Rules save automatically. Default rules are labelled default; your custom rules can be removed at any time.

Redacted values are replaced with [REDACTED] in the stored logs.

Interaction Breadcrumbs

Breadcrumbs are a timeline of what the user did right before submitting — the single most useful thing for reproducing a bug.

Captured events (last 50):

• Clicks on buttons, links, and other interactive elements
• Inputs — with values masked for privacy
• Form submissions
• Navigation — URL changes, including SPA route changes
• JavaScript errors — uncaught errors and unhandled promise rejections

Privacy: breadcrumbs are privacy-first by design. Password, credit-card, CVV, SSN, and similarly named fields are fully masked; other input values are truncated; and sensitive URL query parameters (token, key, secret, access_token, etc.) are replaced with [REDACTED].

Where to view: open a feedback item → Breadcrumbs section.

Breadcrumbs are captured on all plans.

Screenshots & Annotations

On Builder and Studio, users can attach a screenshot of the page and mark it up to point out exactly what’s wrong.

How it works:

1. When submitting feedback, the user chooses to add a screenshot
2. The widget captures the current page
3. The user annotates it with the built-in tools:
   • Arrow — point to a specific element
   • Rectangle — highlight an area
   • Freehand draw — circle or scribble anything
   • Undo and clear are available while annotating
4. The annotated image is uploaded and attached to the report

Where to view: open a feedback item → Screenshot section.

Plan access:

Screenshots are optional — users can always submit a report without one.

Environment Context

Every report — on all plans — also includes the environment it came from:

• Page URL
• Browser name and version
• Operating system
• Device type (mobile / tablet / desktop)
• Screen and viewport size

This context powers the environment breakdowns in the Analytics Dashboard.

Viewing Captured Context

All captured context appears in the feedback detail view. Open any feedback item (from All Feedback or a project’s Feedback tab) to see its Screenshot, Console Logs, Network Logs, Breadcrumbs, and environment details in one place.

AI Handoff

Because every report already carries structured technical context, Miniback can hand it straight to an AI coding assistant.

Copy as AI prompt (all plans)

One click turns a bug report — plus its captured console logs, network requests, and breadcrumbs — into a paste-ready prompt for Cursor, Claude, or any AI coding tool. Open a feedback item and use Copy as AI prompt, then paste it into your assistant to start debugging with full context.

AI “Explain this” (Builder & Studio)

An on-demand Explain this button summarizes what likely went wrong in plain English, so non-technical teammates can understand a report without reading raw logs. Available on the Builder and Studio plans.

What’s Next?

• Categories - Organize feedback by type (Builder+)
• Feedback Workflow - Manage and resolve reports
• Customization - Configure the widget
• Analytics Dashboard - Understand your metrics

Need help? See Troubleshooting or contact support.