NousResearch/hermes-agent
Custom providers show no models in model picker
Cluster 47042 · apps/desktop. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
10items grouped
- Known?
- Yes. 10 related items grouped here, 8 issues 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
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMembers report that custom or user-defined providers appear with zero models (or are hidden) in the GUI, Desktop, TUI, or /model picker, with several pointing to aggregator classification and deduplication logic as the cause. Some members are proposed fixes that skip deduplication for custom providers.
Open issues0
Open PRs0
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 8
- Closed#47042[BUG] Desktop model picker hides custom providers due to is_aggregator() false positive in dedup logic
- Closed#47124[Bug]: Custom endpoints do not appear in the Agent because their models are wiped by the aggregator deduplication logic
- Closed#47132bug(inventory): named custom providers lose all models in GUI picker after 60cc42e38
- Closed#47155Regression: /model hides custom:* provider after deduplication empties its model list
- Closed#47258UI model picker shows 0 models for custom_providers entries
- Closed#47386Custom providers with models: list show 0 models in Desktop/TUI model picker
- Closed#47402Model picker shows 0 models for custom: providers due to is_aggregator() treating all custom: slugs as aggregators
- Closed#48990Bug: custom_providers models silently stripped from /model picker
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.22: 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
- apps/desktop
- Closed issues
- 8
- Attempts
- 2 PRs closed without merging