Named custom auth credential precedence and missing key handling

NousResearch/hermes-agent · cluster 117743 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 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 items address inconsistent precedence rules between main pool and auxiliary key_env for named custom credentials, and the behavior when a declared key is absent. The focus is on unifying resolution order and ensuring missing credentials are rejected rather than silently substituted.

Open issues1

  • Issue#117743Named custom auth: missing key resolves placeholder; main pool precedence diverges from auxiliary key_env

Open PRs2

  • PR#117753fix(auth): unify named custom credential precedence and fail closed on missing declared key
  • PR#117757fix(provider-auth): reject missing named credentials before requests
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
0 PRs closed without merging

For your agent

The same facts, typed.