›_ Codex Issues
Codex Issues / #27665

not able to use codex app in macos from last 4 days i am not able to use my codex help me out

Open 💬 2 comments Opened Jun 11, 2026 by rajsundesha
💡 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)?

latest version

What subscription do you have?

max 20x

What platform is your computer?

mac m1 max

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?

in all possible way even if i say hi or do anything in any chat or in any session it is occuring in my m1 max studio

What is the expected behavior?

<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/66cdb038-2f19-4b32-911b-8278bab6a6c4" />

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #27622
  • #27548
  • #27589
  • #27331
  • #27260

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.