Skip to content
Install

TWO BUILDS 9 browsers

Chrome from the Chrome Web Store Firefox from addons.mozilla.org Edge from Microsoft Edge Add-ons Brave takes the Chrome build Opera takes the Chrome build 4 more Chromium browsers: Arc, Vivaldi, Chromium, Opera GX the Chrome build

diagnostic · one of 50 free, no counter

Bug report

How do I turn what just broke into a ticket somebody can fix?

A ticket that says the button does nothing gets answered with a request for the console output, a day later. This records the page's errors and console warnings while you reproduce the problem, then writes them up beside the failed requests, the viewport and the browser - as Markdown to paste anywhere, or as a GitHub issue's title, labels and body. The text is built in the panel and goes nowhere until you paste it.

Reach it Press ⌘ + K on any tab and type bug report. Ctrl + K on Windows and Linux

Record, reproduce, stop, and the reproduction written up as Markdown
records thrown errors, rejections, console warnings and errors
adds failed requests, viewport, browser, Recorder steps
addresses cut at the path - no query strings
messages passed through the sanitizer first
sends nothing - built locally, sent when you paste
before Record not recoverable
Add   LoupeKit - opens the list of browsers it can be installed in

TWO BUILDS 9 browsers

Chrome from the Chrome Web Store Firefox from addons.mozilla.org Edge from Microsoft Edge Add-ons Brave takes the Chrome build Opera takes the Chrome build 4 more Chromium browsers: Arc, Vivaldi, Chromium, Opera GX the Chrome build

in the panel · free, no counter

section#about

What this actually is

When a tester, a designer or a client hits a bug and the developer is not in the room, when filing an issue against somebody else's site, or when a reproduction needs to travel with its evidence. If the Recorder holds steps from the same session they go in as steps to reproduce; anything the page threw before Record is not recoverable.

section#asked

Asked about this diagnostic

Does the report get uploaded anywhere?

No. The Markdown is assembled in the panel from what the two recordings and the browser's request record already hold, and it sits there until you copy it. No server and no shared link are involved, signed in or not; the only copy that leaves the machine is the one you paste into a ticket.

Can a screenshot go in the report?

Not inside it, because Markdown can only show an image that already has an address and this product uploads nothing. Capture with pins opens the Capture editor, where the screenshot can be marked with numbered pins and saved or copied, to attach beside the report in the tracker.

Why are some failed requests missing?

Failed requests come from the browser's resource-timing record, which carries a status only where the browser reports one - a cross-origin response that does not opt in hands back no status, and a request that never got an answer has none either. Those are left out rather than guessed at.

how to use bug report

  1. Open Bug report and press Record before you reproduce anything.
  2. Reproduce the problem, then press Stop.
  3. Write one line under What happened and press Build report.
  4. Copy it as Markdown, or as a GitHub issue's title, labels and body, and paste it into the ticket.
Add   LoupeKit - opens the list of browsers it can be installed in

TWO BUILDS 9 browsers

Chrome from the Chrome Web Store Firefox from addons.mozilla.org Edge from Microsoft Edge Add-ons Brave takes the Chrome build Opera takes the Chrome build 4 more Chromium browsers: Arc, Vivaldi, Chromium, Opera GX the Chrome build

101 of these · no host permissions · three free audits