[cherry-pick] Disable semantic_search on BYOK/custom endpoints#323610
Merged
Conversation
vs-code-engineering
Bot
added
the
cherry-pick-artifact
bhavyaus
approved these changes
Jun 29, 2026
dmitrivMS
approved these changes
Jun 29, 2026
vritant24
approved these changes
Jun 29, 2026
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.
Cherry-pick of #323605 from
main.Fixes #322525
Problem
When using a BYOK / custom (non‑CAPI) endpoint — e.g. a local
llama.cppmodel — and the GitHub Authentication Provider extension is disabled (--disable-extension vscode.github-authentication), invoking thesemantic_searchtool aborts the whole chat turn:Fix
Gate
semantic_search(ToolName.Codebase) off for non‑CAPI endpoints, alongside the specialized subagents that are already restricted to CAPI ingetAgentTools. Because this is applied through thegetEnabledToolsfilter callback, it takes precedence over a manual tool‑picker enablement (the exact repro in the issue), so the tool is never offered when it can't work.