# NousResearch/hermes-agent · Safer config.yaml write and parse error handling

## Open now

- Nothing open on GitHub.

These items address edge cases in writing config.yaml, including locked files, unreadable files, and parse failures, with the goal of preserving valid configuration state. The work covers both refusing unsafe overwrites and retaining last-known-good config on parse errors.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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

- #5214: Improve handling for locked or invalid config.yaml writes

## Prior & competing PRs

- **#5215: fix(config): handle locked config writes safely**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#81472`
- **#81472: fix(config): handle locked config writes safely**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#5214`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`