ag-ui-protocol / ag-ui-protocol/ag-ui
[Feature]: AG-UI protocol should be extensible
Open
enhancement
- Dominant language
- Python
- Stars
- 15.9k
- Forks
- 1.4k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 163
Description
### Pre-flight Checklist
- [x] I have searched existing issues and this hasn't been requested yet.
### Problem or Motivation
If servers add extra data to AG-UI events, the Zod schema should not filter it.
In my case AssistantMessages (and other messages) to have a timestamp for display in the UI.
### Proposed Solution
It should use a passthrough rather than strip policy, to allow applications to layer on additional semantics onto the messages.
### Alternatives Considered
All sorts of hacks.
### Additional Context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.