
OpenAI Codex Subagents: Run Parallel Multi-Agent Workflows
A practical guide to spawning and coordinating parallel Codex subagents, from TOML custom agents to the Responses API multi-agent beta.

A practical guide to spawning and coordinating parallel Codex subagents, from TOML custom agents to the Responses API multi-agent beta.

OpenAI Codex declares custom agents in TOML, SKILL.md and AGENTS.md use Markdown, Conductor uses YAML, and A2A skips manifests entirely. The right choice depends on whether you need enforceability, readability, or interoperability.

Cumora is team chat rebuilt so agents hold the same roster, DMs, and calendars as humans, not a chatbot bolted on top.

The real gap in multi-agent systems isn’t discovery; it’s deciding who keeps working after execution has already begun.

OpenBot treats agent compute as a governance boundary: one container, one browser, and a fail-closed policy gate in front of every action.

AI coding agents burn tokens invisibly; cost regression gates turn that waste into a failing build signal you can act on.

Stop handing agents long-lived secrets; govern credential use the moment each agent acts, not at rest.

A production engineer’s guide to when parallel token generation beats autoregressive decoding for latency-sensitive agent workloads.

The hard part of federated MCP isn’t plumbing between servers; it’s deciding who can invoke what across a boundary no single party controls.

When an agent fails, you need to know why it chose a particular reasoning path — not just what API calls it made. Here is how the tooling is evolving to close that gap.