Repository navigation
fix(provider): deliver Omni images as lossless WebP - #33
Merged
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.
Omni image-heavy sessions can exceed request body limits as PNG observations accumulate. Both Omni profiles now encode inline PNGs as lossless WebP after context selection, preserving pixels, dimensions, tool receipts, and the original history. Existing batched
sliding_windowremains the mechanism for bounding image history.Also accept an empty streamed tool-argument delta when the Messages content block already contains
{}. Previously, a valid no-argument tool call failed JSON parsing before dispatch; malformed nonempty arguments and incomplete streams still fail validation.Validation: