# NousResearch/hermes-agent · WhatsApp group message routing and filtering fixes

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #72529: \[Bug\]: WhatsApp bot-mode group messages never reach gateway while DMs work

## Prior & competing PRs

- **#72592: \[AI\] fix(whatsapp): group messages silently dropped when LID sender has no lid-mapping file**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8925c70a1c`, `c7a8953d79`, `#63416`, `#73465`, `#111067`
- **#111067: fix(whatsapp): adapter reads WHATSAPP_GROUP_ALLOWED_USERS for the group allowlist (#72529)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8925c70a1c`, `35175df0be`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`