2 items
One-click bug context for AI debugging: collects API calls, state, console, actions & DOM into an AI-ready Markdown report. Snitcher collects the runtime context an AI coding assistant (like Claude Code, Cursor, or Copilot) needs to debug logical and business bugs — and copies it to your clipboard as a clean, AI-ready Markdown report. Screenshots and "it doesn't work" tickets don't tell an AI what actually happened. Snitcher does. Write one sentence describing what went wrong, click Copy, and paste the full context into Jira, Linear, a GitHub issue, or straight into your AI tool. WHAT IT CAPTURES • Recent API calls — method, URL, request/response bodies, status codes, and timing (last 20). • Application state — whatever your app chooses to expose via a simple window.__SNITCHER__ hook (works with Redux, Zustand, Vuex, or any custom store). • Console — the last 100 errors and warnings. • User actions — a human-readable timeline of your clicks and form changes (last 50). • Page map — SPA route/navigation history (pushState, popstate, hashchange). • Interaction context — a sanitized DOM subtree around the element you last interacted with, plus a CSS selector. • DOM snapshot — full sanitized outerHTML (scripts, styles, and hidden nodes removed), truncated to stay paste-able. • A grep-friendly "Data Map" — an endpoint overview with failures first, and failed calls correlated with the console output that landed right after them. HOW IT WORKS Snitcher starts filling circular buffers at document_start, so it captures context continuously — before you even click Copy. Noisy third-party telemetry (analytics, session replay, error trackers) is dropped at capture time so the signal that matters isn't crowded out. PRIVACY FIRST • No backend. No network requests of its own. No analytics. No tracking. • Everything is processed locally — the only output is your clipboard. • Best-effort redaction of credentials (passwords, tokens, API keys, cookies, secrets). Business data and PII are kept because they're often the root cause of the bug — and they never leave your device. Want stricter redaction? It's opt-in. • Because reports can contain your visible data, always review one before pasting it somewhere public. Open source (MIT): https://github.com/Marb-AI/snitcher
Jul 4, 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.