WhatsApp bridge version resolution and 405 fix

NousResearch/hermes-agent · cluster 73700 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 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 3 PRs.

These members address a bug where the WhatsApp bridge fails to pair due to a stale Web version being fetched, resulting in HTTP 405 errors. The work involves updating the bridge endpoint and implementing dynamic WhatsApp version resolution.

Open issues1

  • Issue#73700[Bug]: WhatsApp bridge fails to pair with HTTP 405 — stale WA Web version from fetchLatestBaileysVersion()

Open PRs3

  • PR#73729fix(gateway): update stale WhatsApp bridge endpoint (HTTP 405)
  • PR#73795fix(whatsapp-bridge): implement dynamic WhatsApp version resolution
  • 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.50: 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.