NousResearch/hermes-agent

Config YAML writer: long keys and read-error handling

Cluster 120682 · hermes cli. Data as of 2026-10-26 12:29 UTC

1 open item. Fix merged in #120343 on 23 Sep 2026. Check it covers your case.

open issue

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 0 issues already closed.
Fix event: A fix was merged to main in PR #120343. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #120343, then check whether your report is the one still open.

Read #120343 Pick up a Lab task

The members concern config.yaml handling: one bug report and one fix address long, space-containing mapping keys being folded at width 80 and producing invalid YAML. A third item covers a transient read error affecting config.yaml contents. The first two share a theme; the third is related but distinct, and no outcome is stated here.

Open issues1

Issue#120682[Bug]: config writer folds long scalars at width 80 - a space-containing config KEY is emitted as invalid YAML and the backend refuses to start

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#120343 fix(config): a transient read error no longer wipes config.yaml (explicit nulls kept, no phantom agent section; salvage #105828, #119846)

merged to main

files: gateway/slash_commands.py, hermes_cli/auth.py, hermes_cli/config.py, hermes_cli/config_effective.py, hermes_cli/config_read_errors.py, hermes_cli/web_routers/config_env.py, hermes_cli/xai_retirement.py, tests/hermes_cli/test_config.py, tests/hermes_cli/test_config_save_integrity.py, tests/hermes_cli/test_resolve_provider_corrupt_config.py, tests/hermes_cli/test_xai_retirement.py, tests/test_utils_atomic_roundtrip_yaml_save.py, tui_gateway/server.py, utils.py

1 PR closed without merging

From the close comments: merged via another change 1

#120685 fix(config): preserve long YAML mapping keys · merged via another change → #120682, #120343

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

Subsystem: hermes cli
Merged PRs: #120343
Closed issues: 0
Attempts: 1 PR closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/120682.json
cluster/120682.md