OpenAI's engineering leaders detail the pipeline now running its production code

Gergely Orosz interviewed seven OpenAI engineers and engineering leaders, including Venkat Venkataramani, VP of Engineering for Applied Infra, about the pipeline that now runs the company's software. In Orosz's account, a human still defines the desired outcome, but Codex then gathers context from git, Slack, Notion, Databricks and Datadog, writes the change, runs it through CI and a new performance harness, sends it to review agents configured as domain specialists, and hands the approved change to a deployment agent that builds its own monitoring dashboard and watches the rollout. Venkataramani said pull request volume per engineer is "growing like a hockey stick," and that OpenAI is seeing "roughly a 10x increase in load on some systems" in about six months, growth he said would take two to three years at most companies. Production incidents go to Sevbot, an internal agent that gathers context and proposes mitigations in Slack but, in the piece's words, "never executes any." The published portion of the article covers this pipeline in detail; later sections on tooling changes, infrastructure scaling and how the engineering job itself is changing sit behind a paywall this edition did not access.

Why it matters: Orosz's account describes a coding-agent pipeline running a frontier lab's production software. It divides review among domain-specific agents, gives a deployment agent responsibility for rollout instrumentation, and prevents the incident-response agent from taking action. Teams assembling a harness can compare those boundaries with their own decisions about automation and human approval.