[codex] Support search schema on all search types#157
Merged
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
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.
What changed
This updates the JavaScript SDK search surface so
systemPromptandoutputSchemaare supported across all search types, addsdeep-liteas a deep search variant, and documents thatoutputis returned whenoutputSchemais provided.Why
The search API now supports these parameters across every search type instead of only deep and deep-reasoning, and it adds
deep-litealongside the existing deep variants.Impact
JavaScript SDK consumers can now pass
systemPromptandoutputSchemaon non-deep searches, usedeep-lite, and rely on the documentedoutputfield when structured output is requested.Validation
npx vitest run test/unit/search.test.tsnpm run buildnpm run typecheckstill has unrelated pre-existing repo errors outside this changed surface