NousResearch/hermes-agent

config set wrongly blocks or writes runtime-read keys

Cluster 114107. Data as of 2026-10-26 12:29 UTC

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

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

Read #114226 Pick up a Lab task

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.

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.

#114226 hermes config set writes unseeded runtime-read keys instead of refusing them (#114107, salvage #114113)

merged to main

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

1 PR closed without merging

From the close comments: merged via another change 1

#114113 fix(config): allow runtime-read config keys · merged via another change → 2cf1351, #114226

Closed issues · 1

Closed#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`

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

Merged PRs: #114226
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 17 Sep 2026

For your agent

The same facts, typed.

cluster/114107.json
cluster/114107.md