explaingit

openai/symphony

📈 Trending24,138ElixirAudience · developerComplexity · 4/5ActiveLicenseSetup · hard

TLDR

AI agents autonomously pick up coding tasks from your project board, implement them, and provide proof of work, freeing engineers from micromanaging each agent session.

Mindmap

mindmap
  root((Symphony))
    What it does
      Monitor task boards
      Spawn AI agents
      Merge approved code
    How it works
      Pick up work items
      Run agents independently
      Provide proof of work
    Proof of work
      Test results
      Code review feedback
      Complexity analysis
    Use cases
      Automate routine tasks
      Scale coding capacity
      Reduce supervision overhead
    Tech stack
      Elixir reference
      Language agnostic
      Specification provided

Things people build with this

USE CASE 1

Automatically assign and complete coding tasks from your project board without manual agent supervision.

USE CASE 2

Scale your team's output by running multiple AI agents in parallel on independent work items.

USE CASE 3

Review agent work with built-in proof (test results, code analysis, recordings) before merging to main.

Tech stack

ElixirAI agentsLinearCI/CD

Getting it running

Difficulty · hard Time to first run · 1day+

Requires Elixir runtime, Linear API credentials, CI/CD pipeline configuration, and AI agent orchestration setup with multiple external service integrations.

Use freely for any purpose, including commercial use, as long as you include the copyright notice and license text.

In plain English

Symphony is a tool that lets software teams delegate coding tasks to AI agents instead of micromanaging them step by step. The core idea is to shift engineers from "supervising" a coding agent to simply "managing work", you describe what needs to be done, Symphony spins up isolated agent runs to handle each task, and the agents take care of the actual implementation. Here is how it works in practice: Symphony can monitor a project management board (the demo shows it watching a task board called Linear), automatically pick up work items, and spawn separate AI coding agents to tackle each one independently. The agents don't just write code, they provide "proof of work" when they finish: things like automated test (CI) status, code review feedback, complexity analysis, and even walkthrough recordings. Once a task is approved, Symphony handles merging the code safely. You would reach for Symphony if your engineering team already uses AI coding tools and wants to stop babysitting each individual session. Instead of staying in the loop for every decision, you set the work queue and review the results. It is described as an "engineering preview," meaning it is early-stage and suited to trusted internal environments rather than public production use. The reference implementation is written in Elixir, but the project also provides a specification document so you can build your own version in any language using your preferred coding agent. It is released under the Apache 2.0 open-source license.

Copy-paste prompts

Prompt 1
How do I set up Symphony to monitor my Linear board and spawn AI agents for each task?
Prompt 2
What does 'proof of work' mean in Symphony, and how do I configure what evidence agents must provide?
Prompt 3
Can I build my own Symphony implementation in Python instead of Elixir? What does the specification cover?
Prompt 4
How does Symphony handle code merging safely after an agent completes a task?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.