fix: enum values in input schema#1422
Merged
cotovanu-cristian merged 1 commit intomainfrom Mar 6, 2026
Merged
Conversation
gcuip
approved these changes
Mar 6, 2026
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
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.
Summary
This PR fixes prompt interpolation for enum-backed input fields so the LLM receives the actual enum value instead of the enum member name. In the failing case, risk_tolerance=low was being rendered as DynamicEnum.KEY_0, which
changed the prompt semantics and led to invalid model behavior.
Changes
Why
Agent prompts must reflect the validated input payload exactly. Passing enum member names instead of their values breaks downstream reasoning and can cause the model to branch incorrectly.