Cairn

Named custom provider API key propagation fixes

NousResearch/hermes-agent · cluster 96232 · agent

Data as of

5 open items. Fix attempted, not merged.

The short answer

1open issue
4open PRs
5items grouped
Known?
Yes. 5 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 4 PRs.

A bug where explicit API keys were dropped or rejected when using named custom providers for auxiliary vision tasks. Multiple fixes address threading, lifting, and propagating these keys correctly through the provider resolution path.

Open issues1

  • Issue#96232[Bug] Auxiliary vision drops explicit API key for named custom providers

Open PRs4

  • PR#96248fix(auxiliary): thread the explicit vision api_key to named custom providers
  • PR#96249fix(auxiliary): stop named vision providers from rejecting explicit API keys
  • PR#96254fix(auxiliary): propagate explicit API key to named custom providers (#96232)
  • PR#106916fix(agent): lift named custom provider key when a task base_url flattens it to bare custom
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.40: 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.

cluster/96232.json
cluster/96232.md