Repository navigation
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.
Python: Add tool name prefixes to FileAccessProvider #9654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Python: Add tool name prefixes to FileAccessProvider #9654
Changes from all commits
5e1d6a7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tool_name_prefixis stored verbatim, so whitespace,/, Unicode, or a long prefix can produce function names that violate provider identifier or 64-character limits. Core accepts these names and adapters forward them, causing a remote request failure instead of a usable provider. Validate or normalize the prefix, including the final generated-name length, when constructing the provider.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a provider is prefixed, this frees the canonical
file_access_*names while the public static auto-approval rules still approve those names. An approval-required local tool registered asfile_access_writecan now coexist and will be auto-approved, bypassing the human gate; meanwhile the real prefixed file tool is not matched. Make the approval rules provider/prefix-bound and match only that provider's effective names, so renaming also removes authority from the old names.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a prefix is set, this renames the registered tools but
instructionsremainsDEFAULT_FILE_ACCESS_INSTRUCTIONS, which tells the model to call unprefixedfile_access_*names. In the supported prefixed-plus-default setup, those directions select the default provider, so requests intended for the prefixed store can read or modify the wrong store; with only prefixed providers they name nonexistent tools. Render the injected instructions and cross-tool references from each provider's effective names.Uh oh!
There was an error while loading. Please reload this page.