# NousResearch/hermes-agent · Bot Chat profile switching bug and fixes

## Open now

- Nothing open on GitHub.

A bug was identified where the Desktop Bot Chat interface incorrectly switches to the default profile instead of maintaining the correct one when refreshing history. Two fixes address resolving the session owner and preserving the active profile during history refresh.

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

- #107199: \[Bug\]: Desktop Bot Chat switches from the correct profile to default when refreshing history

## Prior & competing PRs

- **#112809: fix(desktop): resolve Bot Chat session owner before falling back across profiles**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/app/contrib/hooks/use-background-sync.test.ts`, `apps/desktop/src/app/contrib/hooks/use-background-sync.ts`, `apps/desktop/src/app/contrib/wiring.tsx`
- **#107219: fix(desktop): keep active Bot Chat profile when refreshing history**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#112809`

## Fix status

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