Daniel's personal website

This library entry is part of The Extended Frontier thesis. Entries are curated with AI assistance and human review; most initial entries were prepared with Claude (Anthropic), while individual entries may note other assisting systems. Metadata and annotations are editorial, not peer-reviewed. Entries flagged as unverified may contain placeholder dates, authors, or classifications.

An open-source spec for Codex orchestration: Symphony

Alex Kotliarskyi, Victor Zhu, and Zach Brock··blog·source
Metadata unverified. Content came from user capture; URL is the likely OpenAI canonical URL. Confirm exact canonical URL and byline before formal citation.
The agents were fast, but we had a system bottleneck: human attention.

OpenAI describes Symphony, a spec and reference implementation that turns issue trackers such as Linear into always-on control planes for coding agents, shifting humans from supervising sessions to managing work.

Classification

Role
framework-piece
Domain
software
Source type
blog
Harness types
execution-harnessvalidation-harnessrepair-harnessmonitoring-harnesslearning-harnesssocial-harnessinterface-harness
Validation position
before-generationduring-generationimmediately-after-generationbefore-actionpost-deploymentcontinuous
Validation mode
mechanicalempiricalsocialinstitutional
Prescription stance
strongly-procedural
Relation to argument
capability-is-extendedvalidation-is-constitutiverepairability-mattersobservability-mattersinstitutions-shape-capabilitydiffusion-adoption-bottleneck
Tags
codexsymphonyorchestrationissue-trackerlinearagent-managementapp-server

Extended capability commentary

Input legibility
Issues, WORKFLOW.md, project state, and review packets turn ambiguous work into agent-readable objectives.
Task structure
The issue tracker becomes a state machine/control plane with per-issue workspaces, retries, statuses, and dependencies.
Reward richness
CI, reviews, issue state transitions, PR landing, videos, and human review all become feedback signals.
Feedback latency
Agents continuously observe issue state, CI, review feedback, and runtime failures, though some feedback waits on human review.
Repairability
The system rebases, resolves conflicts, retries flaky checks, restarts stalled agents, and feeds failures back into guardrails and skills.
Observability
Symphony foregrounds logs, status surfaces, review packets, videos, Linear state, and operator visibility.
Reversibility
Per-issue workspaces and PR review preserve isolation and throwaway explorations, though rollback policy is implementation-specific.
Offline evaluability
Software tasks have tests, CI, smoke tests, Chrome DevTools checks, and reproducible workspaces.
Institutional ratification
The issue tracker, review statuses, PM/designer requests, and human review make acceptance institutional rather than merely technical.

Why it matters

Symphony is an explicit account of the next bottleneck after coding-agent capability: organizing agentic work. It treats orchestration, workflow documentation, issue state, CI, and review as capability infrastructure.

Annotation

Symphony is a control-plane argument. OpenAI's team found that interactive coding agents were already capable enough to create a new bottleneck: engineers could only supervise a few sessions before context switching overwhelmed them. Symphony responds by moving the unit of management from "agent session" to "project work."

In the described setup, Linear is not just a queue. It becomes the state machine for agent work. Every eligible issue gets an isolated workspace and a running agent. The orchestrator watches issue states, starts work, restarts stalled agents, handles retries, respects blockers, follows dependency DAGs, and lets agents file follow-up issues when they discover work outside the current scope.

This is a strong example of institutional scaffolding as capability. The agents did not simply get better at coding. The work became more delegable because the surrounding system changed: issues became objectives, WORKFLOW.md captured implicit development norms, CI and QA became part of the run loop, and humans reviewed packets instead of steering terminals.

Extended Frontier Read

The key sentence for this library is the attention bottleneck: the agents were fast, but humans were still micromanaging them. Symphony extends capability by changing the coordination layer:

  • issue tracker as control plane,
  • per-issue workspaces,
  • agent sessions abstracted behind tickets,
  • CI/rebase/conflict handling in the loop,
  • review packets and videos for human ratification,
  • WORKFLOW.md as versioned organizational knowledge,
  • agent-created follow-up work.

That turns "can a model implement this task?" into "can the organization make useful agent work cheap to initiate, observe, review, and land?"

Tension

The post is explicit that not every task belongs in Symphony. Some ambiguous work still needs direct interactive Codex sessions and strong human judgment. That caveat is important: orchestration smooths routine implementation and exploration, but it does not erase the frontier. It shifts which work humans spend attention on.

Notes

Source text supplied by Daniel from OpenAI's April 27, 2026 engineering post. This entry was prepared with Codex (OpenAI).

Related entries

  • Deep Research Query: Work Registration and Collision Prevention
    Daniel S. Griffin · 2026-05-05
    #orchestrationcapability-is-extendedvalidation-is-constitutiveobservability-mattersinstitutions-shape-capabilitydiffusion-adoption-bottleneckexecution-harnessvalidation-harnessmonitoring-harnesssocial-harnessinterface-harness
  • What Is an Agent Harness
    Aparna Dhinakaran · 2026-04-21
    capability-is-extendedvalidation-is-constitutiverepairability-mattersobservability-mattersdiffusion-adoption-bottleneckexecution-harnessvalidation-harnessrepair-harnessmonitoring-harnesslearning-harnesssocial-harnessinterface-harness
  • LLM Knowledge Bases
    Andrej Karpathy · 2026-04-01
    capability-is-extendedvalidation-is-constitutiverepairability-mattersobservability-mattersexecution-harnessvalidation-harnessrepair-harnessmonitoring-harnesslearning-harnessinterface-harness
  • Hermes Agent README
    Nous Research · 2026-04-28
    capability-is-extendedrepairability-mattersobservability-mattersdiffusion-adoption-bottleneckexecution-harnessrepair-harnessmonitoring-harnesslearning-harnesssocial-harnessinterface-harness

Overlap is computed on tags, relation-to-argument, and harness types — not on role or domain, because contrasts are often the most useful neighbours.