ARIA: filter newsletter senders from active-threads prompt section#349
Open
holoduke wants to merge 1 commit into
Open
ARIA: filter newsletter senders from active-threads prompt section#349holoduke wants to merge 1 commit into
holoduke wants to merge 1 commit into
Conversation
Drift audit 2026-05-20 flagged that the "Active threads" section of the working-memory prompt was being polluted by promotional/automated streams (currently the AutoScout24 "Nieuwe matches voor je Zoekopdracht" newsletter was the *only* active thread shown). Real signal-to-noise on that section had dropped to 0%. Defense in depth: - working-memory.ts: introduce isNewsletterParticipant() and reject new threads whose sender/chat matches noreply / no-reply / notifications. / newsletter / savedsearches / mailings. / updates@ / bounce, or known one-way notification domains (autoscout24, schoolkassa, rdw, anwb notifications). Also sweep any pre-existing newsletter threads on every update tick — fixes the currently-stuck AutoScout24 entry. - brain-prompt.ts: filter active threads at render time using the same helper, so even if a newsletter slips past the write-time guard via another path, the prompt stays clean. Intent-summary: Newsletter and automation senders were being promoted to "active conversation threads" in the working-memory prompt, crowding out real conversations Gillis is in. Intent-tokens: newsletter, noise, active-threads, prompt-pollution, working-memory, automation-sender, filter Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Active threads:both at write time (so they never get promoted to thread status in the first place) and at render time (defense in depth, also sweeps any senders that slipped in during prior ticks).Changes
backend/memory/working-memory.tsisNewsletterParticipant()helper, exported for reuse.updateConversationThreads()skips creating a new thread when sender/chatName/chatJid matches the newsletter pattern.backend/brain-prompt.tsformatWorkingMemory()filters active threads throughisNewsletterParticipant()before rendering.Patterns matched
Substrings:
noreply,no-reply,notifications.,newsletter,savedsearches,mailings.,updates@,bounce.One-way domains:
autoscout24,schoolkassa,rdw,anwb.nl/notifications.Test plan
npx tsc --noEmitpassesActive threads:in the brain prompt🤖 Generated with Claude Code