Can't spawn any subagents.

Open 💬 4 comments Opened May 28, 2026 by bigboss2063

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

26.519.81530

What subscription do you have?

Plus

What platform is your computer?

Windows

What issue are you seeing?

Codex believes it does not have a spawn_agent tool. I tried the same thing in CLI version 0.130, and the subagent started normally.
<img width="1566" height="588" alt="Image" src="https://github.com/user-attachments/assets/a81e1f34-9a33-4973-ac33-904ab41f1d9f" />

What steps can reproduce the bug?

Just do what I do in 0.134 version.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

mhjiang0408 · 3 months ago

I am also experiencing this same issue in the latest version (0.135.0 codex-cli).
I kindly request the developer team to look into this and investigate the cause of the problem.
You can use the prompt I provided to reproduce the issue:

Review this branch with parallel subagents. Spawn one subagent for security risks, one for test gaps, and one for maintainability. Wait for all three, then summarize the findings by category with

file references.

<img width="1909" height="76" alt="Image" src="https://github.com/user-attachments/assets/a4e4eb4b-9b4b-4ce9-86f1-38e7038faa80" />

Henrywalker2002 · 2 months ago

<img width="1467" height="369" alt="Image" src="https://github.com/user-attachments/assets/b09f6a2b-7c33-4edb-b842-1f137ea26139" />
I also have this trouble ? Anyone has solution ?

bigboss2063 · 2 months ago
<img alt="Image" width="1467" height="369" src="https://private-user-images.githubusercontent.com/46373762/602297075-b09f6a2b-7c33-4edb-b842-1f137ea26139.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODA1MDE4MjAsIm5iZiI6MTc4MDUwMTUyMCwicGF0aCI6Ii80NjM3Mzc2Mi82MDIyOTcwNzUtYjA5ZjZhMmItN2MzMy00ZWRiLWI4NDItMWYxMzdlYTI2MTM5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MDMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjAzVDE1NDUyMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA2ZjI0MzQyN2EyOTkxNWJiMjRjZjNjMTM2ZDE1MWUxMzMwMTI4MmMzODlhMTc4ZWY4NGY2OTU1ZmY1MmUyZGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.5qxvm_torVtZ67Yx_7NNhZkV5SNaf3Sij7WB1o5naKg"> I also have this trouble ? Anyone has solution ?

I rolled back to version 0.130

mhjiang0408 · 2 months ago

I found the solution. Please change "multi_agent = true" to "multi_agent_v2=true" in the config.toml file.
I indeed believe that the OpenAI staff should update their documentation in a timely manner, rather than waiting for developers to read through their source code bit by bit.