OpenAI releases Symphony: an open orchestration standard for Codex agents

OpenAI has released Symphony, an open orchestration specification for Codex that changes the basic model of working with AI agents. Instead of a developer launching an agent by hand for each task, Symphony keeps the agent system permanently active: it watches the task tracker itself and distributes work without human involvement.

The principle is straightforward. An engineer creates a task in GitHub Issues, Jira or any other tracker, and a Codex agent automatically pulls it into its queue. Symphony describes the protocols for this integration: how the tracker becomes a source of commands, how the agent reports progress, and how tasks are prioritized. No manual launch, no switching between interfaces.

The key difference from the familiar approach is the always-on mode. Traditional AI tools work on demand: open, phrase the request, wait, close. Symphony moves the agent system into the background, much like a CI/CD pipeline. The agent works through the task queue on its own while the team focuses on architectural decisions and complex features.

One of the main problems Symphony addresses is context switching. Productivity research has long established that each switch between tasks costs a developer 15 to 30 minutes of recovering context. If routine tasks such as bug fixes, documentation and test coverage can be delegated to agents, with no need to return to them until the result is ready, the overall flow of work becomes steadier and more predictable.

Importantly, Symphony is a specification, not a finished product. It defines protocols and interfaces but does not dictate a specific implementation. Teams build their own connectors for their trackers, configure prioritization logic, and decide which types of tasks go to agents and which stay with people. This gives flexibility and lowers the risk of vendor lock-in.

OpenAI released Symphony under an open license, and a clear strategy lies behind that decision. The company wants not only to sell agent products but also to shape infrastructure standards for the whole industry. Open source works here as a tool for capturing the ecosystem: if Symphony becomes the de facto orchestration standard, the value of Codex as an execution engine rises automatically.

Symphony's arrival reflects the maturing of the agent market. The first wave was about demonstrating what was possible. The second was about concrete products such as Copilot and Codex. Now a third is starting: standards and infrastructure that let teams embed agents into real production processes in a predictable way.

For engineering teams that already have access to Codex and a structured backlog, Symphony opens a concrete opportunity. Agents start clearing routine work in parallel with the main work, without restructuring processes and without new tools layered on top of existing ones.