NousResearch/hermes-agent
Gateway config precedence: max_turns versus .env settings
Cluster 19158. Data as of
Nothing open on GitHub. Fix merged in #21240 on 7 May 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #21240. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #21240. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern the gateway's handling of max_turns, where a value from .env (HERMES_MAX_ITERATIONS) may override or replace the configured value after an environment reload. One member broadens this to config.yaml taking precedence over .env for agent, display, and timezone settings; the titles do not establish whether any change was merged or works.
Open issues0
Open PRs0
Fixes on record
1 PR closed without merging
From the close comments: duplicate 1
-
#19183 fix(gateway): preserve max turns after env reload · duplicate →
#18230,#17306
Closed issues · 1
- Closed#19158Gateway max_turns can be overridden by stale HERMES_MAX_ITERATIONS from .env
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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