# OpenAI publishes Symphony specification for issue-driven Codex orchestration > The open-source specification maps issue-tracker work to isolated Codex agents, with explicit concurrency, retries, state, and human review. Canonical URL: https://www.devobs.io/news/news-openai-symphony-codex-orchestration-spec/ By: Lena Fischer Published: 2026-09-06T11:58:54.619Z Updated: 2026-09-06T11:58:54.619Z Event date: 2026-04-27 Section: Developer tools OpenAI published [Symphony](https://openai.com/index/open-source-codex-orchestration-symphony/) on April 27, describing a language-agnostic specification for running coding agents from an issue tracker. The reference workflow treats a project board as a control plane: eligible issues receive isolated workspaces, agents run with bounded concurrency, and tracker state determines dispatch, cancellation, retry, and handoff. OpenAI released the design as a specification rather than a packaged platform, leaving teams to choose their runtime, approval policy, and tracker integration. ## The useful artifact is the operating contract Symphony makes several assumptions explicit that are easy to miss in a prototype. Workspaces must have deterministic identities and survive retries. The orchestrator needs one authoritative in-memory view of active work, plus reconciliation after restarts. Repository-owned workflow instructions define what an agent can do and what evidence it must return. A successful run may stop at human review rather than mark the issue complete. That separation is the announcement’s most reusable part. The issue tracker expresses intent and dependencies; the orchestrator schedules; the coding agent performs tracker and code changes with its own tools. Teams can replace Linear or the reference runtime while retaining the lifecycle contract. ## What engineering teams should check Before adopting the pattern, define cancellation semantics when an issue changes state, limits for concurrent work, retry backoff, workspace cleanup, and the exact evidence required for review. Treat the workflow file as production configuration: version it, test parsing and defaults, and make secrets indirect. The specification does not prescribe a universal sandbox or approval posture. That is a deliberate integration boundary, but it also means implementers remain responsible for threat modeling agent credentials, network access, destructive commands, and tracker writes. Start with a narrow issue class and measure abandonment, retry, and review outcomes before widening automation. ## Source references -