# NousResearch/hermes-agent · Profile sessions stored in wrong state.db location

## Open now

- Nothing open on GitHub.

A bug caused multiplexed gateway sessions to be written to the root/default state.db instead of the owning profile's database. These items address identifying and fixing the session DB path resolution to respect the active profile scope.

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

- #88532: Bug: a profile's sessions are physically stored in the default/root state.db (profile_name correct) — desktop shows them under the default/hermes bot

## Prior & competing PRs

- **#88734: fix(gateway): multiplex sessions now stored in the owning profile's state.db, not root (#88532, salvage #88632)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run.py`, `gateway/session.py`, `tests/gateway/test_multiplex_session_db_profile_scope.py`
- **#88632: fix(gateway): resolve the session DB inside the active profile scope**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#88734`, `#88532`

## Fix status

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