# NousResearch/hermes-agent · Fix desktop approval routing by event owner

## Open now

- Nothing open on GitHub.

These changes address how approval responses are routed in the desktop client, directing them through the exact owner of the originating runtime event rather than a less specific target.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #100930. Verify it addresses your case.
- **Recommended:** read PR #100930 (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-100930`. 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.50`: 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

- #97511: fix(desktop): route approval responses through exact runtime event owner

## Prior & competing PRs

- **#100930: fix(desktop): approvals on single-connection installs route through the event's exact owner (#96394, salvage #97519)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/store/session-states-runtime-map.test.ts`, `apps/desktop/src/store/session-states.ts`
- **#97519: fix(desktop): route approval responses through the runtime event's exact owner**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `55d8c054eb`, `#100930`
- **#97552: fix(desktop): route approvals by event owner scope**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#97519`

## Fix status

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