{"repo":"NousResearch/hermes-agent","public_id":"17534","display_label":"Setup wizard max_turns written to both .env and config.yaml","summary":"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.","subsystem":"hermes_cli","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":17534,"title":"[Bug]: setup wizard double-writes max_turns to both .env (HERMES_MAX_ITERATIONS) and config.yaml (agent.max_turns), causing silent state drift","url":null,"state":"closed"},{"kind":"pr","number":17554,"title":"fix(setup): keep max turns in config","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#17672","number":17672},{"kind":"pr","value":"#17534","number":17534}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":17672,"title":"fix(cli): drop max_turns env-var dual-write in setup wizard (#17534)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#18413","number":18413}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}