QA bug reports your engineers
don't have to interrogate.

What a QA capture actually contains.

• ↻ Deterministic DOM replay. Not a video. Your engineer can pause the replay, inspect the DOM at any moment, see what was actually on screen — including dynamically-rendered React state.
• ⌘ Console log buffer. Last 500 console entries through the recording, synced to the timeline. The TypeError that fired at 41.3s is right there — no "can you check the console?"
• ↯ Network log. Every fetch/XHR with method, URL, status, duration, body sizes. The failing 500 is impossible to miss.
• ♪ Optional 90-second audio. Your tester narrating what they expected vs what happened. The signal is "I clicked Save and the toast said 4001 but my changes didn't persist after refresh" — saved you three Slack rounds.
• ✎ Drawings on the page. Highlight the element, circle the wrong layout, arrow from "this said" to "this should have said."

Audience gate, baked into the SDK config.

The trigger button only mounts when the user is verified. Issue tokens to your QA team via your existing auth; nobody else sees the button. Public visitors aren't confused, support tickets don't ask "what's this BugJar thing", and end-users on production are unaffected.

Toggle Show trigger only to verified users in the dashboard project settings, mint a JWT on your QA-team auth, and pass it into init:

window.addEventListener('bugjar:ready', () => {
  BugJar.init({
    userToken: '<JWT signed server-side with your project secret>',
  });
});
// showWhen: 'verified' comes from your dashboard project settings.
// Flip it in the UI; next page load, public visitors stop seeing
// the trigger. No snippet re-paste needed.

Same primitive your customer-facing app uses for HMAC user identity, just constrained to a private audience. Token expires in 1 hour; refresh on page load.

From "I found a bug" to "engineer is on it" in five minutes.