Normalize agent.max_turns string value handling
Cluster 82813 · hermes cli. Data as of
2 open items. Fix merged in #90708 on 20 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #90708. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #90708. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
These members address inconsistent parsing of 'none' and 'unlimited' string values for agent.max_turns in config, including a bug report, a fix for spelling normalization, and a feature to handle these values as first-class options.
Open issues0
Open PRs2
Fixes on record
-
#90708 feat(config): agent.max_turns unlimited by default (salvage #67696, fixes #82813)
files:
agent/agent_init.py,cli.py,contributors/emails/[email protected],cron/scheduler.py,gateway/run.py,hermes_cli/config.py,hermes_cli/config_defaults.py,run_agent.py,tests/cli/test_cli_init.py,tests/hermes_cli/test_resolve_turn_limit.py,tui_gateway/server.py,website/docs/user-guide/configuration.md
Closed issues · 1
- Closed#82813[Bug] agent.max_turns accepts 'none'/'unlimited' in config.yaml but crashes or silently falls back to default
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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #90708
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 20 Aug 2026