fix(chat): raise MAX_CONSECUTIVE_TRUNCATIONS 5 → 20#59
Merged
Conversation
Truncation retries were bailing out too aggressively on long agentic runs that legitimately hit the cap several iterations in a row. 20 gives the model more room to make progress while still bounding worst-case spend.
DIodide
added a commit
that referenced
this pull request
Apr 29, 2026
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.
Bumps the consecutive-truncation safety cap so long agentic runs that legitimately hit the token cap multiple iterations in a row aren't bailed out prematurely. Worst-case spend is still bounded (now ~20× output budget instead of ~5×), well below the existing MAX_TOOL_ITERATIONS=120 ceiling.