# NousResearch/hermes-agent · Desktop bot/session routing broken in pooled profiles

## Open now

- Nothing open on GitHub.

These items concern a shared problem where desktop session or bot RPCs are misrouted — landing on wrong gateways or being overridden by the orchestrator — rather than reaching the correct local or named profile endpoint. A routing fix for Bot Mode RPCs is also included.

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

- #101422: \[Bug\]: Desktop default bot unreachable — orchestrator backend overrides session creation and prompt.submit

## Prior & competing PRs

- **#113956: Desktop: pooled-profile chats no longer land on the local primary and get refused SESSION_NOT_OWNED after reload (#101416 class)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/store/gateway-profile-request.test.ts`, `apps/desktop/src/store/gateway.ts`
- **#101554: fix(desktop): route local Bot Mode RPCs to the named profile gateway**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `0dcbc9e5ba8`, `6b96c2d5cad`, `#113956`, `#101422`

## Fix status

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