If state is empty on run_finished event, don't trigger a state update #345
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
maxkorp
requested review from
mme,
ranst91,
ataibarkai,
tylerslaton and
NathanTarbert
as code owners
mattsp1290
pushed a commit
to mattsp1290/ag-ui
that referenced
this pull request
Sep 8, 2025
…ag-ui-protocol#345) * If state is empty on run_finished event, don't trigger a state update * update test
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.
When a RUN_FINISHED event comes in, we convert it to a legacy AgentStateMessage, even if state is empty (I'm not convinced that it is ever not empty). This causes things like pedantic's integration to fail when a user sends a message that does not affect state, since the integration doesn't send anything back.