Cairn
NousResearch/hermes-agent

WhatsApp group message routing and filtering fixes

Cluster 72529 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These items address bugs where WhatsApp group messages were silently dropped or never reached the gateway, covering a missing LID sender mapping and incorrect allowlist configuration reading.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #72592 [AI] fix(whatsapp): group messages silently dropped when LID sender has no lid-mapping file · done elsewhere → 8925c70, c7a8953, #63416, #73465, #111067
  • #111067 fix(whatsapp): adapter reads WHATSAPP_GROUP_ALLOWED_USERS for the group allowlist (#72529) · done elsewhere → 8925c70, 35175df
Closed issues · 1
  • Closed#72529[Bug]: WhatsApp bot-mode group messages never reach gateway while DMs work
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/72529.json
cluster/72529.md