fix: deduplicate URL balloon messages in watch stream#64
Open
lesaai wants to merge 1 commit intosteipete:mainfrom
Open
fix: deduplicate URL balloon messages in watch stream#64lesaai wants to merge 1 commit intosteipete:mainfrom
lesaai wants to merge 1 commit intosteipete:mainfrom
Conversation
iMessage writes multiple rows to chat.db for the same URL when the rich link preview resolves. Both rows have balloon_bundle_id set to 'com.apple.messages.URLBalloonProvider' with identical text and sender but different ROWIDs and timestamps. This causes downstream consumers (like OpenClaw) to process the same URL message twice, burning tokens and producing duplicate responses. Fix: in messagesAfter(), track seen (sender, text) pairs for URL balloon messages and skip duplicates within the same batch.
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.
Problem
iMessage writes multiple rows to
chat.dbfor the same URL when the rich link preview resolves. Both rows haveballoon_bundle_idset tocom.apple.messages.URLBalloonProviderwith identical text and sender but different ROWIDs and timestamps (typically 30-65 seconds apart).This causes downstream consumers (like OpenClaw) to process the same URL message twice, burning tokens and producing duplicate responses.
Evidence from chat.db
Same sender, same text, same balloon type — two separate ROWIDs.
Fix
In
messagesAfter(), addm.balloon_bundle_idto the SELECT query and deduplicate URL balloon messages with the same(sender, text)within a batch. The first occurrence is kept; subsequent duplicates are skipped.Impact
messagesAfter()(used bywatchcommand)balloon_bundle_id = 'com.apple.messages.URLBalloonProvider'