Cairn

Custom provider API key sourcing corrections

NousResearch/hermes-agent · cluster 43586 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

Multiple corrections address how key_env and api_key_env are sourced for custom provider configurations, where API keys were being ignored or not properly drawn from environment variables. Coverage includes credential pooling, direct-alias branches, and runtime provider handling.

Open issues1

  • Issue#43586[Bug]: model: block with bare 'provider: custom' + key_env ignores the API key (sends 'no-key-required' → 401)

Open PRs3

  • PR#43675fix(config): resolve key_env and api_key from model config in direct-alias branch
  • PR#43704fix(config): honor key_env for custom provider
  • PR#45873fix(runtime_provider): resolve key_env/api_key_env from env for custom providers (#44666, #43586)
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/43586.json
cluster/43586.md