fix(chat): continue gRPC responses until natural EOS - #161
Merged
Conversation
Treat max_tokens as an internal streaming chunk instead of a response limit, preserve an optional safety cap, and report real stop reasons and throughput. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
Generate.max_tokensas a streaming chunk size rather than a full-answer limitSTOP_REASON_MAX_TOKENSWhy
The gRPC REPL returned to
you>every 64 tokens, making healthy max-token chunk boundaries look like network truncation. The older Mac chat path already used natural EOS semantics; this brings the session-bound gRPC client to the same contract.Tests
PYTHONPATH=.:sdks/python pytest -q tests/scripts/test_chat_grpc.pypython -m py_compile scripts/chat_grpc.pyMade with Cursor