# NousResearch/hermes-agent · Config key inconsistencies for max_turns and prefill_messages_file

## Open now

- Nothing open on GitHub.

These issues and fixes address two configuration handling problems: max_turns defaults being inconsistent across modules, and prefill_messages_file being ignored or misread in certain backends (CLI, Desktop App) due to key path mismatches.

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

- #634: \[Bug\]: max_turns config has inconsistent defaults across modules — user-set value not persisted correctly

## Prior & competing PRs

- **#655: fix: normalize max turns config path**. closed without merge · fix tier `suggested`
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#634`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#750: fix(config): unify max_turns config location (#634)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#634`

## Fix status

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