NousResearch/hermes-agent
Named custom provider identity lost in various surfaces
Cluster 3114 · hermes cli. Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMultiple fixes addressing a bug where named custom providers lose their identity and get grouped or displayed as generic 'Custom' or 'Custom Endpoint' across the model picker, config, CLI, desktop, and vision routing. The underlying issue involves provider names being stripped or not preserved through various code paths.
Open issues1
- Issue#66329Bug: Model picker groups selected model under "CUSTOM ENDPOINT" instead of correct named provider
Open PRs2
2 PRs closed without merging
From the close comments: done elsewhere 1 · other 1
Closed issues · 1
- Closed#3114CLI /model display omits named custom providers from custom_providers
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.29: 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
- hermes cli
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging