Repository navigation
Conversation
This branch has not been deployed
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.
When an MCP tool is registered as
echo_mcp_my-server, Bash exposes it asecho_mcp_my_server. The script can use the Bash name, but the SDK rejects that same name intool_manifestbefore making the request.The Bash runner now accepts an unambiguous normalized alias and resolves it to the registered name before applying caller policy. Exact names still take precedence. Direct-only tools remain blocked, ambiguous aliases are rejected, and the sandbox and replay still receive the registered name.
Addresses the Bash path in LibreChat-AI/LibreChat#18211. LibreChat will pick up the fix after an SDK release and dependency update.
Verification: the new cases reproduced the rejection on
main; all 245 focused Jest tests passed with the fix. TypeScript and ESLint passed. The tests cover the SDK-to-Code-API request boundary without a live sandbox. AI assistance was used for implementation and testing.