# NousResearch/hermes-agent · Orphaned lease misread as sibling, locking sessions

## Open now

- Nothing open on GitHub.

A backend incorrectly treats its own orphaned leases as belonging to a sibling owner, causing sessions to be permanently locked. The members address identifying and reclaiming these orphaned leases rather than blocking on them.

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

- #101415: \[Bug\]: a backend's own orphaned lease reads as a sibling owner, permanently locking its own sessions ("already has a live owner")

## Prior & competing PRs

- **#101663: fix(sessions): reclaim a backend's own orphaned leases instead of reading them as a sibling owner (salvage #101437)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/active_sessions.py`, `tests/hermes_cli/test_active_sessions.py`, `tests/tui_gateway/test_cross_process_orphan_ownership.py`, `tui_gateway/server.py`
- **#101437: fix(desktop): stop orphaned leases from permanently locking chats**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#101663`

## Fix status

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