Cairn

Fallback provider key_env/api_key_env resolution bug fixes

NousResearch/hermes-agent · cluster 14105

Data as of

Nothing open on GitHub. Fix merged in #14116. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #14116. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #14116. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple bug reports and fix attempts addressing that key_env/api_key_env fields are silently ignored when resolving API keys for fallback provider chain entries. The cluster centers on a single recurring issue with several overlapping fix PRs targeting the same code path.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #14116 fix(agent): resolve fallback provider key_env secrets

    merged to main

    files: run_agent.py, tests/run_agent/test_provider_fallback.py

  • #27308 Batch salvage group 4: 9 low-risk new-contributor PRs (proxy-env/gateway-fixes/security-headers/custom-providers)

    merged to main

    files: agent/auxiliary_client.py, gateway/platforms/api_server.py, gateway/platforms/base.py, gateway/platforms/helpers.py, gateway/platforms/slack.py, gateway/platforms/sms.py, gateway/run.py, hermes_cli/doctor.py, plugins/platforms/google_chat/adapter.py, plugins/platforms/line/adapter.py, plugins/platforms/teams/adapter.py, scripts/release.py, tests/gateway/test_api_server.py, tests/gateway/test_bluebubbles.py, tests/gateway/test_update_streaming.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #25294 fix(auxiliary): resolve api_key_env alias in named custom provider path of resolve_provider_client · merged via another change → #27308
Closed issues · 2
  • Closed#14105[Bug] fallback_providers ignores key_env — only reads api_key field
  • Closed#25091[Bug]: `api_key_env` alias silently ignored in `fallback_providers` entries — falls through to "no-key-required" placeholder
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.34: 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

Merged PRs
#14116, #27308
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
17 May 2026

For your agent

The same facts, typed.

cluster/14105.json
cluster/14105.md