acp_thread: Clarify max token limit error message#52724
Merged
bennetbo merged 5 commits intozed-industries:mainfrom Mar 30, 2026
Merged
acp_thread: Clarify max token limit error message#52724bennetbo merged 5 commits intozed-industries:mainfrom
bennetbo merged 5 commits intozed-industries:mainfrom
Conversation
bennetbo
approved these changes
Mar 30, 2026
Member
bennetbo
left a comment
There was a problem hiding this comment.
Pushed a change that also adjusts the logging message. Thank you!
Contributor
Author
ohh sorry ! |
Contributor
Author
|
Hey @bennetbo , the tests need to be update. Some more tests failing though, its not regarding our change but somehting regarding audio logs |
auto-merge was automatically disabled
March 30, 2026 12:45
Pull Request is not mergeable
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
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.
When generation stops due to the per-response output limit, Zed was surfacing "Max tokens reached", which implies the full context window was exhausted. In reality,
max_output_tokens(the per-response cap) may have been hit a different condition.This change distinguishes between the two cases: if
output_tokens >= max_output_tokens, it surfaces "Maximum output tokens reached"; otherwise it falls back to "Maximum tokens reached".Self-Review Checklist:
Closes #50254
Note : Reopens #50372 suggested by @bennetbo
Release Notes: