Bugzio
For the tester
Walk through the client site, the staging build and the new page in one pass. No waiting for someone to install the widget first.
Chrome and Edge extension
Report a bug on any page
The widget works where someone has put it into the site’s code. The extension drops the same widget into any open tab — a client site that has no widget yet, or a staging build nobody has touched.
Version 1.0.0 · 45 KB
Chrome, Edge, Brave, Opera
6 languages
Who it is for
For your team, not for the client
Clients report through the widget installed on the site. The extension is the internal tool — for the tester, the project manager and the developer who has to get through several sites in a day.
For the manager and the agency
Spot a bug on a client site and capture it right there, with full context, instead of a screenshot in a chat. Every report lands in the right project.
For the developer
Check the fix on staging and send back a report with the console and the network requests, not the words “doesn’t work for me”.
What it captures
The same context as the embedded widget
The extension does not build a second reporting form. It loads the same widget, so everything the widget captures on a site is captured here too.
Annotated screenshot
Mark the spot, draw an arrow, blur anything sensitive — right on the page, before sending.
Console logs
JavaScript errors and warnings that happened on the page up to the moment of the report.
Network requests
Failed requests with their status codes and timings — status 400 and above, or a connection error.
Step timeline
The clicks and URL changes before the bug — the path back to it.
Environment
Browser, operating system, viewport size and the exact page URL.
AI triage
In the panel AI triage summarises the report: a title, reproduction steps, a priority and a category.
One place for every report
Reports from the extension land in the same project, the same list and the same integrations as reports from the widget. The team does not have to know where they came from.
Installing
Three steps, about five minutes
Nothing to build, nothing to compile. Download the archive, load it into the browser and paste the project token.
Download and unzip
The archive holds the extension itself and a README with the same instructions.
bugzio-extension.zip
Load it into the browser
Open the extensions page, turn on developer mode and choose “Load unpacked” → the unzipped folder.
chrome://extensions
edge://extensions
Paste the project token
The token is in the panel, in the project settings. Add one per site you report on.
Project → Settings → Widget
Not in the Chrome Web Store yet
For now the extension installs unpacked, which is why developer mode is needed. Publishing to the store is planned; when it happens installing becomes a single click, and the archive stays available for anyone distributing it themselves.
Widget or extension
Both report into the same place
They do not replace each other. The widget is for the client and the site’s users; the extension is for your team.
Widget on the site
One line of script in the site’s code. The button is visible to everyone who opens the page.
Extension in the browser
Installed in your browser. The button appears only when you call it up.
Permissions and privacy
No standing access to any site
The extension asks for three permissions and uses none of them in the background. It sees no page until you press the icon.
The active tab only
The browser grants access to the page for the moment you press the extension icon, and takes it back afterwards. The “read your data on all websites” permission is never requested.
Settings stay in your browser
Project tokens and preferences live in your browser profile and sync with your Chrome account. They are never sent to our server.
Data leaves only with a report
The extension does not track the pages you open and sends nothing in the background. Only the report you send yourself reaches Bugzio.
Frequently asked
Questions about the extension
Does it work on a site where the widget is not installed?
Yes — that is the whole point. The extension loads the widget into your tab and changes nothing in the site’s code. The report goes to whichever project you pick before pressing the button.
Do the site’s visitors see the button?
No. The widget exists in your tab only and disappears the moment you reload the page. To every visitor the page looks exactly as it always does.
What permissions does it need?
Three: the active tab, settings storage and script injection. The browser grants access to the page only at the moment you press the icon — the extension has no standing access to any site.
Which browsers does it work in?
Chrome, Edge, Brave, Opera and other Chromium-based browsers. The same package works everywhere; on Edge the extensions page is edge://extensions. Firefox is not supported yet.
The report never arrived — where do I look?
Check two things. First, that the settings hold the right project token. Second, if the project has an allowed-domains list, add the domain you are testing — an empty list means “any domain”.
Report from any page, starting today
Download the extension, paste the project token, and the next bug goes to the right list with all of its context.
14-day trial · no card