fix(whatsapp): propagate quotedMessageId to reply_to_id - #52856
Closed
dhruvkej9 wants to merge 1 commit into
Closed
Conversation
The Baileys bridge already reports quotedMessageId for replies, but the WhatsApp plugin adapter ignored it and never set MessageEvent.reply_to_id. This caused inbound replies to look like top-level messages in the agent context and broke reply-threading in groups/DMs. Refs: observed in local gateway logs where reply_to_id was always None for WhatsApp replies.
alt-glitch
added
type/bug
Collaborator
|
Contributor
Author
|
Closing in favor of #52875 which includes this fix plus the full quoted context (text/media paths) for human-like replies. |
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
2 participants
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.
The Baileys bridge already reports
quotedMessageIdfor reply messages, but the WhatsApp plugin adapter ignored it and never setMessageEvent.reply_to_id. This caused inbound WhatsApp replies to look like top-level messages in the agent context and broke reply-threading in both DMs and groups.Changes:
data['quotedMessageId']toreply_to_idwhen building aMessageEventfrom the bridge payload.Tested locally: WhatsApp replies now carry the original message id and the agent sees the reply context correctly.