# NousResearch/hermes-agent · WhatsApp bridge stability, config, and port issues

## Open now

- Nothing open on GitHub.

These items concern crashes, crash-loop behavior, credential loss, and silent config failures in the WhatsApp Baileys bridge, alongside a recurring theme of the bridge hardcoding port 3000 and ignoring configurable port settings from config.yaml.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 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_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.45`: 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

- #33365: WhatsApp gateway crashes (exit 1) on first poll after using existing bridge
- #52702: \[Bug\]: WhatsApp Baileys bridge crash-loop persists in v0.17.0 — kills Telegram as collateral

## Prior & competing PRs

- **#37327: fix(whatsapp): retry external-bridge probe and skip port-kill on timeout (#33365)**. closed without merge
  - maintainer direction: category `volume_quota`; implication `active`

## Fix status

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