Breadbugger is a bug tracking tool built for the pre-launch phase of a WordPress site — the moment when designers, QA, developers and clients walk through the site looking for issues before go-live.

Three complementary surfaces:

On-page floating widget — open the widget with a configurable keyboard shortcut, “pin” reports directly to the HTML element they refer to, attach screenshots captured on-the-fly from the browser.
Clean admin list — manage every report from a compact full-screen view: filter by status, priority, author; sort manually with drag & drop; reply with inline notes.
REST API for external clients — app-password gated endpoints to integrate your bug tracker with CLIs, AI coding assistants, or custom scripts.

Key features

Stable pin selectors — element selector built via a cascade: data-breadbugger-name (opt-in dev), then stable id, then semantic class, then positional CSS. Pins survive refactors.
Configurable hotkey — press the keys to set your preferred combo, with browser/OS collision validation.
Reporter / manager role model — assign who can open reports (reporter) and who can manage them all (manager) via custom capabilities on any WordPress role.
Author filter + configurable visibility — managers can see and filter by author; reporters can optionally see only their own bugs.
In-browser screenshots — automatic capture via getDisplayMedia (HTML2Canvas-Pro as a fallback for modern CSS like oklch / color-mix).
Internationalized — Italian source, .po / .mo translations, .pot template ready for any language.
Built-in feedback channel — settings form to send bug reports / feature requests / questions to the author via wp_mail.
Branded email notifications — HTML emails for @mentions in notes and (optional) for new bugs and resolved bugs, with per-recipient frequency: all events, accorpate (timeout-based), daily digest, weekly digest, or none.

Use case

Client site pre-go-live: 5-10 people testing in parallel. Each one loads the site, opens the widget with a shortcut, pins the issue directly on the affected element. The PM / dev watches the admin list, sorts by priority, assigns fixes, marks resolved.

Standalone. No external SaaS required. No data sent to third-party servers. Your bugs stay in your database.