Cairn

custom provider api_key_env alias not working

NousResearch/hermes-agent · cluster 44666 · agent

Data as of

7 open items. Fix attempted, not merged.

The short answer

2open issues
5open PRs
14items grouped
Known?
Yes. 14 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 6 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 5 PRs.

A bug where the api_key_env configuration alias is silently ignored when locating named custom providers, causing authentication errors. Multiple patches address this across CLI, runtime, config, auxiliary routing, and desktop persistence.

Open issues2

  • Issue#46690[BUG] Named custom provider's api_key_env not resolved in resolve_provider_client — leads to HTTP 401
  • Issue#62254_get_named_custom_provider silently ignores api_key_env — only reads key_env

Open PRs5

  • PR#19213fix(config): resolve direct model aliases at runtime
  • PR#44868fix(cli): accept api_key_env alias in providers entries
  • PR#45873fix(runtime_provider): resolve key_env/api_key_env from env for custom providers (#44666, #43586)
  • PR#62507fix: accept api_key_env as fallback in custom provider resolution (#62254)
  • PR#62534fix(cli): resolve --model <alias> through model_aliases in interactive chat (#62491)

6 PRs closed without merging

From the close comments: duplicate 3 · superseded by another PR 3

  • #44667 fix(runtime): handle api_key_env alias in _get_named_custom_provider · superseded by another PR
  • #44669 fix(runtime-provider): accept api_key_env alias in named custom providers · duplicate → #44667
  • #44684 fix(cli): honor api_key_env for custom providers · duplicate → #44667
  • #44768 fix(runtime_provider): respect api_key_env alias in custom provider entries (#44666) · superseded by another PR → #44667, #44666
  • #46023 fix(config): honor api_key_env alias in providers dict and custom_providers list · duplicate → #44667
Show 1 more
  • #96237 fix: honor api_key_env alias in providers dict resolver · superseded by another PR
Closed issues · 1
  • Closed#44666[Bug]: `api_key_env` alias silently ignored in `providers:` entries — named custom provider falls through to "no-key-required"
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.14: 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
1
Attempts
6 PRs closed without merging

For your agent

The same facts, typed.

cluster/44666.json
cluster/44666.md