Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.

Open 💬 5 comments Opened Jun 11, 2026 by m-mahadi

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.608.12217 • Released 9 Jun 2026

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

No matter what i prompt, i get this error. invalid value: tools. i even uninstalled and reinstalled codex. same bug persists.

What steps can reproduce the bug?

Feedback ID: 019eb543-d235-7fa1-ad17-a72449d06341

You don't need to do anything. Any prompt gives this error.

What is the expected behavior?

Well expected behavior is how it should normally behave no.

Additional information

Please fix quickly. I am on an important work with deadline and I can't afford another sub rn.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#27331
#27260
#26753
#27205

Powered by Codex Action

uhlhosting · 2 months ago

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.

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.

m-mahadi · 2 months ago

@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 · 2 months ago

@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.

ignatremizov · 2 months ago

This looks like the same issue tracked in #27205 / #27331, originally reported in #26753.

Workaround for Codex App users:

Quit Codex App completely.
Edit your Codex config:

# macOS/Linux: ~/.codex/config.toml
# Windows: %USERPROFILE%\.codex\config.toml
[features.multi_agent_v2]
enabled = false

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.