Model reporting accuracy in status and usage endpoints
Cluster 109282. Data as of
Nothing open on GitHub. Fix merged in #110223 on 13 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #110223. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #110223. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern how /status and /usage report the active or current model during gateway sessions, particularly when the displayed model may reflect stale, historical, or non-dominant routing rather than the live compute-host model.
Open issues0
Open PRs0
Fixes on record
-
#110223 Idle /status and /usage report the most recent model route, not the lifetime-dominant one (#109282, salvage #109292 #109289)
files:
gateway/slash_commands_status.py,hermes_state_sessions.py,tests/gateway/test_status_command.py,tests/gateway/test_usage_command.py,tests/hermes_state/test_recent_model_route.py,tests/tui_gateway/test_tui_gateway_server.py,tui_gateway/methods_session.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#109282[Bug]: /status reports a stale historical model as the current model on long gateway sessions
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.00means 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 LabAt a glance
- Merged PRs
- #110223
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 13 Sep 2026