Harness Engineering for Self-Improvement

Lilian Weng’s argument is that recursive self-improvement in AI will arrive through the harness, not through models editing their own weights. The harness, in her definition, is “the system surrounding a base model that orchestrates execution and decides how the model thinks and plans, calls tools and acts, perceives and manages context, stores artifacts, and evaluates results”. Because a harness is just code, it is a much more tractable target for improvement loops than the model itself.

The post is a survey of how those loops work today: context engineering schemes where structured context evolves through generator, reflector and curator roles; evolutionary search over harness code (AlphaEvolve, Darwin Gödel Machine); and self-editing harnesses that mine their own failures, propose bounded edits, and validate them against held-out tests before accepting. Weng is clear-eyed about the failure modes, with weak evaluators and reward hacking at the top of the list.

The HN discussion is worth a skim. One commenter reports that an incomplete check suite silently reporting success was worse than a weak evaluator, because it looked correct and decisive. Another makes the nice point that coding agents already self-improve in a mundane way, by installing and building tools that change their environment, and asks why we treat the agent and its environment as separate at all. There is also a long Torment Nexus joke thread, which tells you how comfortable the room is with the phrase “recursive self-improvement”.

The complement to OpenAI’s harness engineering write-up: that post is about humans building harnesses so agents can ship software, this one is about the harness becoming the thing that improves itself. See also The Anatomy of an Agent Harness for the Agent = Model + Harness framing.