NousResearch/hermes-agent
Credential pool key isolation for shared-URL providers
Cluster 124527 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 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 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items concern a bug where a bare custom model and a named provider sharing the same base URL could incorrectly use each other's API keys, and related fixes to bind credentials to their correct owners in the credential pool.
Open issues1
- Issue#124527[Bug]: A bare `custom` model and a named provider on the same base_url use each other's key; openrouter.ai ignores the configured model key
Open PRs1
- PR#124528fix(credential-pool): keep a bare-custom model and a same-URL provider on their own keys
1 PR closed without merging
From the close comments: partial fix 1
-
#124578 fix(credential-pool): bind shared custom endpoints to runtime owners (#124527) · partial fix →
ec07d9a,#124527,#124528
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.67: 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
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging