Harness Engineering: How to Build Software When Humans Steer, Agents Execute — Ryan Lopopolo, OpenAI

GPT-5.2 marked the "magic moment" for full agent autonomy

Lopopolo identifies GPT-5.2 as the capability inflection point where models became isomorphic to human software engineers in producing production-quality code.

Human engineers now command thousands of agents

Individual engineers can deploy five to five thousand agent-workers in parallel, constrained only by GPU capacity and token budgets exceeding one billion output tokens daily.

Parallel execution eliminates priority backlogs

Previously abandoned P3 tasks can now be attempted immediately across multiple parallel trajectories, with successful solutions merged and failures discarded.

Documentation displaces code as the primary artifact

The valuable output is no longer the implementation but the prompts, ADRs, and guardrails that guide agents, as code has become free to produce, refactor, and delete.

Encode non-functional requirements explicitly

Teams must document quality standards for security and reliability as lint rules and review agent prompts to prevent agents from generating maintenance-burdened "slop."

Durable expertise scales through written standards

Documenting QA plans and coding standards once allows every agent trajectory to inherit the team's collective expertise without synchronous human review.

Deploy automated reviewer agents in CI

Security and reliability agents continuously check proposed patches for patterns like missing timeouts, retries, or unsafe interfaces before human involvement.

Engineer codebases for context efficiency

Adapt repositories to model constraints by enforcing file size limits and writing error messages that include specific remediation prompts to maximize limited context windows.

Compose stackable agent skills

Create reusable "skills" that encode best practices—such as prompt engineering—which agents invoke to maintain consistency and build compound leverage.