Codex CLI 0.144.1 silently ignores custom subagent profiles

I’m using Codex CLI 0.144.1 for sustained repository work because long Codex.app sessions have repeatedly become bloated or  locked.

I configured five valid project-scoped profiles under .codex/agents/, covering Terra and Luna models with low-to-high reasoning.  Codex accepted the profiles and spawned agents bearing their requested names, making profile selection appear successful.

It did not work. Persisted rollout records under ~/.codex/sessions/ showed in all five instances that gpt-5.6-sol, high (the orchestrator) was selected.

The requested profile name therefore appears to label the child thread without selecting its configured model and reasoning effort.

This is difficult to detect without examining persisted turn_context records. I found it looking at Tokscale where I noticed that I only saw 5.6 sol. We should be able to assign work to cheaper, lower-effort agents. In this  five-agent canary, every supposedly mixed-cost worker ran as Sol High.

At minimum, Codex should fail closed when it cannot select the requested profile. Silent substitution defeats governance and  cost/compute controls without informed user consent.