harness-engineering

Google's developer blog argues for testing discrete agent behaviors instead of relying only on composite benchmark scores, framing eval suites mainly as regression guards against prompt, tool, or model changes; the post contrasts this with OpenAI's build-side harness engineering approach.

The user recommends Factory’s technical article “Droid 1.0: Building a Frontier Harness,” highlighting engineering optimizations such as Programmatic Tool Calling, on-demand tool loading, long-running background tasks, and Agent Factory, and sharing a case in which the same optimization had opposite effects on costs for different models (Opus vs. Kimi).

Introducing the open-source course project Learn Harness Engineering (21K+ ⭐), which teaches you how to build engineering environments that enable AI coding agents to run reliably through 14 lessons and 8 hands-on projects, with Chinese language support.

Updated lecture notes for MIT OpenCourseWare 6.S950 Agency with AI, Lecture 5: The Harness, walking through a ~300-line teaching Agent to explain the principles of observability, controllability, and the question of how much Harness you actually need.

A free online book and GitHub repository, 'Harness Engineering 101', that teaches how to build AI agents from first principles — treating the LLM as the brain and the surrounding harness program as the body, across 16 chapters with a growing ~300-line Python toy agent.

Doc2Harness 提出了一个两阶段基准，直接评测 LLM 构建长周期编码代理 harness 的能力；在 19 个前沿模型中，GPT-6Astra 以 53.05% 的通过率领先，而表现最弱的模型仅为 27.44%。

A tweet recommending a paper on harness engineering that breaks down Claude Code (Opus 5.5), Codex, Gemini CLI and other coding agents into the formula agent = model + harness, covering how agents are built, recurring patterns, future directions, and a checklist for building your own.

Kirk Borne shares a 48-page PDF handbook on understanding Harness Engineering for AI Agents, a guide aimed at developers building agent systems.

Brendan Jowett highlights "Harness Engineering" as an emerging AI skill and promotes a curated GitHub repository mapping the infrastructure around AI agents — context engineering, memory, MCP tools, evals, orchestration, and permissions/sandboxes.

Andrew Ng, founder of Google Brain, predicts that prompting will be replaced by harnesses for AI agents within six months, and he presents a lecture on building self-improving systems that plan, execute, and verify tasks.

The article explains why top AI Agent teams are focusing on Harness Engineering, emphasizing that robust runtime scaffolding is crucial for reliable execution in complex scenarios, beyond just model intelligence.

Analysis of 246 open-source repositories and 57 papers on agent harnesses highlights best practices like human-written context, limiting tools, and incremental testing to improve AI agent performance.

Google Research has started researching Recursive Self-Improvement for Agent Harness, focusing on automatically iterating prompts, tools, memory, and control flow without model retraining. This harness-level approach is seen as clearer and more practical than model-level RSI.

The article emphasizes that in AI agents, the harness—comprising tools, context, controls, and workflows—is more critical than the model for achieving reliable, safe, and traceable outcomes.

Harness engineering is a practice to maintain code quality in AI-assisted development by using deterministic tooling and agent-based review to prevent codebase drift and ensure coherence over time.

Two talks and a blog post argue that the feedback loop and harness engineering are more important than model weights for owning AI intelligence in production, highlighting context management and cost considerations.

The article explains harness engineering as a key trend for controlling AI agents by designing deterministic environments, using tools like Google Antigravity SDK, and illustrates how teams can ship software with AI-generated code through sandboxing and repair loops.

This article introduces two books found on GitHub that detail Claude Code's underlying architecture and design philosophy, compare Claude Code with Codex, and help developers understand the design logic of AI coding agents.

The author argues that RL environments serve as the essential data for building AI agents, enabling systematic training, prompt optimization, and evaluation rather than manual iteration.

Omar recommends reading Chamath Palihapitiya's AI investing guide, emphasizing the importance of harness engineering and evals for AI builders.