5 items
Review notes anchored to the exact component, with screenshots and logs, exported as a bundle for your AI coding agent. FrontBug turns a page review into something a developer can act on: every note is pinned to the exact component you clicked, and it carries the screenshot, the component's identity and the console and network activity from that moment. WHAT IT DOES • Note on any element. Right-click an element or press Alt+Shift+N, type the note, press Enter. A numbered pin stays on the component. • Note on a region. Drag a rectangle over a card, a header, a table. FrontBug works out which components the rectangle actually covers and ranks them. • Screenshots that survive tall pages. Full-page captures of a whole document, correct on sticky headers and high-resolution displays, with the numbered pins drawn onto the image. • The note knows the component: the selector that finds it again, its accessible name, its surrounding markup, and the component name and source file when the site is a development build. • Console and network activity around the note: errors, failed requests and the clicks that led to them, kept next to the note instead of in a separate screenshot of a devtools panel. • Signal, not noise. Missing analytics keys, blocked trackers and favicon 404s are labelled as noise and summarised, while a first-party error two seconds after your click is flagged. • Notes are attributed. Each note records who wrote it and when, so a team of reviewers can file in parallel and the developer knows who to ask. • Export a bundle. One zip with a report, the notes, the screenshots and the logs, written so a developer or an AI coding assistant can read it with no extra tooling. It can be written straight into a project folder instead of downloaded. • Combine reviewers. Import someone else's bundle into your session and re-export one report that lists every reviewer. • Pick up where you left off. Reopen the page and the pins find their components again. HOW TO USE IT 1. Open the site you want to review and click the FrontBug icon. 2. Start a session. FrontBug asks for access to that one site, and only that site. 3. Right-click an element and choose "Note on this element", or press Alt+Shift+N and click it. 4. Type the note, pick a type and severity, press Enter. 5. Open the side panel to browse, filter and search your notes, then choose Export. PRIVACY FrontBug has no account, no server and no analytics. It makes no network requests of its own. Everything, notes included along with screenshots and logs, is stored on your computer and leaves it only when you export a bundle yourself. FrontBug is inactive on every site until you start a session there, and it asks for access to that site at that moment. Pause or close the session and it stops. Passwords, tokens, cookies and authorisation headers are masked in captured logs by default. Screenshots are not masked, so whatever is on screen is in the image, and the export screen shows every screenshot and lets you delete any of them before exporting. PERMISSIONS • "Read and change your data on sites you allow": only on the sites where you start a session, granted one site at a time, revocable from Settings. • "Debug attached devices": used only while a full-page screenshot is being taken, then released. Chrome shows its usual banner during those few seconds. • "Know your email address": read once, to sign your notes. It is never sent anywhere, and you can turn it off or use a name you type yourself. SUPPORT Bugs and suggestions: support@frontbug.com · https://frontbug.com Version 0.1.0, first release. fol
Sep 16, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.