docs: add subagent guardrail tuning guidance - #68350
Closed
ajzrva-sys wants to merge 1 commit into
Closed
Conversation
alt-glitch
added
type/docs
teknium1
reviewed
Jul 30, 2026
teknium1
left a comment
teknium1
left a comment
Contributor
There was a problem hiding this comment.
Thanks for adding operational guidance for autonomous work.
Problems
website/docs/user-guide/configuration.md:1448points todelegation.progress_tracker, but current main has no such configuration or implementation. The destination fragment is also invalid: the configuration page exposes## Delegationatwebsite/docs/user-guide/configuration.md:2144, not#subagent-delegation.- The snippet is presented as subagent/cron tuning, but
tool_loop_guardrailsis global:agent/agent_init.py:1593-1596loads it for AIAgent instances, including delegated children (tools/delegate_tool.py:1505) and cron jobs (cron/scheduler.py:3477). Enabling these values would also change interactive parent-session behavior.
Suggested changes
- Remove the nonexistent progress-tracker reference until its implementation and documentation land.
- Clarify the global scope of this configuration, or avoid framing it as a subagent/cron-only setting.
Automated hermes-sweeper review.
| max_iterations: 80 # default is 50; bump for complex tasks | ||
| ``` | ||
|
|
||
| For **cross-turn non-convergence** (different tool calls each turn, no output), see `delegation.progress_tracker` in the [Delegation](#subagent-delegation) section. |
Contributor
There was a problem hiding this comment.
delegation.progress_tracker is not implemented or documented on current main, and this page's delegation heading resolves to #delegation, not #subagent-delegation. Please remove this reference until the setting exists.
teknium1
added
the
sweeper:blast-contained
Recommend enabling hard_stop_enabled with tighter thresholds for delegate_task subagents and cron jobs. References cross-turn progress tracker (delegation.progress_tracker) and max_iterations config.
ajzrva-sys
force-pushed
the
docs/subagent-guardrail-tuning
branch
2 times, most recently
from
August 1, 2026 02:03
3ee35e4 to
51212d9
Compare
Contributor
Author
|
The documented feature (subagent non-convergence guardrail, #68348) hasn't landed on main yet. Closing until the implementation is ready. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a "Subagent / Autonomous Sessions" subsection under Tool-Loop Guardrails with recommended config for
delegate_tasksubagents and cron jobs.Why
Defaults (
hard_stop_enabled: false, loose thresholds) are right for interactive sessions where a human can intervene. Subagents running autonomously burn iteration budget on repeated failures before the guardrails kick in. Tightening thresholds saves budget for productive work.References #414 (iteration budget pressure). Complementary to #68348 (cross-turn progress tracker).