# NousResearch/hermes-agent · config set wrongly blocks or writes runtime-read keys

## Open now

- Nothing open on GitHub.

A bug introduced around #112003 causes \`hermes config set\` to either hard-fail or incorrectly write keys that are designated as runtime-read. The cluster covers the problem report, a salvage attempt, and a fix.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #114226. Verify it addresses your case.
- **Recommended:** read PR #114226 (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-114226`. 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.67`: 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

- #114107: \`hermes config set\` now refuses documented, runtime-read keys (\`skills.creation_nudge_interval\`, \`display.tool_progress\`, \`stt.provider\`, …) — since #112003 the DEFAULT_CONFIG walk hard-fails 164 of the 242 paths in #96715 and 11 keys from \`cli-config.yaml.example\`

## Prior & competing PRs

- **#114226: hermes config set writes unseeded runtime-read keys instead of refusing them (#114107, salvage #114113)**. 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/reference/cli-commands.md`, `website/docs/user-guide/configuration.md`
- **#114113: fix(config): allow runtime-read config keys**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `2cf1351779`, `#114226`

## Fix status

- Merged to main in PR #114226 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-17`.