Harness engineering becomes agent battleground
AlphaSignal’s post frames OpenAI, Anthropic, and ThoughtWorks as converging on the same agent-era lesson: the model matters, but the surrounding harness increasingly determines reliability. OpenAI emphasizes agent-legible repos and feedback loops, Anthropic pushes managed long-running agent infrastructure, and ThoughtWorks turns the idea into guides, sensors, and governance patterns.
The useful shift here is that “agent engineering” is becoming less about clever prompts and more about boring systems work: constraints, observability, verification, permissions, and recovery.
- –OpenAI’s version is the most aggressive: make the repo itself legible to Codex, encode taste as tooling, and let agents iterate through PRs, tests, and reviews.
- –Anthropic’s answer is more platform-shaped: decouple the model from the tools and runtime so managed agents can run longer jobs while the harness evolves underneath.
- –ThoughtWorks brings the enterprise lens: treat harnesses as feedforward guides and feedback sensors, mixing deterministic checks with AI review.
- –For developers, this makes harness design a new leverage point: better tests, linters, permissions, docs, and state handling can outperform simply swapping models.
DISCOVERED
45d ago
2026-04-23
PUBLISHED
45d ago
2026-04-23
RELEVANCE
AUTHOR
AlphaSignalAI