feat(ag-ui): preserve owned protocol transcripts at request egress - #1164
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
enabled auto-merge (squash)
September 24, 2026 22:21
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
This branch was successfully deployed
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.
The neutral display message contract cannot preserve the complete AG-UI transcript needed for a later request: it omits protocol roles, multimodal parts, exact tool argument strings, encryption and metadata. Raw HTTP execution also bypasses the SDK's higher-level activity/null-attribution preparation.
Add two private pure value functions.
ownTranscriptcaptures a detached, recursively frozen protocol transcript.requestMessagescreates an independent mutable request copy, filtering activity and removing only top-level null child attribution. All other observed portable data is retained without schema validation or argument parsing. Existing raw run behavior and public exports are unchanged; session composition and snapshot reconciliation remain separate work.Validation:
This boundary preserves observed SDK data; it cannot recover fields removed by SDK parsing or provider conversion. No public backend/React parity or production performance claim is made. No dependencies, releases or publishing configuration change.