Pin a bug to any element on any page.
A Chrome extension for QA testers and developers who'd rather click a button than write a paragraph. Element selector, screenshot, console errors, and page context — captured automatically.
Three steps. No tab-switching.
Hit the shortcut
Pin BugPin from any page with the keyboard. The panel slides in on the right — your bugs for this URL live there.
Click the broken thing
Hover any element to highlight it. Click to lock. BugPin captures a stable selector, fingerprint, and screenshot of exactly what's on screen.
Annotate, then ship
Add a title, severity, tags. Draw arrows on the screenshot. Ctrl+Enter sends it to your local list, a shared session, or straight into Mantis as a real ticket.
Built for the moment something breaks.
Most bug reports are useless because the person reporting was in a hurry. BugPin captures the context the developer actually needs — without making the reporter type it.
Pin markers that find their target. Even after the next deploy.
A CSS selector alone breaks the moment the design changes. BugPin captures a fingerprint — text content, attributes, parent context, sibling position — and uses it to score candidate elements when the selector is no longer unique. The pin lands on the same thing, every time.
- Uses ID, data-testid, aria-label when stable
- Falls back to nth-of-type chain anchored at unique ancestors
- Multi-candidate scoring when the selector is ambiguous
.cards
Draw on the screenshot without leaving the page.
A built-in canvas annotator with arrow, rectangle, and blur tools. Privacy-first: blur sensitive data before it gets attached to the bug. The screenshot uploads to your backend and travels with the ticket — no third-party image host.
- Arrow + rectangle + blur for redacting
- Auto-attaches to Mantis tickets via REST API
- JPEG-compressed (~150 KB) for fast uploads
Console transcripts and a network HAR — without DevTools.
For developer-role bugs, BugPin attaches every console.* call and a HAR-1.2 file of every fetch/XHR. Open the HAR in Chrome DevTools or any HAR viewer. Bridges the gap to LogRocket without the heavyweight session replay.
- All log levels — info, warn, error, debug
- Method, URL, status, timing for every request
- No request bodies or headers — privacy-first
Files real tickets in your real tracker.
BugPin doesn't try to replace Jira or Linear. It's a capture tool — bugs land in your existing workflow with screenshot, selector, severity, and full context already filled in. Zero copy-paste from the reporter.
- Screenshot attached to the ticket automatically
- Severity, assignee, expected/actual mapped to your fields
- Or skip integrations and use shared sessions for a real-time team view
QA, devs, and the designer who keeps spotting things.
Less typing, better tickets
Switch to QA mode in the popup. The form asks for repro steps, BugPin captures everything else. Tag bugs, search them, file them straight to Mantis.
- Steps to reproduce as a first-class field
- Auto-captured browser, OS, viewport
- Severity workflow with statuses
The errors are already attached
Switch to Dev mode and BugPin auto-attaches console errors and failed network requests to every bug. On Pro, the full console transcript and a HAR file too.
- Console errors + 4xx/5xx responses
- Framework + viewport hints
- Downloadable HAR for DevTools replay
Pin the thing that's a few px off
You don't need to write a Jira ticket for "this card overflows on tablet". Pin it, screenshot, draw an arrow, hand it to the dev. Done in 15 seconds.
- Visual annotation built in
- Shareable session for whole team
- Markdown export for design reviews
Honest about what it is.
Most "all-in-one" tools become nothing-in-one. BugPin has a narrow job and tries to do it well.
What BugPin is
- + A capture tool for the moment something breaks
- + A way to file a real ticket with real context, fast
- + A Chrome extension. That's it. No web app to log into.
- + Local-first — your bugs stay on your machine until you say otherwise
What BugPin isn't
- − A replacement for Jira, Linear, or Mantis. Use both.
- − A general-purpose feedback tool. We're for bugs.
- − Going to "transform your workflow." It saves you a few minutes per ticket.
- − AI-powered, blockchain-secured, vector-database-driven. It's a Chrome extension that works.
Free to start. Pro when you need it.
No credit card for the free plan. No "contact sales" anywhere. Cancel Pro any time.
- 25 bugs total
- Local-only mode
- Screenshot capture + annotation
- QA / Dev role-aware capture
- Markdown / JSON export
- Shared sessions
- Mantis integration
- Unlimited bugs
- Shared sessions, real-time
- Mantis ticket creation + screenshot attach
- Full console transcript on Dev bugs
- Network HAR capture + download
- Email support
- Everything in Pro
- Up to 10 session members
- Team session management
- Linear + GitHub Issues (when shipped)
- Early access to new features
- Priority support
Already a customer? Find your license key →
The honest answers.
chrome.storage.local — nothing leaves your machine. Shared mode syncs bug records (no images) via Firestore. Mantis mode also creates the actual ticket in your own Mantis instance via your API token.console.* and fetch/XHR with thin wrappers — overhead is on the order of microseconds per call. Pro capture is off by default; turn it on only on tabs where you're hunting bugs.Stop typing bug reports.
Pin them.
Add BugPin to Chrome. File your first bug in 30 seconds.
Add to Chrome — it's free