openai symphony
OFFICIALLABSCO SUMMARY
The six line up with one lifecycle: commit builds a commit message from session history, pull merges the latest origin/main into a feature branch, push publishes the branch and opens a pull request, land waits for checks and squash-merges it once green, debug traces Symphony's and Codex's logs when a run stalls or fails, and linear runs raw GraphQL calls against Symphony's own Linear client for things like comment edits and uploads. All 6 skills sit as one flat set in our database — no page groups, no categories.
Symphony itself is not a general automation library; these six skills are the connective tissue for one specific system. OpenAI's own description says it "turns project work into isolated, autonomous implementation runs" so a Codex-based agent can watch a Linear board, spawn a run per task, and use these skills to land the resulting pull request without an engineer typing the git commands by hand. Getting it running takes one of two paths: write your own implementation from the published SPEC.md, or use OpenAI's experimental Elixir reference implementation.
READ THE FULL ANALYSIS
What it costs to start. Two of the six skills are ready to use with nothing else installed, two depend on a local tool already being present on the machine, one needs a saved account credential, and one talks to an MCP service — so even at six skills, this is not an install-and-go set.
What Symphony is not, in OpenAI's own words. The README calls it "a low-key engineering preview for testing in trusted environments" and says it works best in codebases that have already adopted OpenAI's "harness engineering" approach — not a plugin for an arbitrary repository, and not a finished product, whatever its 25,801 stars suggest.
Checked 19 September 2026 from OpenAI's own README and the six skill descriptions in our database; we have not run Symphony or its Elixir reference implementation.
WHAT'S INSIDE
6 showing · 6 totalNothing else to set up — install it and go.
commit
A commit is a saved change plus the note that explains it — and the note here is written from the session you just had, not from the file diff alone.
debug
Symphony runs coding agents on tickets by itself; when one of those runs hangs or quietly keeps retrying, this is how you find out what actually happened.
land
A pull request does not merge itself, and this does not hand it back half-finished — it stays with the pull request until it is genuinely merged.
linear
Reaches straight into Linear from inside a Symphony session, using the login that session already holds, so tickets can be read and changed without setting up access first.
pull
While you were working, everybody else was too — this catches your branch up with them, and the hard part is never the merge itself but deciding which side should win.
push
The point where your work leaves your machine and becomes something other people can see, with the pull request around it kept honest about what the branch now contains.
HOW TO GET IT
npx skills add openai/symphonynpx skills add openai/symphony --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.