Install and first report

Video guide (3.5 minutes)

Install

Open BugScribe on the Chrome Web Store and press Add to Chrome.
Click the puzzle-piece icon in the toolbar and pin BugScribe.

It works in Chrome and other Chromium browsers that use the Chrome Web Store.

Make a report

Go to the page with the problem and click the BugScribe icon.
Press Analyze page. The page reloads once and a loader shows progress. The icon badge reads ON while recording.
Reproduce the bug: click around, submit the form, trigger the error. The popup updates live while it is open.
Press Report this bug. A report tab opens with a draft title, steps, actual result, environment and a screenshot.
Edit the title and expected result, switch sections on or off, and check the preview. It shows exactly what is exported.
Copy Markdown and paste it into GitHub, Jira or Slack, or download the full log as PDF or Word.
Press Stop capturing in the popup when you are done.

"BugScribe started debugging this browser"
While BugScribe analyzes a tab, Chrome shows this bar. It is Chrome's standard notice for access to the same data DevTools uses, and it is how BugScribe sees browser-generated warnings and failed requests. It only appears on the tab you analyzed, and it goes away when you press Stop capturing. Pressing Cancel on the bar also stops it; BugScribe then keeps recording with reduced detail.

Limits

Chrome's own pages (chrome://) and the Chrome Web Store cannot be analyzed.
After you navigate to a different site, open BugScribe again; Chrome only lets it act on the tab you last clicked it on.
BugScribe keeps the newest 200 console messages and 200 failed requests for a tab. Identical repeats are merged and counted.

Settings

Right-click the icon and choose Options, or use the popup's Settings button, to block specific sites, switch email masking off, or Clear all data.

Help

Something not working? Email wasifraza909@gmail.com.