Cairn

WhatsApp bridge stability, config, and port issues

NousResearch/hermes-agent · cluster 5965 · gateway

Data as of

9 open items. Fix attempted, not merged.

The short answer

5open issues
4open PRs
15items grouped
Known?
Yes. 15 related items grouped here, 4 issues 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
5 issues and 4 PRs.

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.

Open issues5

  • Issue#5965WhatsApp bridge_port from config.yaml silently ignored — yaml_cfg not in scope in _apply_env_overrides()
  • Issue#16521[Bug]: bridge_port config not loaded into config.extra — WhatsApp bridge always uses default port 3000
  • Issue#24122WhatsApp bridge hardcodes port 3000, conflicts with local dev servers
  • Issue#26997[Bug]: WhatsApp bridge dies immediately with code -9 under systemd
  • Issue#58936WhatsApp bridge (Baileys) crashes silently, loses creds.json, requires full re-pairing

Open PRs4

  • PR#6024fix(gateway): bridge_port, bridge_script, session_path from config.yaml
  • PR#24320fix(whatsapp): move bridge default port off 3000
  • PR#29742fix: move WhatsApp bridge default port off 3000
  • PR#43795feat(gateway): configurable bridge port for WhatsApp

2 PRs closed without merging

From the close comments: PR volume cleanup 1 · closed without comment 1

  • #37327 fix(whatsapp): retry external-bridge probe and skip port-kill on timeout (#33365) · PR volume cleanup
  • #58959 fix(whatsapp): crash resilience for Baileys bridge — uncaught exception logging, creds.json backup/restore, crash-loop detection (#58936) · closed without comment
Closed issues · 4
  • Closed#23322[Feature]: Support setting WhatsApp `bridge_port` configuration
  • Closed#33365WhatsApp gateway crashes (exit 1) on first poll after using existing bridge
  • Closed#43554[Feature]: Configurable port for gateway WhatsApp
  • Closed#52702[Bug]: WhatsApp Baileys bridge crash-loop persists in v0.17.0 — kills Telegram as collateral
How this cluster was grouped
  • Link evidence (partly structural links): 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.09: 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
4
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/5965.json
cluster/5965.md