feat(core): support lazy tool search registration#25211
Draft
fcoury-oai wants to merge 1 commit into
Draft
Conversation
This was referenced May 30, 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.
Why
tool_searchneeds a reusable way to surface tools discovered after a turn starts and dispatch a returned MCP tool immediately. This infrastructure should be reviewable separately from the MCP startup policy that supplies the loaders.What Changed
tool_searchto refresh optional MCP search entries through injected loaders.This layer is dormant until a caller supplies lazy MCP loaders.
Stack
How to Test
Targeted tests:
just test -p codex-core lazy_mcp_searchThe focused run covers same-turn dispatch registration, pending-loader avoidance when existing results match, ready-tool refresh, normalized-name replacement, and shadow handling.