# NousResearch/hermes-agent · Fix agent.reconnect_attention_after read timing in gateway

## Open now

- Nothing open on GitHub.

These members address a bug where agent.reconnect_attention_after was evaluated at import time rather than call time, causing per-profile and live configuration values to be ignored during gateway reconnect escalation. The fixes ensure the value is read from the bound profile's config at the moment it is needed.

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

- #115635: \[Bug\]: agent.reconnect_attention_after is frozen at import — per-profile and live config values are ignored (gateway reconnect escalation)

## Prior & competing PRs

- **#116749: fix(gateway): reconnect_attention_after read from the bound profile's config at call time**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run.py`, `gateway/run_adapters.py`, `scripts/ci/profile_scope_patterns.json`, `tests/gateway/test_adapter_connect_classification.py`, `tests/gateway/test_reconnect_attention_profile_scope.py`
- **#115636: fix(gateway): resolve agent.reconnect_attention_after at call time, not import time**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `40bfcbda34`, `#116749`

## Fix status

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