ARIA: filter promo senders from active-threads surface#345
Open
holoduke wants to merge 1 commit into
Open
Conversation
The active-threads block in think/reflect prompts was concatenating 11+ unrelated promo/notification senders (AutoScout24, AliExpress, Glassdoor, MijnOverheid, Ferrari newsletter, LinkedIn job alerts, etc.) under one subject line. They share the gmail:<account> thread key so they all aggregate into a single "thread" that drowns out real conversations and wastes prompt budget. Add isPromoSender() in brain-prompt.ts using common no-reply / newsletter / jobalerts / savedsearches local-part patterns plus a small denylist of marketing domains. Filter participants when rendering the Active threads section; suppress a thread entirely if every participant matches. Raw observations are untouched — only the prompt-side aggregation is filtered. Intent-summary: Active-threads prompt surface was bundling many promotional/notification email senders into one fake thread, polluting reasoning context with inbox noise. Intent-tokens: active-threads, promo-filter, email-noise, prompt-noise, gmail, newsletter, noreply
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
In
think/reflectprompts the Active threads block has been showing one giant fake thread with 11+ unrelated senders — AutoScout24, AliExpress, Glassdoor, MijnOverheid, Ferrari newsletter, FD, Apprentus, Trimble, LinkedIn Job Alerts, Google, etc. — concatenated under a single subject line. They aggregate that way because all Gmail observations share thegmail:<account>thread key inworking-memory.ts, so every promotional sender lands in the sameConversationThread.participantsarray.The result: a noise "thread" that drowns out real conversations, wastes prompt budget, and makes the active-thread list harder to scan for what actually matters.
What
Add a sender-pattern filter in
backend/brain-prompt.tsand apply it where the Active threads block is rendered:PROMO_LOCAL_PATTERNS: common notification local-parts —no-reply@,do-not-reply@,newsletter@,notifications@,savedsearches@,jobalerts(-noreply)@,best-message-notice@.PROMO_DOMAIN_KEYWORDS: small denylist of marketing/notification domains —aliexpress,autoscout24,glassdoor,ferrari,mijn.overheid,marktplaats,quora.participantsper thread; if every participant matches, suppress that thread entirely.Conservative — only obvious promo/notification patterns. Real human/work email senders still show up.
Scope
wm.conversationThreadsdata structure are untouched.Verification
npx tsc --noEmitclean.🤖 Self-improvement worker