# NousResearch/hermes-agent · Isolated turns incorrectly blocking session lease access

## Open now

- Nothing open on GitHub.

These issues and fixes concern a bug where isolated turns in the TUI gateway were fencing out session leases — either their own or the parent's — causing 'Session already has a live owner' errors on new session creation.

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

- #101416: bug(desktop): 'Session already has a live owner' on every new session creation

## Prior & competing PRs

- **#113974: fix(tui_gateway): isolated turns no longer fence themselves out of their own session lease (#101416, salvage #103737)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/[redacted:email]`, `tests/tui_gateway/test_compute_host_borrowed_lease.py`, `tui_gateway/compute_host.py`, `tui_gateway/compute_host_bridge.py`, `tui_gateway/session_lifecycle.py`
- **#103737: fix(tui_gateway): stop isolated turns fencing out the parent's session lease**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `b3973490654`, `ecefbfa6e1c`, `baeebe4a60f`, `#113974`, `#101501`

## Fix status

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