Model picker shows wrong model under mismatched provider

NousResearch/hermes-agent · cluster 125640 · 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 issues and fixes address a bug where a model from one provider family appears injected into a different provider's row in the model picker UI. The work focuses on preventing cross-family model defaults from leaking into the wrong provider's picker entry.

Open issues1

  • Issue#125640[Bug]: Model picker injects current_model into wrong provider's row when provider/model config is mismatched (Sonnet 5 shown under ChatGPT/Codex)

Open PRs2

  • PR#125670fix(cli): keep a cross-family leftover default out of the current provider's picker row
  • PR#125675fix(cli): keep a foreign-family model.default out of the picker's current-provider row (#125640)

1 PR closed without merging

From the close comments: duplicate 1

  • #125667 fix(cli): avoid injecting mismatched models into provider picker · duplicate → #125640, #125670
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.