fix(runtime): honor provider stop reasons - #136
Merged
Conversation
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.
Summary
pause_turnwith the exact provider content, replacing the prior continuation payload when pauses repeatmax_tokenswith a bounded internal continuation prompt while keeping CMA public events unchangedend_turnend_turn,stop_sequence,refusal, andmodel_context_window_exceededremain valid completed provider responses.tool_usemust contain a client tool call;pause_turnandmax_tokensmust not.The continuation behavior follows the Anthropic stop reason guidance, while the public terminal state remains within the Managed Agents session event contract.
Verification
make verifymake test-servicepause_turn, raw server-tool content,max_tokensrecovery and bounds, and contradictory provider responses