3 items
Record a bug — session activity, console, network, and picked elements — then review and file it. Manual QA is fast at finding bugs and slow at handing them over. The console is cleared, the steps get retyped, and the developer reproduces from scratch. Bug Dossier records the session as it happens. Press record — or rely on the rolling two-minute buffer that is always running, so the failure you just watched is already captured — then flag the moment, stop, and file. The report arrives with the DOM at every frame, the network waterfall with response bodies, the console with stacks, storage, cookies and a video. The developer opens the recording and scrubs to the flag instead of asking what was on screen. A coding agent connected over MCP reads the same capture directly and can reach a root cause without asking anyone a question. Requires a Bug Dossier dashboard account, at bugdossier.com, which is where recordings are filed.
Sep 7, 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.