Cairn
NousResearch/hermes-agent

Setup wizard max_turns written to both .env and config.yaml

Cluster 17534 · 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 members concern the setup wizard storing max_turns in two places, the HERMES_MAX_ITERATIONS env var in .env and agent.max_turns in config.yaml, which one report says causes state drift. Two titles propose changes to stop the dual-write and keep the value in config; their outcome is not established here.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #17554 fix(setup): keep max turns in config · other → #17672, #17534
  • #17672 fix(cli): drop max_turns env-var dual-write in setup wizard (#17534) · done elsewhere → #18413
Closed issues · 1
  • Closed#17534[Bug]: setup wizard double-writes max_turns to both .env (HERMES_MAX_ITERATIONS) and config.yaml (agent.max_turns), causing silent state drift
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/17534.json
cluster/17534.md