feat(agent-core): add config hint to max-steps-per-turn error - #1097
Merged
Conversation
🦋 Changeset detectedLatest commit: 5fb1381 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Merged
5 tasks
7723qqq
pushed a commit
to 7723qqq/kimi-code
that referenced
this pull request
Jul 11, 2026
…otAI#1097) * feat(agent-core): add config hint to max-steps-per-turn error * test(agent-core): assert config hint in max-steps error (cherry picked from commit 27ef516)
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
1 participant
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.
Related Issue
No related issue.
Problem
When a turn exceeds
loop_control.max_steps_per_turn, the agent only reportsTurn exceeded maxSteps=N. Users who hit the limit because it is set too low get no hint that they can raise it themselves inconfig.toml, so the error is not actionable.What changed
Append a hint to the max-steps-exceeded error message that points users to the
loop_control.max_steps_per_turnoption inconfig.toml, and align the error code'sactiontext to match. The existing turn test now asserts the hint appears in the error payload.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.