fix(ag-ui): enforce owned patch paths and safe data writes - #1165
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
blove
enabled auto-merge (squash)
September 24, 2026 22:54
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.
AG-UI state/activity patches could silently accept nonexistent replacement or copy paths, read inherited JavaScript properties, or read beyond an array's existing elements. Adding
__proto__changed the returned object's prototype instead of creating an own data field.Correct the existing pure path-copy helper: reads, replacements and removals require existing own members; final add keeps array insertion/object creation semantics. Computed own-property writes retain special keys as data. Failed batches leave the original document intact, and the current reducers retain their existing error policies and observations.
Validation:
This corrects path execution rather than adding argument-schema validation. Root removal and broader pointer grammar remain outside the helper's existing supported scope. No public API, dependency, reducer reporting policy or release changes. The optional full built-workspace boundary check was not satisfied because unrelated packages were not built; scoped source-boundary and AG-UI build checks passed.