# NousResearch/hermes-agent · Prune incorrectly cancels connection redial fix

## Open now

- Nothing open on GitHub.

A bug where pruning during a connection redial would silently cancel the re-activation and re-home the window to the primary. Fixes are described targeting this specific interaction between prune and redial behavior.

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

- #113877: A prune during a connection redial cancels the re-activation through the epoch, silently re-homing the window to the primary

## Prior & competing PRs

- **#114985: fix(desktop): a live-work prune no longer cancels the redial of the connection being viewed (#113877, salvage #113878)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/store/gateway-connection-lifecycle.test.ts`, `apps/desktop/src/store/gateway.ts`
- **#113878: fix(desktop): a prune no longer cancels the redial of the route it is pruning**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `11a12f201e7e`, `#114985`, `#113877`, `#113878`

## Fix status

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