NousResearch/hermes-agent

Roster poll performance: reduce redundant state reads

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

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

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

Read #117601 Pick up a Lab task

These issues and PRs address performance costs in the 5-second Bots roster poll, which repeatedly reopens state databases and reloads session, UI metadata, and YAML-derived fields even when their underlying sources have not changed.

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.

#117601 perf(profiles): the 5s roster poll reuses each profile's session and YAML-derived fields while their files have not moved (#117257 #117383 #117378, salvage #117258 #117380)

merged to main

files: hermes_cli/profiles.py, tests/hermes_cli/test_profile_listing_cache.py, tests/tui_gateway/test_profiles_list_session_field_cache.py, tests/tui_gateway/test_profiles_list_ui_meta_cache.py, tui_gateway/methods_profiles.py, tui_gateway/profile_roster_cache.py

1 PR closed without merging

From the close comments: done elsewhere 1

#117258 perf(gateway): the roster poll reuses each profile's session and ui_meta fields while their sources have not moved · done elsewhere → #117601

Closed issues · 1

Closed#117257[Perf]: the 5s Bots roster poll reopens every profile's state.db, and the cost grows with session history

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

For your agent

The same facts, typed.

cluster/117257.json
cluster/117257.md