# NousResearch/hermes-agent · Desktop session mutations scoped to owning profile

## Open now

- Nothing open on GitHub.

These items address a bug where session archive and delete operations fail or produce NULL profile data when using non-default profiles on the desktop app. The fixes ensure session mutations are correctly scoped to the profile that owns the session.

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

- #96531: \[Bug\]: Desktop app archive fails with "Session not found" when using non-default profile

## Prior & competing PRs

- **#99376: fix(desktop): session archive/delete land in the owning profile; new rows stop getting profile_name=NULL (#96531 #98609 #99222, salvage #97199)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/api/sessions.test.ts`, `apps/desktop/src/api/sessions.ts`, `contributors/emails/[redacted:email]`, `hermes_state.py`, `run_agent.py`, `tests/test_session_db_profile_stamp.py`, `tests/test_tui_gateway_server.py`, `tui_gateway/methods_session.py`, `tui_gateway/server.py`
- **#97199: fix(desktop): scope every session mutation to its owning profile**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `5cc3da6827`, `7c2ec7c73b`, `#99376`, `#96531`, `#98609`, `#78836`

## Fix status

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