Cairn
NousResearch/hermes-agent

Model alias key_env config fixes

Cluster 83847 · agent. Data as of

1 open item. Fix merged in #114809 on 18 Sep 2026. Check it covers your case.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #114809. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

Multiple fixes addressing model aliases silently ignoring key_env/api_key settings, causing wrong API keys to be used, plus related issues with aliases not appearing in the model picker and malformed custom provider configs.

Open issues1

  • Issue#83847model_aliases: key_env is silently ignored (custom provider forced onto OPENAI_API_KEY, causes 401), and aliases never appear in the model picker

Open PRs0

No open pull requests.

Fixes on record

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

  • #114809 fix(config): malformed custom_providers no longer empties the providers view; config set refuses type mismatches; nested aliases keep key_env (#114605, #114471, salvage #45730, #109834)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], hermes_cli/config.py, hermes_cli/config_providers.py, hermes_cli/model_switch.py, tests/hermes_cli/test_config.py, tests/hermes_cli/test_config_set_list_values.py, tests/hermes_cli/test_model_alias_credentials.py, tests/hermes_cli/test_set_config_value.py, website/docs/reference/cli-commands.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #83908 fix(model-alias): honor key_env in direct model aliases · done elsewhere → 3145986, #83612
  • #109834 fix(cli): honour key_env/api_key in config.yaml model.aliases entries · merged via another change → aca2631, #114809, #114605, #114471, #45730, #109834
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
agent
Merged PRs
#114809
Closed issues
0
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/83847.json
cluster/83847.md