Namespace multi-agent v2 tools under collaboration - #29067
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f6d5c11afd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d7ab71fbf3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
30d146a to
0f8faee
Compare
# Conflicts: # codex-rs/core/tests/suite/model_runtime_selectors.rs # codex-rs/core/tests/suite/rollout_budget.rs
Summary
Multi-agent v2 tools now use the fixed
collaborationnamespace when namespace tools are available. This keeps the model-visible hint and the actual tool surface aligned aroundfunctions.collaboration.*, without exposing an unshipped namespace knob to users.The PR also removes the old
features.multi_agent_v2.tool_namespaceconfig/schema surface, updates the MAv2 test fixtures for namespaced calls, and fixes staleTurnContext.featuresreferences that were breakingcodex-corebuilds.Changes
collaborationinstead of relying on a configurable namespace.tool_namespacefrom MAv2 TOML config, resolved config, validation, schema, and tests.TurnContext.config.featuresin the multi-agent mode context paths.Testing
just write-config-schemajust test -p codex-features