Repository navigation
Avoid full-string scans in token-budget truncation - #49712
Merged
copyberry[bot] merged 1 commit intoSep 30, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why Token-budget truncation uses byte counts to estimate tokens, but previously scanned the entire string to count characters, including the discarded middle. ## What changed Use UTF-8 boundary lookups to select the retained prefix and suffix for token-budget truncation. Skip character counting for a zero-token budget and defer it to paths that need character counts. ## Testing Add regression coverage for multibyte characters crossing both retained boundaries, checking the truncated output and original token estimate. GitOrigin-RevId: 37fee0c8d4ede8e74b491d3d641b0ea0e9003dd4
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/37fee0c8d4ede8e74b491d3d641b0ea0e9003dd4
branch
from
September 30, 2026 19:15
1d3b613 to
5e96aab
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/37fee0c8d4ede8e74b491d3d641b0ea0e9003dd4
branch
September 30, 2026 19:15
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Avoid full-string scans in token-budget truncation
Why
Token-budget truncation uses byte counts to estimate tokens, but previously scanned the entire string to count characters, including the discarded middle.
What changed
Use UTF-8 boundary lookups to select the retained prefix and suffix for token-budget truncation. Skip character counting for a zero-token budget and defer it to paths that need character counts.
Testing
Add regression coverage for multibyte characters crossing both retained boundaries, checking the truncated output and original token estimate.