Symphony turns project work into isolated, autonomous implementation runs, allowing teams to manage work instead of supervising coding agents.

In this demo video, Symphony monitors a Linear board for work and spawns agents to handle the tasks. The agents complete the tasks and provide proof of work: CI status, PR review feedback, complexity analysis, and walkthrough videos. When accepted, the agents land the PR safely. Engineers do not need to supervise Codex; they can manage the work at a higher level.

The experimental Elixir implementation currently supports:

• Codex, Claude Code, and OpenCode as unattended agent backends.
• Multi-project routing from one Symphony instance across multiple repos.
• Repo-local WORKFLOW.md files with a global symphony.yml runtime config.
• Linear label-based backend switching with labels like codex, claude, and opencode.
• Linear label-based thinking/effort switching with labels like thinking/high and thinking/max.

If you want to try those features, start with elixir/README.md, which now documents backend support, multi-project setup, and label-routing behavior in detail.

Symphony works best in codebases that have adopted harness engineering. Symphony is the next step -- moving from managing coding agents to managing work that needs to get done.

Tell your favorite coding agent to build Symphony in a programming language of your choice:

Implement Symphony according to the following spec: https://github.com/openai/symphony/blob/main/SPEC.md

Check out elixir/README.md for instructions on how to set up your environment and run the Elixir-based Symphony implementation. It includes setup guidance for OpenCode, Claude Code, multi-project routing, and Linear label-based backend and effort switching. You can also ask your favorite coding agent to help with the setup:

Set up Symphony for my repository based on https://github.com/openai/symphony/blob/main/elixir/README.md

This project is licensed under the Apache License 2.0.