Cairn
NousResearch/hermes-agent

Config key inconsistencies for max_turns and prefill_messages_file

Cluster 634 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #655 fix: normalize max turns config path · merged via another change → #634
  • #750 fix(config): unify max_turns config location (#634) · done elsewhere → #634
Closed issues · 1
  • Closed#634[Bug]: max_turns config has inconsistent defaults across modules — user-set value not persisted correctly
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
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/634.json
cluster/634.md