# NousResearch/hermes-agent · Gateway resume_pending_expired session reset behavior and notifications

## Open now

- 1 issue, 2 PRs open on GitHub.
- #61052: gateway: resume_pending_expired resets despite session_reset.mode=none and shows misleading 'inactive for 24h' notice
- PR #58935: fix(gateway): notify user and write correct end_reason for resume_pending_expired resets
- PR #61154: fix(gateway): honor session_reset.mode none in resume_pending freshness gate

Members concern the gateway's resume_pending_expired handling: whether it respects session_reset.mode=none, whether the user is notified, and whether the reset notice text and end_reason are accurate. The group includes both issue reports and proposed fixes, which appear closely related though they emphasize different aspects.

## TL;DR

- 5 member(s): 1 open issue(s), 1 closed issue(s), 2 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.34`: 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.

## Open related issues

- #61052: gateway: resume_pending_expired resets despite session_reset.mode=none and shows misleading 'inactive for 24h' notice

## Closed / duplicate issues

- #58933: \[Bug\]: resume_pending_expired silently creates new session without notifying user or properly closing the old one

## Prior & competing PRs

- **#58935: fix(gateway): notify user and write correct end_reason for resume_pending_expired resets**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/run.py`, `gateway/session.py`, `tests/gateway/test_session_reset_notify.py`
- **#61092: fix(gateway): respect session_reset.mode and fix misleading reset notice**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#61071`
- **#61154: fix(gateway): honor session_reset.mode none in resume_pending freshness gate**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/run.py`, `gateway/session.py`, `tests/gateway/test_session_reset_notify.py`

## Fix status

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