# NousResearch/hermes-agent · WhatsApp bridge lifecycle logs missing timestamps

## Open now

- Nothing open on GitHub.

These issues and fixes address WhatsApp bridge lifecycle console lines (startup, connected, logged-out, reconnect) appearing in bridge.log without timestamps. The work involves adding timestamp formatting to the relevant console.log/warn calls in bridge.js.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #126259. Verify it addresses your case.
- **Recommended:** read PR #126259 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-126259`. 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.67`: 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

- #97021: \[Bug\]: WhatsApp bridge lifecycle console lines (startup/connected/logged-out/reconnect) reach bridge.log with no timestamps

## Prior & competing PRs

- **#126259: fix(whatsapp): every bridge.log console line carries a timestamp (#97021, salvages #97105)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `scripts/whatsapp-bridge/bridge.js`, `scripts/whatsapp-bridge/bridge_helpers.js`, `scripts/whatsapp-bridge/bridge_helpers.timestamp.test.mjs`
- **#97105: fix(whatsapp): timestamp bridge.js's lifecycle console.log/warn lines**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `1e2498a23d`, `#126259`

## Fix status

- Merged to main in PR #126259 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-28`.