OpenAI Codex adds subagents for parallel tasks in app and CLI

• OpenAI's launch post says Codex can now spawn subagents natively, letting a main agent delegate specialized work while keeping the primary thread cleaner.
• The rollout is live for all developers in both the Codex app and Codex CLI, according to the docs link post and a product screenshot.
• OpenAI and early users are framing the feature around parallel execution: Codex can explore “different parts of a task in parallel,” while each subagent gets its own isolated thread and returns results to the orchestrator launch post workflow summary.
• Early examples point to larger review and implementation jobs rather than one-shot prompts; one user had Codex launch six parallel review passes, then “aggregate findings by category” before producing a checked summary CLI walkthrough.

OpenAI added native subagents to Codex in both the app and CLI. In the company’s announcement, the pitch is straightforward: spin up specialized agents to “keep your main context window clean,” handle multiple parts of a task at once, and steer agents independently as work changes. The linked subagents docs position this as a first-class Codex workflow rather than a prompt hack.

The rollout appears broad from day one. OpenAI’s follow-up post says subagents are “available for all developers,” and the product screenshot shows the feature surfaced directly inside the Codex interface with a “Subagents in Codex” prompt and a warning that it “may increase token usage.” That makes the tradeoff explicit: better task decomposition, but potentially higher consumption.

The practical model is an orchestrator-plus-workers pattern. The documentation screenshot says Codex can spawn specialized agents in parallel and then collect their results into one response, which is most useful for “complex tasks that are highly parallel,” including codebase exploration and multi-step feature work. It also says developers can define custom agents with different instructions and model configurations.

A more implementation-focused summary from an early explainer describes each subagent as running in its own isolated thread, with the main agent handling spawning, follow-up routing, and result collection. That separation matters for long sessions: instead of stuffing exploration, implementation, and verification into one context window, Codex can split them across threads and collapse the outputs back into the parent session.

The clearest early workflow is parallel code review. In one CLI example, a user asked Codex to spawn one agent per review category: security, code quality, bugs, race conditions, test flakiness, and maintainability. The terminal output shows Codex starting six explorer agents, waiting for them, closing them, and then “spot-checking the highest-severity findings locally” before producing a final summary.

That example also shows the limits of the environment rather than the agent plan itself. A GitHub CLI call failed with “HTTP 401: Bad credentials,” but the orchestrator still proceeded with repository analysis and summarized the blocked step separately CLI walkthrough. Another early user summary says Codex now “orchestrates agents, spawns subagents, routes follow-ups, awaits results, and closes threads,” which matches the behavior in the terminal logs CLI walkthrough.

OpenAI staff and users are already pointing to broader patterns. One staff post says they’ve seen “awesome new and creative workflows,” while another user note highlights pairing subagents with faster modes like Spark on Pro. The immediate engineering story is less about autonomous coding in one giant run and more about giving Codex a built-in way to decompose parallel work without polluting the main thread.