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
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model. #27548
@uhlhosting bro in windows i tried these codex features disable multi_agent_v2
codex features disable multi_agent in powershell and then in config.toml i changed to this [features]
multi_agent = false
multi_agent_v2 = false.
@uhlhosting bro in windows i tried these codex features disable multi_agent_v2
codex features disable multi_agent in powershell and then in config.toml i changed to this [features]
multi_agent = false
multi_agent_v2 = false.
Hi will give it a try. For me it works partially. New tasks works. Old one cannot continue still.
Reopen Codex App and start a fresh thread/session.
If an existing thread still fails after disabling it, the config change is not enough for that old thread. Some existing threads persist multi_agent_version = "v2" in rollout history, so resumed old threads can keep sending the encrypted spawn_agent / followup_task tool schema even after the feature is disabled. That persistence case is discussed in #27205.
Separate but related: #26210 also made v2 subagent task/message data unreadable in rollouts, which makes these recovery/debugging cases harder. I opened #28058 for that auditability issue, please react if this affects you.
Activity
github-actions commentedon Jun 11, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
uhlhosting commentedon Jun 11, 2026
Same issue on MacOS. I disable all findings from other posts. It's in a loop! All was working fine on last release this must be a joke!
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
Your workspace is out of credits. Add credits to continue. 0 Ignore this I have full tokens in this session!
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.
m-mahadi commentedon Jun 11, 2026
@uhlhosting bro in windows i tried these codex features disable multi_agent_v2
codex features disable multi_agent in powershell and then in config.toml i changed to this [features]
multi_agent = false
multi_agent_v2 = false.
uhlhosting commentedon Jun 11, 2026
Hi will give it a try. For me it works partially. New tasks works. Old one cannot continue still.
ignatremizov commentedon Jun 13, 2026
This looks like the same issue tracked in #27205 / #27331, originally reported in #26753.
Workaround for Codex App users:
If an existing thread still fails after disabling it, the config change is not enough for that old thread. Some existing threads persist
multi_agent_version = "v2"in rollout history, so resumed old threads can keep sending the encryptedspawn_agent/followup_tasktool schema even after the feature is disabled. That persistence case is discussed in #27205.Separate but related: #26210 also made v2 subagent task/message data unreadable in rollouts, which makes these recovery/debugging cases harder. I opened #28058 for that auditability issue, please react if this affects you.