You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Subagent Custom Agent Model/Reasoning Config Not being Respected #14671
What terminal emulator and version are you using (if applicable)?
ghostty
What issue are you seeing?
I am testing custom subagent roles, and according to the rust logs, its not using the model I configured. I tested in 0.115.0 alpha as well and it also doesn't work.
So if you set model to 5.3 spark, or 5.1 mini, instead of running that model from that agent.toml files, it will just inherit the parent's model (5.3 in this case).
Rust log confirmed that my Spark and Mini agents both ran with GPT 5.3 Medium (the current model I was using) despite having them configured.
spark.toml
model = "gpt-5.3-codex-spark"
model_reasoning_effort = "high"
The custom agent roles are available and callable in Codex, so they are configured correctly as far as I'm aware, and Codex will call them, but the model is overridden.
@jif-oai tagging because I know you are the one who created this feature. tysm
try create it on agents folder and agent-profile, currently on my workflow , the subagent using the correct model as given to them, if you want to see , you can check my repo about codex_skills i do
@jif-oai tagging because I know you are the one who created this feature. tysm
try create it on agents folder and agent-profile, currently on my workflow , the subagent using the correct model as given to them, if you want to see , you can check my repo about codex_skills i do
they are in the agents folder with an agent profile. you should check the rust logs to make sure. they used to work, but now they are not using the appropriate model.
@jif-oai tagging because I know you are the one who created this feature. tysm
try create it on agents folder and agent-profile, currently on my workflow , the subagent using the correct model as given to them, if you want to see , you can check my repo about codex_skills i do
they are in the agents folder with an agent profile. you should check the rust logs to make sure. they used to work, but now they are not using the appropriate model.
as tested on my end , it work very well, i try using spark model for memory update, working okay , using another model also can work okay, i dont have this issue on my end after add it on agents folder and agent profile , make sure on config.toml you add the route for it. example :
We run 9 agents with GPT, Opus, Gemini and lower grade models like Kimi and Qwen with per-agent model configuration via OpenClaw. Getting model assignment right for subagents is essential for cost and capability matching.
In our setup, each agent has its own config file that specifies its model, and the gateway respects that regardless of what the orchestrator uses. The key design decision was: model selection is an agent property, not inherited from the parent.
If this is a Codex-specific inheritance bug, the fix should ensure that agent role configs (like spark.toml) take precedence over the spawning context. Model choice is usually intentional. You pick a lighter model for routine tasks and a heavier one for complex reasoning. Having the parent override that defeats the purpose.
We run 9 agents with GPT, Opus, Gemini and lower grade models like Kimi and Qwen with per-agent model configuration via OpenClaw. Getting model assignment right for subagents is essential for cost and capability matching.
In our setup, each agent has its own config file that specifies its model, and the gateway respects that regardless of what the orchestrator uses. The key design decision was: model selection is an agent property, not inherited from the parent.
If this is a Codex-specific inheritance bug, the fix should ensure that agent role configs (like spark.toml) take precedence over the spawning context. Model choice is usually intentional. You pick a lighter model for routine tasks and a heavier one for complex reasoning. Having the parent override that defeats the purpose.
Yeah so this used to work just fine. But in one of the recent updates, it broke, so the agents launch but they just inherit instead of override.
I tried on my side and everything is working as expected... @am-will can you send me your full config.toml, the agent file and confirm the command you use to start Codex?
Activity
github-actions commentedon Mar 14, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
am-will commentedon Mar 14, 2026
@jif-oai tagging because I know you are the one who created this feature. tysm
UntaDotMy commentedon Mar 14, 2026
try create it on agents folder and agent-profile, currently on my workflow , the subagent using the correct model as given to them, if you want to see , you can check my repo about codex_skills i do
am-will commentedon Mar 14, 2026
they are in the agents folder with an agent profile. you should check the rust logs to make sure. they used to work, but now they are not using the appropriate model.
UntaDotMy commentedon Mar 14, 2026
as tested on my end , it work very well, i try using spark model for memory update, working okay , using another model also can work okay, i dont have this issue on my end after add it on agents folder and agent profile , make sure on config.toml you add the route for it. example :
[agents.git-expert]
description = "Analysis-first Git workflow and state-safe collaboration guidance"
config_file = "agents/git-expert.toml"
am-will commentedon Mar 14, 2026
i can assure you the file is correct. the agents work. they just dont respect the model and reasoning level.
ThinkOffApp commentedon Mar 14, 2026
We run 9 agents with GPT, Opus, Gemini and lower grade models like Kimi and Qwen with per-agent model configuration via OpenClaw. Getting model assignment right for subagents is essential for cost and capability matching.
In our setup, each agent has its own config file that specifies its model, and the gateway respects that regardless of what the orchestrator uses. The key design decision was: model selection is an agent property, not inherited from the parent.
If this is a Codex-specific inheritance bug, the fix should ensure that agent role configs (like
spark.toml) take precedence over the spawning context. Model choice is usually intentional. You pick a lighter model for routine tasks and a heavier one for complex reasoning. Having the parent override that defeats the purpose.am-will commentedon Mar 14, 2026
Yeah so this used to work just fine. But in one of the recent updates, it broke, so the agents launch but they just inherit instead of override.
Config is correct.
am-will commentedon Mar 16, 2026
In fact, Spark doesn't work at all in the new 115 update you will want to fix this before launching it live.
jif-oai commentedon Mar 16, 2026
I was OOO, sorry for the delay. I saw some PRs were pushed here. I'll take a look and fix all the issues
jif-oai commentedon Mar 16, 2026
I tried on my side and everything is working as expected...
@am-will can you send me your full
config.toml, the agent file and confirm the command you use to start Codex?5 remaining items
fix: sub-agent role when using profiles (#14807)
Merge upstream/main into fork main (#9)
sync: merge upstream main (#464)
Sync upstream: automated sync (phenotype/upstream-sync-20260324) (#487)
fix: sub-agent role when using profiles (#14807)
fix: sub-agent role when using profiles (openai#14807)
fix: sub-agent role when using profiles (#14807)