NousResearch/hermes-agent

Custom-provider key_env lookup with .env and profile secrets

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

Nothing open on GitHub. Fix merged in #115885 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 #115885. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #115885. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #115885 Pick up a Lab task

These members all concern how a custom provider's key_env value is looked up, including the interaction between .env edits, stale os.environ values, and the profile secret scope. One is a bug report of 401 errors on a long-lived desktop local gateway after a .env edit, and two are fix PRs referencing #67935 that touch the CLI model picker/Ollama catalog and agent-side lookup.

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.

#115885 fix(cli): custom-provider key_env in the model picker and Ollama catalog resolves through the profile secret scope (#67935)

merged to main

files: hermes_cli/model_setup_flows_custom.py, hermes_cli/models_local.py, tests/hermes_cli/test_custom_provider_key_env_scope.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#67947 fix(agent): resolve custom-provider key_env preferring .env over stale os.environ (#67935) · superseded by another PR → #115885, #67935

Closed issues · 1

Closed#67935[Bug]: Desktop local gateway: custom provider key_env fails 401 after .env edit (long-lived hermes serve)

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

For your agent

The same facts, typed.

cluster/67935.json
cluster/67935.md