Extreme Harness Engineering for Token Billionaires: 1M LOC, 1B toks/day, 0% human code, 0% human review — Ryan Lopopolo, OpenAI Frontier & Symphony

What It Covers

Ryan Lopopolo from OpenAI's Frontier team describes building a 1M+ line Electron application over five months with zero human-written code, deploying 1B tokens daily through a fully autonomous multi-agent pipeline. The episode covers harness engineering principles, the Symphony orchestration system built in Elixir, and how small teams can eliminate human bottlenecks from the software development lifecycle.

Key Questions Answered

• •Build time discipline as agent constraint: Cap CI build times at under one minute to force modular architecture. When GPT-4.5's background shell feature made the model less patient with blocking scripts, Lopopolo's team rebuilt their entire build system — migrating from Make to Bazel to Turbo to NX within one week — because fast builds directly determine how long agents can operate without interruption.
• •Encode non-functional requirements as text, not code: Every engineering standard — network call timeouts, reliability patterns, architecture decisions — should be written into markdown documentation that gets prompt-injected into agents. When a production page fires, add the fix to reliability docs so the requirement persists permanently. This converts one-time fixes into durable institutional knowledge the agent references on every future task.
• •Post-merge review replaces pre-merge review at scale: With 1,500+ PRs generated across five months, human review became the bottleneck. The team shifted to post-merge sampling rather than blocking merges on human approval. Humans review a representative sample to infer systemic agent mistakes, then encode corrections into docs or lints — functioning more like a tech lead managing 500 engineers than a line-level reviewer.
• •Agent PR review requires explicit priority thresholds: When deploying automated code review agents alongside coding agents, define explicit merge-bias instructions. Without them, coding agents get "bullied" into scope-expanding changes by reviewer agents, causing non-convergence. The team resolved this by instructing reviewer agents to surface only P0-level issues (defined as code that breaks the codebase) and giving coding agents explicit permission to defer lower-priority feedback to backlog.
• •Symphony's rework state eliminates monitoring overhead: The Elixir-based Symphony orchestrator handles the full PR lifecycle autonomously — pushing branches, waiting for CI, resolving merge conflicts, and entering the merge queue. When a PR fails human review, Symphony trashes the entire work tree and restarts from scratch. This removes the need for engineers to monitor terminal sessions, shifting human attention from synchronous babysitting to async review of completed work.
• •Ghost library distribution via self-generating specs: To share the harness architecture externally, the team used Codex to write a spec from their proprietary repo, then spawned a disconnected Codex instance in a separate TMux to implement the spec, then spawned a third Codex to compare the implementation against upstream and refine the spec iteratively. This loop runs until the spec reproduces the system with high fidelity — enabling others to reconstruct the full system by feeding the spec to any coding agent.