Config set routing: .env vs config.yaml key handling
Cluster 111848. Data as of
Nothing open on GitHub. Fix merged in #112562 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #112562. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112562. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern how hermes config set decides where to write values—specifically, the incorrect or inconsistent routing of environment-style keys between .env and config.yaml, and validation of paths before writing.
Open issues0
Open PRs0
Fixes on record
-
#112250 fix(config): `hermes config set` refuses typo paths before writing and routes env settings to .env (#112003, #111848, salvage #111850)
files:
hermes_cli/AGENTS.md,hermes_cli/config.py,hermes_cli/config_env_routing.py,hermes_cli/subcommands/config.py,tests/hermes_cli/test_config.py,tests/hermes_cli/test_config_dotted_key_names.py,tests/hermes_cli/test_config_platform_env_routing.py,tests/hermes_cli/test_config_set_list_values.py,tests/hermes_cli/test_set_config_value.py,website/docs/reference/cli-commands.md,website/docs/reference/environment-variables.md,website/docs/user-guide/configuration.md -
#112562 hermes config set stores every UPPER_SNAKE name in .env, never config.yaml (#111848)
files:
hermes_cli/config.py,hermes_cli/config_env_routing.py,tests/hermes_cli/test_config_platform_env_routing.py,website/docs/reference/cli-commands.md,website/docs/reference/environment-variables.md,website/docs/user-guide/configuration.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#111850 fix(config): route platform setup values through .env · merged via another change →
da98103,#112250
Closed issues · 1
- Closed#111848`hermes config set <non-credential env key>` writes config.yaml top-level instead of .env → two "official" writers for platform keys, two different readers
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 Lab