NousResearch/hermes-agent
Fix API key reading in CLI and runtime
Cluster 117667 · hermes cli. Data as of
2 open items. Fix merged in #131926 on 5 Oct 2026. Check it covers your case.
The short answer
0open issues
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131926. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131926. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
A bug report and two fixes addressing cases where provider API keys were not being read from config.yaml or .env files during one-shot CLI calls and OpenRouter fallback key lookups.
Open issues0
Open PRs2
Fixes on record
-
#131926 fix(runtime): read the OpenRouter fallback keys from .env after an exhausted pool entry [risk 0.30]
files:
hermes_cli/config.py,hermes_cli/runtime_provider_backends.py,tests/hermes_cli/test_runtime_provider_resolution.py
Closed issues · 1
- Closed#117667[Bug]: One-shot `hermes chat` CLI calls don't read provider API keys from config.yaml or .env
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.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #131926
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 5 Oct 2026