.enabled\` writes to a key the gateway loader never reads, along with several related fixes to redirect or reconcile the config path so the gateway correctly consults the intended location. ## TL;DR - 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging. - A fix was merged to main in PR #116745. Verify it addresses your case. - **Recommended:** read PR #116745 (and any competing PRs below) before filing. Confirm the merged change covers your symptom. ## Maintainer resolution verdict - Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-116745`. This is distinct from the fix status above. Weigh it yourself. ## How this cluster was grouped - Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. - Pairwise link density `0.50`: the share of member 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. ## Closed / duplicate issues - #115212: \[Bug\]: \`hermes config set gateway.platforms.
.enabled\` reports success but writes a key the loader never reads ## Prior & competing PRs - **#116745: fix(config): hermes config set gateway.platforms.
.enabled lands on the platforms block the gateway reads (#115212)**. merged to main · fix tier `verified` - maintainer direction: category `merged` - files: `hermes_cli/config.py`, `tests/hermes_cli/test_set_config_value.py`, `website/docs/user-guide/configuration.md` - **#115226: fix(config): redirect gateway.platforms.
. .