BugSnap

Open the popup on the page that is misbehaving and click the capture button. It grabs the tab image, pulls the buffered console output and reads the browser, OS and screen resolution in one pass, then shows all of it as a report. From there, Copy as Markdown puts the text on the clipboard and the download button saves the image.

Only the visible area of the active tab, which is what chrome.tabs.captureVisibleTab returns. The image is taken as JPEG at quality 70 and scaled down to 1280 pixels wide if it is larger, which keeps stored captures small enough to survive extension storage limits. Scroll to the part that matters before you capture.

No. The console wrapper is installed at document start, so it collects entries whether or not the DevTools panel is open. It keeps the fifty most recent console.error, console.warn and console.log calls plus uncaught errors and unhandled rejections, each message truncated at 5000 characters. Anything logged before this build was installed is not there.

A heading, the environment list, and then only the error and warning entries, each in a code fence with its stack trace if one was attached. Plain console.log lines appear in the popup list but are left out of the Markdown so the ticket stays readable. Anything you typed in the note box is appended as a Notes section.

The manifest declares storage, activeTab, tabs, scripting, notifications and webNavigation, plus host access to all sites. Storage keeps the recent capture reports in chrome.storage.local. activeTab and tabs are how a capture identifies and photographs the tab you are looking at. Scripting injects the small script that reads the console buffer and screen size out of the page. Notifications covers system notifications, and webNavigation gives the extension page-load events for a tab. The all-sites host access is what lets the console-collecting content script match every http and https page, which is why the buffer is already filling before you decide to capture.