fix(client): filter Chrome extension receiving-end Sentry noise (KODY-CLOUDFLARE-4F)

[kentcdodds]

Intent

Stop Chrome/Firefox extension messaging noise from polluting production Sentry for Kody.

Summary

• Sentry KODY-CLOUDFLARE-4F (7662064169): Error: Could not establish connection. Receiving end does not exist.
• Production event on https://heykody.app/ (Chrome), zero stack frames, handled generic capture — classic extension runtime.sendMessage when the receiving end is gone.
• Kody never uses chrome.runtime / browser.runtime.
• Adds a narrow browser beforeSend filter (same pattern as KODY-CLOUDFLARE-3S Object Not Found) and unit coverage that nearby "connection" wording is kept.

Testing

• npx vitest run packages/worker/client/sentry-browser-filters.node.test.ts

System changes

System recap — composes existing primitives (low risk)

Mode: recap · Base: main @ e9b6b3cc · Head: 2fd463c0

Classification: composes — wires one more narrow predicate into the existing browser Sentry beforeSend filter chain; no primitive contract change.

Primitives touched

Primitive	Group	Impact
app-ui	surfaces	composes — drop Chromium/Firefox "Receiving end does not exist" noise

System map

Browser Sentry init already runs filterBrowserSentryEvent; this PR adds the receiving-end missing predicate to that chain.

Legend: green = composes (wiring only) · amber = extended by this PR · red = new primitive · gray = context (unchanged, included only when an edge crosses it).

flowchart LR
	appUi["app-ui<br/>Browser app (Remix 3)"]:::touched
	sentry["Sentry browser SDK"]:::untouched
	appUi -->|"beforeSend: drop receiving-end missing"| sentry
	classDef touched fill:#1a7f37,color:#fff
	classDef extended fill:#9a6700,color:#fff
	classDef added fill:#cf222e,color:#fff
	classDef untouched fill:#57606a,color:#fff

Loading

  

Summary by CodeRabbit

• Bug Fixes

  • Reduced noise from Chrome and Firefox extension messaging errors in error reporting.
  • Preserved reporting for similar but unrelated connection messages.

• Documentation

  • Expanded error-filtering documentation with additional browser noise categories and references.

[coderabbitai]

📝 Walkthrough

Walkthrough

The browser Sentry filters now remove matching Chrome and Firefox extension connection errors. Tests cover direct events, original errors, aggregate filtering, and similar MCP messages that remain reportable.

Changes

Extension Sentry filtering

Layer / File(s)	Summary
Extension error detection and pipeline integration packages/worker/client/sentry-browser-filters.ts, packages/worker/client/sentry-init.ts	The filter matches the receiving-end-missing error in strings, exceptions, and Sentry events. The aggregate browser filter applies it before later filters. The Sentry filtering documentation lists related browser noise categories and references.
Filtering behavior coverage packages/worker/client/sentry-browser-filters.node.test.ts	Tests cover direct event matching, original Error matching, aggregate filtering, and a similar MCP connection message that remains reportable.

Estimated code review effort: 3 (Moderate) | ~15–30 minutes

Possibly related PRs

• kentcdodds/kody#1246: Adds a related Chrome extension Sentry-noise filter in the same module and pipeline.
• kentcdodds/kody#1302: Adds filtering for connection-related browser or MCP errors.
• kentcdodds/kody#1164: Adds a related browser Sentry noise filter and integrates it into the aggregate filter.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely describes the main change: filtering Chrome extension receiving-end Sentry noise.
Description check	✅ Passed	The description includes the required Intent, Summary, and Testing sections, plus an optional System changes section with relevant implementation and risk details.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/sentry-triage-kody-cloudflare-7662064169-2643

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔎 Preview deployed: https://kody-pr-1344.kody-a99.workers.dev

Worker: kody-pr-1344
D1: kody-pr-1344-db
KV: kody-pr-1344-oauth-kv

Mocks:

• cloudflare: https://kody-pr-1344-mock-cloudflare.kody-a99.workers.dev/__mocks (kody-pr-1344-mock-cloudflare)