Fix Anthropic native structured output rejecting min/max and other JSON Schema constraints#718
Open
sulimanbenhalim wants to merge 1 commit into
Conversation
…onstraints unsupported by output_config
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.
Fixes #715
When an agent's
schema()uses Laravel's JsonSchema builder methods like->min()or->max(), Anthropic native structured output returns a 400. Itsoutput_config.format.schemaonly accepts a subset of JSON Schema, sominimum,maximum,minLength,maxLength,maxItems,multipleOfanduniqueItemsget rejected before the model even runs. The same schema works on OpenAI.The constraints reach the API unfiltered because
ObjectSchema::toSchema()only disablesadditionalPropertiesand Illuminate's Serializer keeps everything else.This adds
AnthropicSchemaSanitizer, which strips the unsupported keywords on the native path and folds each one into the node's description so the model still honors it, the same transform Anthropic's own Python, TS, Ruby and PHP SDKs do:minItems> 1 is clamped to 1 (Anthropic allows only 0 or 1),patternis left alone since simple patterns are supported, and the synthetic-tool fallback isn't touched since toolinput_schematakes these as hints.Tests cover every stripped keyword plus an integration test checking the constraints are gone from the request body.