Cairn

WhatsApp bot JID/device suffix matching fixes

NousResearch/hermes-agent · cluster 2934 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

Multiple bugs and proposed fixes around WhatsApp bot detection failing due to device suffix mismatches in JIDs, affecting reply-to-bot detection, group @mentions, and sender authorization.

Open issues1

  • Issue#29023[Bug]: WhatsApp reply-to-bot detection fails — device suffix mismatch in botIds vs quotedParticipant

Open PRs3

  • PR#29112fix(whatsapp): match reply bot ids without device suffix (#29023)
  • PR#47495fix(whatsapp): strip configured mention_patterns wake-word from group body
  • PR#75743fix(whatsapp): normalize device-suffixed WhatsApp JIDs

3 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · stale or abandoned 1

  • #29049 fix(whatsapp): match reply-to-bot when botIds carry device suffix · stale or abandoned
  • #46264 fix: match WhatsApp reply-to bot IDs without device suffix · closed without comment
  • #63416 fix(whatsapp): authorize first-contact LID senders via senderPn · done elsewhere → 8925c70, 7b7338c, #72592
Closed issues · 1
  • Closed#2934WhatsApp bot mode: structured @mentions never detected in groups (device suffix mismatch)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.23: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/2934.json
cluster/2934.md