API & MCP

Snitcher – AI Bug Context Collector

One-click bug context for AI debugging: collects API calls, state, console, actions & DOM into an AI-ready Markdown report.

As of July 2026, Snitcher – AI Bug Context Collector has users in the Developer Tools category.

Usersno change0%
Ratingno change0%
— reviews
Reviewsno change0%
Version
0.1.1
Manifest V3

History

1 snapshots

Tracking since Jul 5, 2026.

Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
DateUsersRatingReviewsVersion
Jul 5, 20260.1.1
Now0.1.1

Permissions & access

Permissions
None declared
Host access
<all_urls>

Screenshots

Snitcher – AI Bug Context Collector screenshot 1Snitcher – AI Bug Context Collector screenshot 2

About

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

Technical

Version
0.1.1
Manifest
V3
Size
22.93KiB
Min Chrome
88
Languages
1
Featured
No

Metadata

ID
nckkpikgbgegmgmfdeacldempdceoimn
Developer ID
uc700837468ca6d9529719b6dd03515e9
Developer Email
[email protected]
Created
Jul 4, 2026
Last Updated (Store)
Jul 4, 2026
Last Scraped
Jul 5, 2026
Website
Support URL
Privacy Policy

Data sourced from the Chrome Web Store · last verified Jul 5, 2026.