# NousResearch/hermes-agent · WhatsApp bridge version resolution and 405 fix

## Open now

- 1 issue, 3 PRs open on GitHub.
- #73700: \[Bug\]: WhatsApp bridge fails to pair with HTTP 405 — stale WA Web version from fetchLatestBaileysVersion()
- PR #73729: fix(gateway): update stale WhatsApp bridge endpoint (HTTP 405)
- PR #73795: fix(whatsapp-bridge): implement dynamic WhatsApp version resolution
- PR #136853: WhatsApp pairing no longer loops on 405 when the version host is rate-limited (#73700, salvage #99256)

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.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 3 open PR(s), 0 merged PR(s), 0 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.50`: 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.

## Open related issues

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

## Prior & competing PRs

- **#73729: fix(gateway): update stale WhatsApp bridge endpoint (HTTP 405)**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `de5798b45a76`
  - files: `.bytecode-fingerprint`, `agent/tool_executor.py`, `hermes_cli/mcp_catalog.py`, `optional-mcps/agentkey/manifest.yaml`, `plugins/model-providers/hetzner/__init__.py`, `plugins/model-providers/hetzner/plugin.yaml`, `scripts/whatsapp-bridge/bridge.js`, `skills/email/himalaya/SKILL.md`, `skills/email/himalaya/references/configuration.md`
- **#73795: fix(whatsapp-bridge): implement dynamic WhatsApp version resolution**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#2728`
  - files: `scripts/whatsapp-bridge/bridge.js`, `scripts/whatsapp-bridge/bridge.native.test.mjs`, `scripts/whatsapp-bridge/bridge_helpers.js`
- **#136853: WhatsApp pairing no longer loops on 405 when the version host is rate-limited (#73700, salvage #99256)**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `51f8cf55122e375311d9f4c0bc43ff819682b6d6`
  - files: `scripts/whatsapp-bridge/bridge.js`, `scripts/whatsapp-bridge/bridge.reconnect.test.mjs`, `scripts/whatsapp-bridge/bridge_helpers.js`, `website/docs/user-guide/messaging/whatsapp.md`

## Fix status

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