NousResearch/hermes-agent

Desktop hover triggering excessive backend pre-warming

Cluster 100548. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #117068 on 20 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #117068, then check it covers your case.

Read #117068 Pick up a Lab task

These items concern a bug where hovering over the profile rail in the desktop app caused backends to be pre-warmed for every profile without pointer movement, leading to high memory churn and exceeding backend caps. The cluster covers the problem report, a fix, and a related salvage change.

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.

#117068 Desktop: hovering the profile rail without moving the pointer no longer pre-warms a backend for every profile (#100548, salvage #100588)

merged to main

files: apps/desktop/src/app/chat/sidebar/profile-dropdown-switcher.tsx, apps/desktop/src/app/chat/sidebar/profile-rail-connect.test.tsx, apps/desktop/src/app/chat/sidebar/profile-rail-fleet.test.tsx, apps/desktop/src/app/chat/sidebar/profile-switcher.tsx, apps/desktop/src/app/chat/sidebar/session-row.test.tsx, apps/desktop/src/app/chat/sidebar/session-row.tsx, apps/desktop/src/app/chat/sidebar/use-profile-prewarm.test.ts, apps/desktop/src/app/chat/sidebar/use-profile-prewarm.ts

1 PR closed without merging

From the close comments: merged via another change 1

#100588 fix(desktop): stop fleet-wide hover-prewarm without pointer movement · merged via another change → 1ec61e4, #117068, #100548

Closed issues · 1

Closed#100548Desktop hover-prewarm cascades through the entire profile fleet with no user input — ~750 MB/min RAM churn, 19 backends vs cap of 3

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.67: 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

Merged PRs: #117068
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/100548.json
cluster/100548.md