NousResearch/hermes-agent

Agent reaction events not rendering live on desktop

Cluster 80678 · apps/desktop. Data as of

Nothing open on GitHub. Fix merged in #128557 on 1 Oct 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #128557. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where agent reaction events are not delivered to or rendered by the renderer process on desktop. The fixes involve routing message.reaction events by session ID and enabling live rendering of those reactions.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #128557 fix(desktop): scope message.reaction events to the active session transcript

    merged to main

    files: apps/desktop/src/app/session/hooks/use-message-stream/gateway-event/desktop-bridge.reaction.test.ts, apps/desktop/src/app/session/hooks/use-message-stream/gateway-event/desktop-bridge.ts, apps/desktop/src/components/assistant-ui/thread/use-message-reactions.ts, apps/desktop/src/store/gateway-switch.ts, apps/desktop/src/store/reactions-local.test.ts, apps/desktop/src/store/reactions-local.ts, apps/desktop/src/store/session-states.ts, tests/tools/test_desktop_ui.py, tools/desktop_ui.py

2 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1

  • #80702 fix(desktop): render agent reactions live · closed without comment
  • #80818 fix(desktop): route message.reaction events by session id, not window id · superseded by another PR → #128557
Closed issues · 1
  • Closed#80678fix(desktop): agent reactions persist but never paint live (message.reaction event not delivered to renderer)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
apps/desktop
Merged PRs
#128557
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.