NousResearch/hermes-agent

Desktop serve idle CPU burn from polling loop

Cluster 108005. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #117063 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 #117063. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #117063. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #117063 Pick up a Lab task

A per-session notification poller in desktop serve calls psutil.Process.status() roughly twice per second per session, causing CPU usage that scales with the square of open sessions. The cluster covers identifying this idle CPU burn and throttling the bot-delivery poll interval to reduce it.

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.

#117063 Desktop `serve` stops burning a core while idle: the bot-delivery poll runs every 5 s, not 2×/s per session (#108005, salvage #108014)

merged to main

files: hermes_cli/active_sessions.py, tests/hermes_cli/test_active_sessions.py, tests/hermes_cli/test_shared_session_attach.py, tests/tui_gateway/test_bot_delivery_poll_throttle.py, tests/tui_gateway/test_bot_live_owner_delivery.py, tui_gateway/session_notifications.py

1 PR closed without merging

From the close comments: merged via another change 1

#108014 fix(tui): throttle idle bot-delivery poll to stop sessions² CPU · merged via another change → 0caf219, #117063, #108005

Closed issues · 1

Closed#108005Desktop `serve` burns up to a full core while idle (cost ≈ open sessions²): per-session notification poller sweeps every session lease with `psutil.Process.status()` ~2×/s

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: #117063
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/108005.json
cluster/108005.md