Extreme Harness Engineering

Ryan Lopopolo’s team produced roughly 1 million lines of code in the total codebase and 1,500 PRs in five months under a deliberate constraint that Ryan write no code himself. The constraint was deliberate: if enterprise agents were to perform his job, “the only way I could do my job was to get the agent to do my job.” Codex Mini initially failed at whole features, forcing the team to build smaller primitives that agents could later assemble reliably.

The productivity curve first moved sharply backward, then overwhelmed traditional engineering throughput. The first month and a half was “10 times slower” than Ryan coding by hand, but paying that tooling cost ultimately made the system roughly 10x faster than one engineer. The broader call is that agent adoption requires funding an assembly line before expecting assembly-line economics.

At agent scale, synchronous human attention—not tokens or code generation—is the scarce resource. The team progressed from close code review to mostly post-merge sampling because models are “trivially parallelizable,” while people still need sleep and cannot follow dozens of concurrent trajectories. Autonomy remains bounded: this is a greenfield native application, and a human still cuts the release branch and approves a smoke test before distribution.

The durable advantage is encoded institutional taste: documentation, tests, lints, observability, and review agents that turn every failure into future context. A missing timeout becomes both a fix and a rule requiring timeouts on every network call; a failed build or PR comment signals that “at some point the agent was missing context.” The advantage therefore shifts from privately held engineering intuition toward a continuously improving, machine-readable operating system.

Symphony removed terminal babysitting; Shawn described the resulting workflow as producing another 5x productivity increase. Output had already risen from 3.5 PRs per engineer per day before 5.2 to 5–10 after 5.2, but context switching exhausted the humans; Symphony instead drives tickets through completion and escalates a compact merge decision. If a result fails review, it deletes the worktree and PR and starts over because code now carries “close to zero investment in the actual authorship experience.”

Code abundance may compress parts of the software-dependency and internal-tools markets, although Ryan preserved important limits. He thinks a dependency of a couple thousand lines can already be internalized in an afternoon, stripped to the exact functionality needed, while “ghost libraries” can distribute a reproducible specification instead of source. Shawn’s counterpoint was that internalization resets confidence to zero, forfeiting lessons accumulated through widespread use and “many eyes.”

In the later Frontier discussion, Peter Steinberger described the same factory model extending from coding into governed enterprise labor. Frontier targets observable agents integrated with IAM, security tooling, workspaces, bespoke safety policies, and revocable authorization. David Luan reported that Codex had passed 2 million weekly active users while growing 25% week over week; Shawn cited roughly 1 billion tokens of intelligence deployed daily. Yet the frontier remains clear: hard, novel product creation and the “gnarliest refactorings” still require sustained human steering.

🔗 Original source & video: Extreme Harness Engineering: 1M LOC, 1B toks/day, 0% human code or review — Ryan Lopopolo, OpenAI