Symphony

An open-source spec for Codex orchestration

Symphony 介绍

Symphony is an open-source specification from OpenAI that orchestrates Codex agents to automate software development workflows. It connects issue trackers like Linear to coding agents, enabling each task to run autonomously in its own workspace from assignment to pull request. This turns task trackers into always-on systems for agentic work, allowing developers to focus on review and direction.

核心功能

Automates task execution from issue trackers to pull requests
Isolated per-issue workspaces for independent agent execution
Continuous monitoring and assignment of new work without manual triggering
Keeps workflow policy in-repo via WORKFLOW.md for versioned prompts
Minimal orchestration layer designed as a reference implementation

典型使用场景

Engineering teams using issue trackers to automate routine coding tasks
Open-source maintainers delegating bug fixes and feature implementations to AI agents
Startups accelerating development cycles by reducing manual coding effort
Organizations exploring AI-driven software delivery pipelines

为什么适合初创团队

Startups need to move fast with limited resources. Symphony automates routine development tasks, freeing engineers to focus on higher-level work. Its open-source nature allows customization without vendor lock-in, ideal for lean teams.

可替代选择

Harness Engineering, GitHub Actions, Jenkins, Buildkite, AWS CodePipeline

常见问题

What is Symphony?

Symphony is an open-source specification for orchestrating Codex agents via issue trackers like Linear, automating the lifecycle from issue to pull request.

How does Symphony differ from other coding agents?

It provides a structured orchestration layer that works with existing project management tools, enabling continuous autonomous execution.

Is Symphony maintained as a standalone product?

No, it's a reference implementation; OpenAI encourages developers to build their own versions.

What tools does Symphony integrate with?

Currently specified for Linear, but the concept can be extended to other issue trackers.

How does Symphony ensure isolation?

Each task runs in its own isolated workspace with its own context and lifecycle.