Cairn
NousResearch/hermes-agent

Auth credential pool base_url ignored during provider resolution

Cluster 42269 · 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.

The members concern credentials added via hermes auth add (e.g. deepseek) being stored in a pool while provider resolution appears not to use them, specifically around pool entry base_url handling and error logging in _resolve_api_key_p…. Two members are fix-oriented pull requests and one is an issue report, all touching the same auth resolution area.

Open issues1

  • Issue#42269hermes auth add deepseek: credential stored to pool but provider resolution ignores it at runtime

Open PRs1

  • PR#42386fix(auth): surface pool base_url and log errors in _resolve_api_key_p…

1 PR closed without merging

From the close comments: other 1

  • #42425 fix(auth): honour pool entry base_url in provider credential resolution (#42269) · 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.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.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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/42269.json
cluster/42269.md