# NousResearch/hermes-agent · WhatsApp LID alias resolution and authorization fixes

## Open now

- Nothing open on GitHub.

These items address handling of LID (Linked ID) sender aliases in WhatsApp, covering allowlist resolution for DMs and groups and authorization of first-contact LID senders via senderPn on modern session layouts.

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

- #63415: fix(whatsapp): authorize first-contact LID senders via senderPn

## Prior & competing PRs

- **#63416: fix(whatsapp): authorize first-contact LID senders via senderPn**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8925c70a1c`, `7b7338cd6d`, `#72592`
- **#63540: fix(whatsapp): authorize first-contact LID senders via senderPn (#63415)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `8925c70a1c`, `#63415`, `#63416`

## Fix status

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