fix(client): filter Chrome extension IPC Object Not Found Sentry noise (KODY-CLOUDFLARE-3S)

[kentcdodds]

Summary

Sentry issue KODY-CLOUDFLARE-3S captures unhandled promise rejections on https://heykody.dev/ with:

Object Not Found Matching Id:N, MethodName:update, ParamCount:4

This is Chromium extension messaging noise (an antifingerprint extension breadcrumb appears on the event). There are no in-app stack frames — the rejected Chrome API promise bubbles to window.onunhandledrejection and Sentry's browser SDK reports it as app error.

Outcome: filtered — add a narrow client beforeSend predicate matching only that Chrome IPC signature (same pattern as AbortError / Firefox Xray / injected-global / Fathom filters).

Changes

• packages/worker/client/sentry-browser-filters.ts — filterChromeExtensionObjectNotFoundSentryEvent
• Wired into filterBrowserSentryEvent + sentry-init.ts comment
• Unit tests for positive/negative cases

Test plan

• Unit tests for the new filter signature
• npm run validate

System recap — composes existing primitives (low risk)

Mode: recap · Base: main @ 69f10ac9 · Head: cc2da1b9

Classification: composes — narrow browser Sentry beforeSend filter using the existing client noise-filter pattern; no primitive contracts changed.

Primitives touched

Primitive	Group	Impact
app-ui	surfaces	composes — drop Chrome extension IPC unhandledrejection noise in client Sentry

System map

Browser SDK beforeSend drops Chromium extension "Object Not Found Matching Id…" rejections before they open Sentry issues.

Legend: green = composes (wiring only) · amber = extended by this PR · red = new primitive · gray = context.

flowchart LR
  page["heykody.dev page"] --> ext["Browser extension IPC"]
  ext -->|"unhandledrejection"| sdk["@sentry/browser"]
  sdk --> filter["filterBrowserSentryEvent"]
  filter -->|"Chrome Object Not Found match"| drop["drop event"]
  filter -->|"other errors"| sentry["Sentry"]
  style filter fill:#216e4e,color:#fff
  style drop fill:#6b7280,color:#fff
  style ext fill:#6b7280,color:#fff

Loading

Risk notes

• Low risk: message-signature filter only; false-positive risk is low because the Chrome IPC wording is highly specific.
• Does not touch auth, isolation, billing, migrations, or DR.

Review focus

1. Is the regex narrow enough (Id + MethodName + ParamCount required)?
2. Should any sibling UnhandledRejection patterns share this filter later?

  

Summary by CodeRabbit

• Bug Fixes

  • Reduced Sentry noise by filtering Chrome extension “Object Not Found Matching Id” errors from browser error reports.
  • Preserved unrelated and incomplete error reports to maintain accurate monitoring and troubleshooting.

• Documentation

  • Updated error-filtering documentation to clarify which browser-generated and extension-related noise is excluded from monitoring.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 805e84da-d020-426f-827e-e52f553a5f04

📥 Commits

Reviewing files that changed from the base of the PR and between cc2da1b and fec5da9.

📒 Files selected for processing (1)

• packages/worker/client/sentry-browser-filters.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/worker/client/sentry-browser-filters.ts

---

📝 Walkthrough

Walkthrough

The browser Sentry filters detect Chrome extension IPC object-not-found errors, discard matching events, preserve incomplete patterns, and document the added noise filter. Tests cover direct matching and aggregate browser filtering.

Changes

Chrome extension Sentry filtering

Layer / File(s)	Summary
Chrome extension error detection and integration packages/worker/client/sentry-browser-filters.ts, packages/worker/client/sentry-init.ts	Adds detection for matching Chrome extension IPC errors and integrates it into the combined browser Sentry filter. Updates the filtering comment.
Filter behavior tests packages/worker/client/sentry-browser-filters.node.test.ts	Tests matching messages, argument-based matching, incomplete patterns, and aggregate browser filtering.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• kentcdodds/kody#1006: Adds a related browser Sentry noise filter and tests in the same module.
• kentcdodds/kody#1164: Adds an analogous browser Sentry filter and aggregate pipeline integration.
• kentcdodds/kody#1166: Adds dedicated browser Sentry filtering and tests in the same files.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: filtering Chrome extension IPC Sentry noise.
Description check	✅ Passed	The description explains the intent, changes, testing, and system impact, although it uses alternative headings for Intent and Testing.
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.

✨ 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-seer-kody-cloudflare-kody-cloudflare-3s-fc92

---

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-1246.kody-a99.workers.dev

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

Mocks:

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