NousResearch/hermes-agent
Fallback mislabels custom providers as 'custom'
Cluster 98739 · agent. Data as of
2 open items. Fix merged in #98757 on 14 Sep 2026. Check it covers your case.
The short answer
0open issues
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #98757. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #98757. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
These issues and fixes address a bug where automatic fallback to a custom provider incorrectly displays 'custom' in the UI and billing records instead of the provider's configured name.
Open issues0
Open PRs2
Fixes on record
-
#98757 fix(fallback): automatic fallback no longer relabels named custom providers as 'custom' (#98739)
files:
cron/scheduler.py,gateway/run.py,hermes_cli/fallback_config.py,tests/hermes_cli/test_fallback_config.py,tui_gateway/server.py
Closed issues · 1
- Closed#98739Fallback to custom provider shows "custom" in UI instead of configured provider name
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
- Subsystem
- agent
- Merged PRs
- #98757
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 14 Sep 2026