docs: document file search result limits#1981
Open
HAYDEN-OAI wants to merge 1 commit into
Open
Conversation
1 task
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
max_num_resultstools[].file_search.max_num_resultsfile_searchand cannot carry tool configurationWhy
Issue #1004 reports conflicting guidance about where
max_num_resultsbelongs. The generated Assistants types already expose the correct run-level shape, but the hand-maintained helper guide did not show it or contrast it with the invalid attachment placement.Impact
Existing Assistants users now have a copyable example for limiting file search results without changing the generated API surface or runtime behavior.
Validation
pnpm run formatpnpm run lintResolves #1004