# NousResearch/hermes-agent · cached agent reuse disabling inactivity timeout fix

## Open now

- Nothing open on GitHub.

A bug where cached agent reuse silently disables the inactivity timeout, causing an infinite 'Still working' loop after user interrupt. A fix preserves the inactivity clock across interrupt-recursive cached-agent turns.

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

- #15654: Cached agent reuse silently disables the inactivity timeout, producing a Still working iteration 0/60 (cached) loop after user interrupt

## Prior & competing PRs

- **#16116: fix(gateway): preserve inactivity clock on interrupt-recursive cached-agent turns (#15654)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run.py`, `tests/gateway/test_agent_cache.py`
- **#15807: fix(gateway): preserve inactivity clock on interrupt-recursive cached-agent turns (#15654)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#1`

## Fix status

- Merged to main in PR #16116 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-26`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.