Cairn
NousResearch/hermes-agent

Model picker shows named provider models under custom endpoint

Cluster 66329 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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.

These members appear to concern the model picker grouping a selected model under a generic "Custom endpoint" heading rather than its named provider, including a bug report and related changes to preserve provider names in config and avoid duplicate custom rows. The titles suggest one shared theme, though details beyond them are not shown.

Open issues1

  • Issue#66329Bug: Model picker groups selected model under "CUSTOM ENDPOINT" instead of correct named provider

Open PRs2

  • PR#66367fix: model picker groups selected model under CUSTOM instead of correct provider (#66329)
  • PR#66370fix(cli): don't emit duplicate 'Custom endpoint' row for named custom…

1 PR closed without merging

From the close comments: other 1

  • #66374 fix(model): preserve provider name in config for providers: entries (#66329) · other
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.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

Subsystem
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/66329.json
cluster/66329.md