spawn_agent model allowlist omits gpt-5.6-luna
Codex version
Codex CLI 0.144.6, Codex Desktop on macOS.
What happened
The runtime model catalog exposes gpt-5.6-luna, and the Desktop create_thread / send_message_to_thread schemas also accept it, but the native multi-agent spawn_agent tool rejects the same model:
Unknown model `gpt-5.6-luna` for spawn_agent. Available models: gpt-5.6-sol, gpt-5.6-terra
Reproduction
- Confirm the host catalog:
codex debug models | jq -r '.models[].slug'
Key output includes:
gpt-5.6-sol
gpt-5.6-terra
gpt-5.6-luna
- In a Codex Desktop task with native collaboration enabled, call
spawn_agentwith modelgpt-5.6-lunaand low reasoning. - Observe the allowlist rejection above.
Expected behavior
spawn_agent should accept gpt-5.6-luna when the calling host reports it as available, matching the host model catalog and the other Desktop thread tools. This is useful for low-cost supervision-only sub-agents that mainly execute shell commands, monitor external workers, and summarize progress.
Additional context
gpt-5.6-terra works as a fallback. Using an external codex -m gpt-5.6-luna process is not equivalent because it does not create a native child thread and therefore does not appear in the Codex App Subagents panel.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Still reproducible on Windows with the next stable release.
Environment:
26.715.9868.0CODEX_CLI_PATH:codex-cli 0.145.0multi_agent = truemulti_agent_v2 = trueReproduction request:
The native tool still returns:
The desktop log confirms it is spawning the external 0.145.0 CLI, so this is not caused by the older bundled binary. No child agent is created.
Since this issue is currently closed as completed, could the maintainers please confirm whether Luna is intentionally excluded by the active backend/account catalog, or reopen this if the allowlist fix has not reached 0.145.0?