catchsignal.dev · Developer Tools
5 items
Record and share detailed bug reports: console logs, network traffic, storage state, environment data, and screencasts. Bug reports that developers actually love. Signal captures everything - network traffic, console logs, storage state, environment data, and a synchronized screencast - and wraps it into a crisp, shareable report in seconds. No more back-and-forth. No more "can you reproduce it?" No more digging through logs. Just one click to record, one click to share, and a report that tells the full story. ───────────────────────────────────── 🚀 WHY TEAMS CHOOSE SIGNAL ───────────────────────────────────── Whether you're a QA engineer hunting regressions, a support agent triaging customer issues, or a developer fixing that impossible-to-repro bug - Signal gives you the full picture so problems get fixed faster. ✅ Reports your whole team will actually read ✅ AI-ready context so LLMs debug for you, not with you ✅ Privacy-first: credentials and PII are redacted automatically ✅ Works on any site - no code changes, no SDK, no backend required ───────────────────────────────────── ⚡ CORE FEATURES ───────────────────────────────────── 🎯 High-Fidelity Recording Capture full network traffic (HAR), every console event - errors, warnings, tables, uncaught exceptions - plus storage state and environment metadata, all synced to an interactive timeline. 🔄 Intelligent Session Replay More than a screen recording. Replay captured user events in a clean environment with injected storage and pre-flight auth requests, so anyone on the team can reproduce the exact bug state. 🤖 LLM Context Export Turn any report into a precise, token-efficient AI prompt with one click. Send straight to ChatGPT, Claude, Gemini, or Llama. A live arc indicator shows token usage against each model's limit so you never blow the context window. Choose exactly what to include: environment, console errors, failed requests (with redacted payloads), storage snapshot, and user-reported issues. 🔒 Automatic Data Redaction Sensitive data is stripped at capture time - before anything hits storage or export. Built-in rules cover auth headers, cookies, JWT tokens, credit cards, email addresses, and common secret JSON keys across all six capture surfaces. Add custom rules (header, query param, JSON key, or regex) for your project's specific fields. 🛠️ Developer Request Composer Re-send any captured network request with one click. Edit headers and bodies inline to test API fixes on the spot - no switching to Postman, no copy-pasting curl commands. 📸 Screenshot & Annotation Editor Snap, highlight, and draw. Point exactly where it hurts with built-in annotation tools before you share. 🔗 One-Click Webhook Delivery Push reports directly to Jira, Slack, or any custom endpoint via configurable webhooks - formatted exactly how your team expects them. 💻 VS Code Integration Map domains to local project folders. When your tab matches a saved mapping, an "Open in VS Code" button appears instantly in the popup - zero friction from browser to editor. 📦 Flexible Export Formats Export as JSON, ZIP, or GZIP - configured once in Settings. Download any screencast as a WebM video directly in the browser, no server required. 🕘 Local Session History Every recorded session is saved automatically and browsable from the popup - pin the important ones, rename, replay, or export as JSON, all stored locally with no MCP server required. ───────────────────────────────────── ✨ WHAT'S NEW IN v1.8 ───────────────────────────────────── Per-Site Access Signal no longer runs automatically on every website you visit. Grant it access one time per site with a simple prompt, right when you try to record, screenshot, or capture - giving you tighter control over where the extension is active. Encrypted Jira & Azure DevOps Credentials Your Jira API token and Azure DevOps personal access token are now encrypted with a password you choose, instead of being stored in plain text. You unlock them once per browser session to create tickets. Security Audit Log A local, structured log now records security-relevant events - recording start/stop, debugger attach/detach, report saves - viewable and exportable right from a new Security Log tab in Settings. Widget: Close for Session The floating recording widget now has a close button. Hide it for the rest of your browser session with one click; it reappears automatically next time you open the browser. Rolling Buffer: always-on, zero-effort capture A silent background buffer records the last 2 minutes of debug context on configured domains. When a JS error fires - or you press Alt+Shift+B - it commits instantly into a full report. No need to remember to start recording. Backend Log Correlation Connect an observability integration (Azure Log Analytics, Sentry, Grafana/Loki) via the new Workspace Builder. Network requests show a badge with matched log entries revealed inline, correlated via distributed trace IDs. Azure Log Analytics includes a no-credentials demo account to try immediately. ───────────────────────────────────── 🔐 PRIVACY ───────────────────────────────────── Signal records only what you explicitly start recording, and only on sites you've explicitly granted it access to. There is no background telemetry and no data is sent anywhere without your action. The built-in redaction engine strips credentials and PII before reports leave your machine, integration credentials are encrypted at rest with a password only you know, and a local security audit log gives you full visibility into recording and debugger activity. Full privacy policy: https://catchsignal.dev/privacy ───────────────────────────────────── Ready to fix bugs faster? Install Signal and send your first report in under a minute. → https://catchsignal.dev/
Jul 13, 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.