Fix custom provider disambiguation by api_mode field

NousResearch/hermes-agent · cluster 102725 · 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.

A bug where custom providers sharing the same base URL and model but differing by api_mode were incorrectly collapsed to the first entry, causing display and runtime desync. Fixes persist and apply api_mode to correctly distinguish such providers.

Open issues1

  • Issue#102725[Bug]: same model + same base_url custom providers with different api_mode always heal to first entry (display vs runtime desync)

Open PRs2

  • PR#102749fix(agent): disambiguate custom providers sharing base_url by api_mode (#102725)
  • PR#135580fix: preserve requested custom provider identity in session state

1 PR closed without merging

From the close comments: duplicate 1

  • #102748 fix(config): disambiguate same-URL/model custom providers by persisted api_mode · duplicate → #102749
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.