Prevent save_config from overwriting config when read returns empty

NousResearch/hermes-agent · cluster 113301

Data as of

Nothing open on GitHub. Fix merged in #114227. Check it covers your case.

The short answer

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

These issues and PRs concern a bug where save_config collapses an existing config.yaml to fewer sections when the cached or raw read returns empty. The fixes add a guard to refuse overwriting an existing config file in that scenario.

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.

  • #114227 save_config no longer collapses an intact config.yaml when the cached read comes back empty (#113301)

    merged to main

    files: hermes_cli/config.py, tests/hermes_cli/test_config.py

4 PRs closed without merging

From the close comments: merged via another change 2 · duplicate 1 · superseded by another PR 1

  • #113321 fix(cli): keep save_config from collapsing over an existing-but-empty config.yaml · merged via another change → 3887082, #114227, #113301
  • #113323 fix(config): refuse to save over an existing config that reads empty · merged via another change → 3887082, #114227
  • #113332 fix(cli): refuse to save over an existing config.yaml that reads empty · superseded by another PR → #113323, #113301
  • #113383 fix(config): refuse to save over an existing config that reads empty (32 sections -> 7) · duplicate → #113323, #113301
Closed issues · 1
  • Closed#113301save_config collapses a config to non-default values when the raw read returns empty (32 sections -> 7)
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.33: 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
#114227
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.