
Openai Symphony Autonomous Agents
Stand up OpenAI Symphony so tasks from Linear spawn isolated Codex-style runs that open PRs with proof of work instead of babysitting one long agent session.
Overview
OpenAI Symphony Autonomous Agents is an agent skill most often used in Build (also Ship, Operate) that configures Symphony so tracker tasks spawn isolated coding-agent runs with PRs and proof of work instead of live supe
Install
npx skills add https://github.com/aradotso/trending-skills --skill openai-symphony-autonomous-agentsWhat is this skill?
- Monitors Linear (or similar) for tasks and spawns one isolated agent run per task
- Agents implement work, open PRs, and attach proof of work (CI, reviews, walkthrough video)
- Engineers review outcomes instead of supervising live coding sessions
- Supports agent-built Elixir implementation or paste-into-Claude install path
- Pairs with harness-engineering style repos for reliable autonomous landing
Adoption & trust: 1.3k installs on skills.sh; 31 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You spend hours watching a single agent session instead of delegating discrete tracker tasks that land PRs with verifiable CI and review artifacts.
Who is it for?
Small teams with Linear (or compatible trackers), harness-engineered repos, and appetite for autonomous PR workflows.
Skip if: One-off scripts without a work tracker, codebases with no CI or review gates, or builders who only need a single interactive coding chat.
When should I use this skill?
User asks to set up Symphony, run autonomous agents on a project, integrate Linear, spawn isolated agent runs, or configure Symphony Elixir implementation.
What do I get? / Deliverables
Symphony monitors your board, runs isolated agents per task, opens PRs with proof of work, and leaves you reviewing merged outcomes rather than chat transcripts.
- Symphony configuration in the codebase
- Tracker-integrated autonomous PR workflow
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Symphony is introduced when you are building the harness that turns tracker tasks into autonomous implementation runs—the core agent orchestration shelf. agent-tooling fits because the skill configures Symphony, work-tracker polling, and per-task isolated agent runs rather than shipping end-user product UI.
Where it fits
Paste the install prompt so Claude implements the Symphony spec and Elixir config in your repo.
Wire CI proof and PR creation so each Linear task lands a reviewable branch without a watched session.
Tune tracker polling and agent isolation after the first wave of autonomous PRs.
Scale task throughput by adding board columns Symphony monitors while engineers only review outcomes.
How it compares
Orchestration harness for many isolated agent runs—not a replacement for a single IDE copilot session.
Common Questions / FAQ
Who is openai-symphony-autonomous-agents for?
Indie builders and lean teams who want Codex- or Claude-class agents to execute Linear tasks as isolated runs with PRs and proof, aligned with OpenAI Symphony and harness engineering practices.
When should I use openai-symphony-autonomous-agents?
In Build when setting up Symphony in your repo; in Ship when automating PR workflow and proof-of-work collection; in Operate when tuning Elixir config and tracker integration for ongoing autonomous runs.
Is openai-symphony-autonomous-agents safe to install?
Autonomous agents touch git, CI, and external trackers—review the Security Audits panel on this Prism page and lock down tokens, branch policies, and PR approval rules before production use.
SKILL.md
READMESKILL.md - Openai Symphony Autonomous Agents
# OpenAI Symphony > Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection. Symphony turns project work into isolated, autonomous implementation runs, allowing teams to **manage work** instead of **supervising coding agents**. Instead of watching an agent code, you define tasks (e.g. in Linear), and Symphony spawns agents that complete them, provide proof of work (CI status, PR reviews, walkthrough videos), and land PRs autonomously. --- ## What Symphony Does - Monitors a work tracker (e.g. Linear) for tasks - Spawns isolated agent runs per task (using Codex or similar) - Each agent implements the task, opens a PR, and provides proof of work - Engineers review outcomes, not agent sessions - Works best in codebases using [harness engineering](https://openai.com/index/harness-engineering/) --- ## Installation Options ### Option 1: Ask an agent to build it Paste this prompt into Claude Code, Cursor, or Codex: ``` Implement Symphony according to the following spec: https://github.com/openai/symphony/blob/main/SPEC.md ``` ### Option 2: Use the Elixir reference implementation ```bash git clone https://github.com/openai/symphony.git cd symphony/elixir ``` Follow `elixir/README.md`, or ask an agent: ``` Set up Symphony for my repository based on https://github.com/openai/symphony/blob/main/elixir/README.md ``` --- ## Elixir Reference Implementation Setup ### Requirements - Elixir + Mix installed - An OpenAI API key (for Codex agent) - A Linear API key (if using Linear integration) - A GitHub token (for PR operations) ### Environment Variables ```bash export OPENAI_API_KEY="sk-..." # OpenAI API key for Codex export LINEAR_API_KEY="lin_api_..." # Linear integration export GITHUB_TOKEN="ghp_..." # GitHub PR operations export SYMPHONY_REPO_PATH="/path/to/repo" # Target repository ``` ### Install Dependencies ```bash cd elixir mix deps.get ``` ### Configuration (`elixir/config/config.exs`) ```elixir import Config config :symphony, openai_api_key: System.get_env("OPENAI_API_KEY"), linear_api_key: System.get_env("LINEAR_API_KEY"), github_token: System.get_env("GITHUB_TOKEN"), repo_path: System.get_env("SYMPHONY_REPO_PATH", "./"), poll_interval_ms: 30_000, max_concurrent_agents: 3 ``` ### Run Symphony ```bash mix symphony.start # or in IEx for development iex -S mix ``` --- ## Core Concepts ### Isolated Implementation Runs Each task gets its own isolated run: - Fresh git branch per task - Agent operates only within that branch - No shared state between runs - Proof of work collected before PR merge ### Proof of Work Before a PR is accepted, Symphony collects: - CI/CD pipeline status - PR review feedback - Complexity analysis - (optionally) walkthrough videos --- ## Key Elixir Modules & Patterns ### Starting the Symphony supervisor ```elixir # In your application.ex or directly defmodule MyApp.Application do use Application def start(_type, _args) do children = [ Symphony.Supervisor ] Supervisor.start_link(children, strategy: :one_for_one) end end ``` ### Defining a Task (Symphony Task struct) ```elixir defmodule Symphony.Task do @type t :: %__MODULE__{ id: String.t(), title: String.t(), description: String.t(), source: :linear | :manual, status: :pending | :running | :completed | :failed, branch: String.t() | nil, pr_url: String.t() | n