feat: expose multi-agent v2 as model-only tools#22514
Conversation
|
@codex review |
|
Codex Review: Didn't find any major issues. What shall we delve into next? ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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 |
26fbdc1 to
bdb3b1e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdb3b1ea66
ℹ️ 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".
Why
code_mode_onlyfilters code-mode nested tools out of the top-level tool list. For multi-agent v2, we need a rollout shape where the collaboration tools remain callable as normal model tools without also being embedded into the code-modeexectool declaration.Related to this: https://openai-corpws.slack.com/archives/C0AQLHB4U75/p1778660267922549
What Changed
features.multi_agent_v2.non_code_mode_only, including config resolution, profile override handling, and generated schema coverage.ToolExposure::DirectModelOnlyso a tool can be included in the initial model-visible list while staying out of the nested code-mode tool surface.spawn_agent,send_message,followup_task,wait_agent,close_agent, andlist_agents.Verification
non_code_mode_only.