# NousResearch/hermes-agent · Relay deadline chain and bot reply timeout fixes

## Open now

- Nothing open on GitHub.

These members address bugs in the relay's deadline propagation, where reply waiters could outlive their host context and bot_mode turn wait seconds were not respected. The work involves identifying and patching the broken deadline chain behavior.

## TL;DR

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

## Closed / duplicate issues

- #113107: The relay's deadline chain does not hold: the reply waiter outlives its host, and the client deadline ignores bot_mode.turn_wait_seconds

## Prior & competing PRs

- **#113246: fix(relay): preserve delivery deadline chain**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#113107`
- **#113527: fix(relay): honor configured bot reply deadlines**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`
- **#113528: fix(relay): honor configured bot reply deadlines**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#113246`, `#113107`

## Fix status

- No merged fix on record.