OpenAI Symphony ships Elixir reference stack

The real news here is not just another coding-agent wrapper — it is OpenAI hinting that autonomous software work needs reliable process supervision, not just better prompts. Choosing Elixir/OTP for the reference build makes Symphony feel like infrastructure for long-running agent operations rather than a flashy demo.

• –Symphony reframes agentic coding from interactive pair programming into queue-based work execution, with humans managing issues instead of babysitting sessions
• –The Elixir/OTP choice fits the product’s needs unusually well: supervising long-lived workers, cleaning up failed runs, and handling many concurrent tasks
• –OpenAI is explicit that this is prototype software and recommends teams build their own hardened version from the spec, which makes the repo more architectural blueprint than polished product
• –The current workflow is tightly opinionated around Linear and Codex app-server, so adoption depends on how much a team already buys into OpenAI’s tooling stack
• –Because the repo ships under Apache 2.0 with a public SPEC.md, it also invites alternative implementations in other languages, which could matter more than the reference build itself