中文
← Back to news
FrameworksJul 9, 2026

Lilian Weng Proposes Harness Engineering for AI Self-Improvement: Near-Term Path Lies in Peripheral Systems, Not Model Weights

Former OpenAI VP of Safety Research and co-founder of Thinking Machines Lab, Lilian Weng, published a blog post on July 4, 2026, titled "Harness Engineering for Self-Improvement," systematically outlining a near-term feasible path for recursive self-improvement (RSI) in AI. She argues that AI self-improvement should not start with models directly rewriting their own weights, but rather prioritize optimizing the Harness system that wraps around the model—the execution layer responsible for orchestrating model thinking, tool invocation, context management, and result evaluation. This view was endorsed by DeepSeek researcher Tianyi Cui.

Core Argument: Harness Layer Over Model Weights

Weng points out that the near-term path for RSI is more likely to occur at the Harness layer rather than the model weight layer. The Harness is a system built around the base model, determining how the model plans, invokes tools, manages context, stores outputs, and evaluates results. She believes that improving the "mechanism for obtaining better answers" is more realistic than improving the answers themselves. Many improvements at the Harness layer may eventually be internalized as model capabilities, but the external interface should be retained.

Three Design Patterns for Harness

Weng identifies three core design patterns for Harness engineering:

  • Workflow Automation: Define goal-oriented loops (plan → execute → observe/test → improve), where the model iterates by analyzing its own trajectory at runtime, rather than relying on static prompts.
  • File System as Persistent Memory: Store outputs such as experiment logs and code diffs as files to avoid context window overflow, leveraging the LLM's bash read/write capabilities.
  • Sub-Agents and Backend Tasks: Spawn multiple sub-agents for parallel execution, monitored and merged by a process manager to ensure state recoverability.

Harness Optimization Path: From Context to Evolutionary Search

Weng summarizes the evolution of optimization targets as: instruction prompts → structured context → workflows → Harness code → optimizer code. Specifics include:

  • Context Engineering: ACE treats context as a dynamic manual; MCE separates context management skills from content.
  • Workflow Design: AI Scientist, ADAS, AFlow, and others incorporate process structure into the search space.
  • Self-Improving Harness: Self-Harness automatically optimizes Harness configurations through a cycle of weakness mining, proposal generation, and validation.
  • Evolutionary Search: Darwin Gödel Machine (DGM) allows coding agents to directly modify their own Harness code, improving from 20% to 50% on SWE-bench Verified and from 14.2% to 30.7% on Polyglot, matching or exceeding human-designed systems.

Challenges and Boundaries

Weng candidly lists current bottlenecks:

  • Evaluators are too weak; only tasks like code and math that can be automatically evaluated run the cycle smoothly, while scientific taste and other qualities are hard to quantify.
  • Lifecycle management of context and memory remains unsolved.
  • Negative results are systematically ignored; models may not be good at judging when to abandon hypotheses.
  • Diversity collapse: evolutionary loops may converge to local optima.
  • Reward hacking remains an issue.

Connection to Scaling Laws

Two weeks ago, Weng published "Scaling Laws, Carefully," pointing out that fitting scaling laws is affected by details such as parameter counting methods, loss precision, and data duplication, making extrapolation risky. Both articles together suggest: when the marginal benefit of stacking parameters and data diminishes, Harness engineering may become the second growth curve for AI.

Also available in 中文.