Codex cli can no longer spawn subagents with specific models or reasoning

apparently there is a new version of the subagents call version 2, I had to dig into the code with codex ti figure it out. That said, it doesn’t work the same… you can choose model and effort. However, the agents are completely behind the scenes. /agents doesn’t work with them any longer, I had codex give me a summary of the change for my plugins:

Yes—the change was for Codex MultiAgent V2. The central issue was that the old spawn pattern could appear to select a GPT‑5.6 child while actually inheriting the parent’s model and effort.

What changed:

The required configuration became:

“[features.multi_agent_v2]”

hide_spawn_agent_metadata = false tool_namespace = “agents”

The resulting dispatch flow is:

permission-appropriate parent → fresh spawn with agent_type + bounded fork → verify role/model/effort/permission in turn_context → accept the result or respawn

We standardized GPT‑5.6 into five managed execution profiles:

• review_max: gpt-5.6-sol / max
• review_high: gpt-5.6-sol / high
• test_medium: gpt-5.6-terra / medium
• scan_low: gpt-5.6-luna / low
• monitor_low: gpt-5.6-luna / low

For generic children, we now pass both model and reasoning_effort; specifying only the model does not establish the compute budget. We also avoid resumed children for budget-sensitive work because they can adopt the coordinator’s current model and effort.

The permission limitation was important: reviewer/scanner profiles must run beneath a read-only parent, while test_medium runs beneath a workspace-write parent. The child TOML cannot safely narrow a more powerful parent.

This also produced the operating policy now in your guidance: use Luna for bounded auxiliary work, Terra for ordinary implementation, and Sol only for consequential or unusually difficult judgment. Settings remain “requested” until runtime evidence proves them.

The change landed in PR #26, commit e27c6f9, and is documented in the docs/work-sessions/2026-07-11-verified-workflows-v2- bootstrap.md and plugins/verified-workflows/README.md.

Separately, outcome.dispatch.v2 is the launch-acknowledgement protocol. It is related modernization work, but it is not the mechanism that enabled GPT‑5.6 profile selection.

repo: infiquetra/infiquetra-codex-plugins