tools: infer code-mode namespace descriptions from specs#22406
Merged
pakrym-oai merged 1 commit intoMay 13, 2026
Conversation
sayan-oai
approved these changes
May 13, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Code mode already builds the merged nested
ToolSpecs that feed theexecprompt. Keeping a separatetool_namespacesmap in the planning path duplicated that metadata and left extra wrapper plumbing inspec.rs.What changed
ToolSpec::Namespaceentries before building the code-mode handlersbuild_code_mode_handlers(...)so the code-mode-specific planning stays in one placetool_namespacesfromToolRegistryBuildParamsMcpToolPlanInputswrapper and related test helper plumbingTesting
cargo test -p codex-core spec_plan