# NousResearch/hermes-agent · Live session registry scoped incorrectly by profile

## Open now

- Nothing open on GitHub.

These items address a bug where the live session registry is keyed by bare session ID rather than profile, allowing a turn to run on the wrong profile. Fixes scope the registry by profile and restrict session resumption to matching profiles.

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

- #100029: Live session registry is keyed by bare session id, so a turn can run on the wrong profile (launch-profile fallback)

## Prior & competing PRs

- **#101212: fix(tui_gateway): session.resume reuses live sessions only within the requesting profile**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/test_tui_gateway_server.py`, `tests/tui_gateway/test_resume_live_profile_scope.py`, `tests/tui_gateway/test_session_resume_db_ownership.py`, `tui_gateway/methods_session.py`, `tui_gateway/server.py`
- **#100117: fix(gateway): scope live session registry by profile and fail closed on unknown profile**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#100029`, `#101212`

## Fix status

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