HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
openai
symphony
Elixir2026–2026
openai / symphony

symphony

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

15Distinct people
16Mentions
1Explicit recommenders
28KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love the idea of using a shared event log for coordination. Smart! I have a Symphony-style[1] factory, which keeps all the context in a single session, but I want to start…

jessmartin used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week16 dated mentions

Observed mentions: 2026-03-04 18:50:39 UTC to 2026-07-23 16:11:42 UTC. Weeks start Monday, UTC.

02468102026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 9 mentions; 7 submissions, 2 commentsMar 22026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-13 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-20 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 112026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 20

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC972
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC211
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC000
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC000
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC000
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC101
Apr 132026-04-13 00:00:00 UTC2026-04-20 00:00:00 UTC000
Apr 202026-04-20 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-05-04 00:00:00 UTC000
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC000
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC000
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC101
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC101
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC000
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC101
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC000
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC000
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC101

What Hacker News says

16 sources
It was the BEAM process/actor model that fit much better for managing agents, and then there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing. I had started the project in Typescript/Node (because that's my company's primary stack choice), but it hit a plateau in reliably managing multiple independent long-lived agent processes (not really what Node is designed for). I could have used an even more boring tech like Go with more robust process management, but Elixir and Phoenix also came with a lot out of the box. It's no surprise that OpenAI's reference project for agent orchestration (https://github.com/openai/symphony) is also written in Elixir.
In Hologram Works. Sponsor What Comes Next
wrote something similar for my own use/work stuff; seems everything is converging towards similar ideas. IMO, this style of workflow/agentics is how all SWE'll look like long term. Automate everything into a big pipe-y thing. How it's gonna be modelled is up in the air though. lots of different approaches: mine: https://github.com/portpowered/you-agent-factory https://github.com/ComposioHQ/agent-orchestrator https://github.com/gastownhall/gastown https://github.com/openai/symphony
In Dynamic Workflows in Claude Code
Symphony is fine, but I'm more impressed at them sharing the spec and encourage others to build their own[0]. I haven't seen quite the same example of "show me the prompt" in open source before, alongside the open invite to build it yourself. > Implement Symphony according to the following spec: > https://github.com/openai/symphony/blob/main/SPEC.md [1] [0] https://github.com/openai/symphony?tab=readme-ov-file#option... [1] https://github.com/openai/symphony/blob/main/SPEC.md
In OpenAI Symphony

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.