NousResearch/hermes-agent

Custom provider model.key_env key resolution in bare provider path

Cluster 67453 · agent. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #115791 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #115791, then check it covers your case.

Read #115791 Pick up a Lab task

The members concern how a bare custom provider resolves the API key named by model.key_env, including one report of 401/403 errors in sessions after the first and two pull requests referencing #67453 that change config or provider handling. One also mentions a warning for unset key_env. Outcomes are not established from these titles.

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.

#115791 fix(providers): bare custom provider sends the key named by model.key_env; unset key_env is warned about (#67453, salvage #67554)

merged to main

files: agent/model_metadata.py, hermes_cli/runtime_provider_backends.py, hermes_cli/runtime_provider_custom.py, tests/agent/test_output_cap_parsing.py, tests/hermes_cli/test_runtime_provider_resolution.py, website/docs/integrations/providers.md

1 PR closed without merging

From the close comments: merged via another change 1

#67554 fix(config): resolve model.key_env in bare custom provider path (#67453) · merged via another change → 709e7ad, #115791, #67453, #67554

Closed issues · 1

Closed#67453[bug] custom provider `key_env` only resolved for the first session after boot — all subsequent sessions get 401/403

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.67: 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
Merged PRs: #115791
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/67453.json
cluster/67453.md