Codex now supports subagents, allowing you to spawn specialized, parallel AI workers for complex coding tasks. By defining custom TOML agents with isolated roles (like explorers and reviewers), you can execute multi-step workflows without context rot.
Codex just leveled up with Subagents — you can now spawn specialized parallel agents for complex tasks like PR review or multi-step features. Each subagent gets its own instructions, model, and tools, and Codex merges everything back cleanly.
Over the last week I used Codex to design, debug, and do embedded work for a new device prototype, and the speed honestly shocked me. This feature makes that whole experience feel even more serious. Now I can have one agent map, one review, and one check docs, and the main thread stays much cleaner instead of drowning in logs and side quests.
It really feels like OpenAI is going all in on the coding lane right now. This puts some real pressure on @Claude Code. And Goolgle, @Google Antigravity alone probably is not enough :)
Report
Spawning specialized parallel agents for complex coding tasks is the right evolution for Codex — splitting a large problem into concurrent subagents that each handle a focused piece mirrors how experienced engineering teams actually decompose work, and doing it in parallel rather than sequentially should dramatically cut time-to-completion on multi-file refactors and complex feature builds. How do subagents coordinate when their changes overlap — is there a central orchestrator that detects conflicting edits across parallel workers, or do they operate on isolated branches that get merged at the end?
Replies
Flowtica Scribe
Hi everyone!
Codex just leveled up with Subagents — you can now spawn specialized parallel agents for complex tasks like PR review or multi-step features. Each subagent gets its own instructions, model, and tools, and Codex merges everything back cleanly.
Over the last week I used Codex to design, debug, and do embedded work for a new device prototype, and the speed honestly shocked me. This feature makes that whole experience feel even more serious. Now I can have one agent map, one review, and one check docs, and the main thread stays much cleaner instead of drowning in logs and side quests.
It really feels like OpenAI is going all in on the coding lane right now. This puts some real pressure on @Claude Code. And Goolgle, @Google Antigravity alone probably is not enough :)
Spawning specialized parallel agents for complex coding tasks is the right evolution for Codex — splitting a large problem into concurrent subagents that each handle a focused piece mirrors how experienced engineering teams actually decompose work, and doing it in parallel rather than sequentially should dramatically cut time-to-completion on multi-file refactors and complex feature builds. How do subagents coordinate when their changes overlap — is there a central orchestrator that detects conflicting edits across parallel workers, or do they operate on isolated branches that get merged at the end?
The concept looks solid.
What was the hardest part of building it?