Cairn
NousResearch/hermes-agent

WhatsApp LID alias resolution and authorization fixes

Cluster 63415 · 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 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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #63416 fix(whatsapp): authorize first-contact LID senders via senderPn · done elsewhere → 8925c70, 7b7338c, #72592
  • #63540 fix(whatsapp): authorize first-contact LID senders via senderPn (#63415) · done elsewhere → 8925c70, #63415, #63416
Closed issues · 1
  • Closed#63415fix(whatsapp): authorize first-contact LID senders via senderPn
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/63415.json
cluster/63415.md