fix: Preserve UI message step boundaries#88
Merged
Conversation
commit: |
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
2 participants
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.
What this PR does / why we need it:
Persist generation step boundaries as
step-startUI message parts and rebuild model history by generation step. This keeps reasoning and multiple tool calls from the same generation in one assistant message when continuing a conversation.Resolve effective reasoning-history support from model-level tri-state overrides and provider defaults, and expose the configuration in the Console without adding provider-specific conversion branches.
Add Java and TypeScript regression coverage for multi-tool steps, persistence, validation, capability resolution, and unsupported reasoning history.
Does this PR introduce a user-facing change?