Harness Engineering

Harness engineering is the practice of making a codebase, toolchain, and team process legible enough that coding agents can work, verify, review, and hand off changes with less human babysitting.

Key points

• OpenAI frames the move from autocomplete and pair programming into agent delegation as requiring a better "harness" around the model, not only a better model ^[src-084].
• The API & Codex Build Hour demo builds an "agent legibility score" for repositories, with criteria such as bootstrap self-sufficiency, task entry points, validation harnesses, linting, formatting, documentation, and modular boundaries ^[src-084].
• Worktrees are part of the harness because they let multiple agent tasks run in parallel on separate branches without clobbering each other ^[src-084].
• High-quality validation is central: tests, lint, build commands, browser checks, logs, and other acceptance signals let Codex decide whether the work is actually done ^[src-084].
• Skills and subagents encode repeatable team standards, such as PR creation, commit style, code review, architecture review, standards enforcement, and pull-request follow-up ^[src-084].
• Team knowledge should move from individual heads and chat history into version-controlled files, docs, specs, skills, notes, and local decision records so every agent benefits from the same context ^[src-084].
• The source also adds a company-context version: an "Atlas" style repo for operating principles, strategy, and non-code context can make Codex useful beyond production code ^[src-084].

Related entities

• OpenAI
• Codex (OpenAI)
• GPT-5.4

Related concepts

• Agentic Engineering
• Agent Harness Portability
• Codex Project Workspace
• Context Engineering
• Progressive Context Loading (Skills)
• Human-Agent Collaboration
• Continuous Agent Evaluation

Source references

• ^[src-084] OpenAI Codex, Workspace Agents, Prompt Caching, and Superintelligence Policy cluster (2026-02-09 to 2026-05-08)