Cairn
NousResearch/hermes-agent

WhatsApp pairing HTTP 405 and stale Baileys version

Cluster 88516 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These members all concern WhatsApp pairing hitting HTTP 405 when the Baileys version lookup returns a stale build or the version host is rate-limited. They include a bug report and two pull requests proposing a fallback to the WhatsApp Web version and avoiding a pairing loop.

Open issues1

  • Issue#88516[Bug]: WhatsApp pairing fails with HTTP 405 when fetchLatestBaileysVersion() returns stale WA version

Open PRs2

  • PR#99256fix(whatsapp): fall back to the WhatsApp Web version when Baileys returns a stale build
  • PR#136853WhatsApp pairing no longer loops on 405 when the version host is rate-limited (#73700, salvage #99256)
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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/88516.json
cluster/88516.md