ReproLens

Every other bug-reporting tool asks you to send screenshots of your product to someone else's server. This one doesn't. ReproLens captures issues two ways — click an element to mark it, or run a rule-based scan of the whole page — and exports straight into whatever your team already uses. Nothing is ever sent anywhere unless you explicitly export it, connect your own GitHub account for one-click issue push, or turn on the opt-in device-sync setting (an issue-title summary across your own Chrome devices, via Chrome's own first-party sync — never a screenshot, log, or attachment, and off by default). There's no AI, no analytics, no account required. Why that matters in practice: you can use this on an internal tool behind a VPN, on a client's unreleased product, or on a healthcare/finance app with real user data on screen — none of which you could safely point a cloud-based bug tool at. What it finds, all via hand-written, explainable rules (never a black-box model): contrast issues, overlapping elements, inconsistent spacing, broken images and links, missing alt text and form labels, layout overflow, layout shift (Core Web Vitals CLS), dead/rage clicks, slow network requests, and more. Every finding tells you exactly why it fired — and you can add your own custom detector scripts for rules specific to your own product. What you can do with a captured issue: annotate the screenshot (box, arrow, or pixelate to redact anything sensitive), record a short local screen capture, preview it as someone with a color-vision deficiency would see the page, edit every field before it ships, and export it straight to whatever your team already runs — Jira and GitHub, and half a dozen other trackers and file formats besides — with a one-click direct push for GitHub, or a no-account CLI script if you'd rather not connect an account at all. Free. Local-first by design. No subscription, no required server, no required account.