Codex no usable and all the threads are down with this error Invalid Value: 'tools'. Function 'functions.spawn_agent' declares encrypted parameters but is not configured for encrypted tool use by this model.

Resolved 💬 3 comments Opened Jun 11, 2026 by teazle Closed Aug 6, 2026
💡 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 Jun 9, 2026

What subscription do you have?

pro

What platform is your computer?

macos

What issue are you seeing?

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

What steps can reproduce the bug?

Feedback ID: no-active-thread-019eb75f-e979-7393-8077-6d9527601d45

just update the app...all the chat is not working

What is the expected behavior?

can use codex normally and chat and work

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #27548
  • #27260
  • #27331
  • #26753
  • #27589

Powered by Codex Action

ignatremizov · 2 months ago

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

Workaround for Codex App users:

  1. Quit Codex App completely.
  2. Edit your Codex config:
# macOS/Linux: ~/.codex/config.toml
# Windows: %USERPROFILE%\.codex\config.toml
[features.multi_agent_v2]
enabled = false
  1. 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.

teazle · 2 months ago

Can I ask for compensation ? I missed like 3 days of usage because of this

Vincent Yap

"See big, Think smart, Have Human-sense"
Singapore | Indonesia | Philippines

Disclaimer: The information in this email and any attachments may contain
proprietary and confidential information that is intended for the
addressee(s) only. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution, retention or use of
the contents of this information is prohibited. When addressed to our
clients or vendors, any information contained in this e-mail or any
attachments is subject to the terms and conditions of any governing
contract. If you have received this e-mail in error, please immediately
contact the sender and delete the email.

On Sat, 13 Jun 2026, 16:38 Ignat Remizov, @.***> wrote:

ignatremizov left a comment (openai/codex#27622) <https://github.com/openai/codex/issues/27622#issuecomment-4698016901> This looks like the same issue tracked in #27205 <https://github.com/openai/codex/issues/27205> / #27331 <https://github.com/openai/codex/issues/27331>, originally reported in #26753 <https://github.com/openai/codex/issues/26753>. Immediate workaround for new sessions: # ~/.codex/config.toml [features.multi_agent_v2]enabled = false or run Codex with: codex --disable multi_agent_v2# or for exec: codex exec --disable multi_agent_v2 ... For custom Responses providers, the same underlying problem applies: the active backend/model has to support encrypted tool use before Codex can expose the v2 spawn_agent / followup_task schemas. If you still see the error after disabling it, start a fresh thread/session. Some existing threads appear to 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 <https://github.com/openai/codex/issues/27205>. Separate but related: #26210 <https://github.com/openai/codex/pull/26210> also made v2 subagent task/message data unreadable in rollouts, which makes these recovery/debugging cases harder. I opened #28058 <https://github.com/openai/codex/issues/28058> for that auditability issue. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/27622?email_source=notifications&email_token=ACJTWRHQ5SUQ75IN6NUXZLL47UHGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRZHAYDCNRZGAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4698016901>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJTWRGGB4MAXBS43S2EEJL47UHGRAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TINRUGIYDSOBSGEYKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ACJTWRAQXNBIHJ6WBQBKJR347UHGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRZHAYDCNRZGAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/ACJTWRCHZMYE3G66Q6XKD3T47UHGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRZHAYDCNRZGAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>