# NousResearch/hermes-agent · Peer DM timeout misclassified as unreachable peer

## Open now

- Nothing open on GitHub.

These issues and fixes address a bug where a timed-out peer direct message is incorrectly reported as the peer being unreachable, rather than as a slow or still-running response. This misclassification can cause the sender to resend a message that was already delivered.

## 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 #116885. Verify it addresses your case.
- **Recommended:** read PR #116885 (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-116885`. 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

- #113099: A timed-out peer DM is reported as an unreachable peer, so the sender resends an already-delivered message

## Prior & competing PRs

- **#116885: fix(peer): a timed-out peer DM says the turn was accepted and is still running, not that the peer is unreachable (#113099, salvage #113102)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/subcommands/peer.py`, `tests/hermes_cli/test_peer_dm_reporting.py`, `website/docs/user-guide/bot-mode.md`
- **#113102: fix(peer): a timed-out peer DM is a slow answer, not an unreachable peer**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#116885`, `#113099`

## Fix status

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