# NousResearch/hermes-agent · Setup wizard max_turns written to both .env and config.yaml

## Open now

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

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

- #17534: \[Bug\]: setup wizard double-writes max_turns to both .env (HERMES_MAX_ITERATIONS) and config.yaml (agent.max_turns), causing silent state drift

## Prior & competing PRs

- **#17554: fix(setup): keep max turns in config**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#17672`, `#17534`
- **#17672: fix(cli): drop max_turns env-var dual-write in setup wizard (#17534)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#18413`

## Fix status

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