Terminal config precedence over .env TERMINAL_ENV
NousResearch/hermes-agent · cluster 71137 · environments
Data as of
Nothing open on GitHub. Fix merged in #76047. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #76047. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #76047. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the .env TERMINAL_ENV value silently overrides the terminal.backend setting in config.yaml. The work focuses on ensuring explicit config.yaml terminal settings take precedence over stale .env values.
Open issues0
Open PRs0
Fixes on record
-
#76047 fix(terminal): honor explicit config keys over stale .env TERMINAL_ENV (#71137)
files:
hermes_cli/config.py,tests/tools/test_terminal_env_bridge.py,tools/terminal_tool.py -
#77180 fix(env): config.yaml terminal.* keys win over stale .env on every reload (#29186)
files:
hermes_cli/env_loader.py,tests/gateway/test_runtime_env_reload_config_authority.py,tests/hermes_cli/test_dump_terminal_backend.py,tests/hermes_cli/test_env_loader.py
3 PRs closed without merging
From the close comments: merged via another change 2 · superseded by another PR 1
-
#71139 fix(terminal): config.yaml terminal section takes precedence over .env TERMINAL_ENV · superseded by another PR →
#77180 -
#71247 fix(tools): config.yaml terminal.backend overrides stale .env TERMINAL_ENV (#71137) · merged via another change →
#76047,#71139 -
#71384 fix(terminal): config.yaml terminal.backend takes precedence over .env TERMINAL_ENV · merged via another change →
#76047,#71247,#71139
Closed issues · 1
- Closed#71137[Bug]: .env TERMINAL_ENV=ssh silently overrides config.yaml terminal.backend=local
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.33: 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 Lab