[Agent][Platform] Shift structured output from Agent to Platform component #802
+625
−409
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
chr-hertel
added
Platform
carsonbot
changed the title
chr-hertel
force-pushed
the
shift-structure-output
branch
from
95bcfbc to
edebf2b
Compare
chr-hertel
force-pushed
the
shift-structure-output
branch
from
edebf2b to
14158cb
Compare
|
Rebase needed, but from what I can see 👍 |
chr-hertel
force-pushed
the
shift-structure-output
branch
from
14158cb to
8110d13
Compare
OskarStark
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 main differentiator between the Agent and the Platform component is that the Agent is designed for multi-step model interaction and this is not the case for structured output. In the beginning the feature was also a bit more heavy than the light platform, since it was using the Serializer, and the Platform not having extension points for it.
Nowadays the Platform uses the Serializer anyways for the contract handling, and relies on a optional EventDispatcher, that now also can provide the needed extension points.
Secondary goals where to introduce a
ResultEventand bring back user-land validation for structured output capability of model.Fixes #791, replaces #794