Agent Harness for Large Language Model Agents: A Survey
10
17 commits
38 linked in READMEs
updated May 14, 2026
β This repo is actively maintained. If you find it useful, please star the repo to stay updated and help others find it.
The agent execution harness β not the model β is the primary determinant of agent reliability at scale.
This survey formalizes the harness as a first-class architectural object H = (E, T, C, S, L, V), surveys 110+ papers, blogs and reports across 23 systems, and maps 9 open technical challenges.
π Read the Paper π Preprints Version (v3)
βοΈ Corrections & suggestions: gloriamenng@gmail.com (Qianyu Meng); wangyanan@mail.dlut.edu.cn (Yanan Wang); chenliyi@xiaohongshu.com (Liyi Chen)
If you find this survey useful, please cite:
@article{meng2026agentharness,
title = {Agent Harness for Large Language Model Agents: A Survey},
author = {Meng, Qianyu and Wang, Yanan and Chen, Liyi and Wu, Wei and
Li, Yihang and Jiang, Wenyuan and Wang, Qimeng and
Lu, Chengqiang and Gao, Yan and Wu, Yi and Hu, Yao},
year = {2026},
doi = {10.20944/preprints202604.0428.v3},
url = {https://www.preprints.org/manuscript/202604.0428/v3},
publisher = {Preprints},
}
LLM agents are increasingly deployed in agentic settings where they autonomously plan, use tools, and act in multi-step environments. The dominant narrative attributes agent performance to the underlying model. This survey challenges that assumption.
We introduce a formal definition of the agent execution harness as a six-component tuple:
| Component | Symbol | Role |
|---|---|---|
| Execution Loop | E | Observe-think-act cycle, termination conditions, error recovery |
| Tool Registry | T | Typed tool catalog, routing, monitoring, schema validation |
| Context Manager | C | What enters the context window, compaction, retrieval |
| State Store | S | Persistence across turns/sessions, crash recovery |
| Lifecycle Hooks | L | Auth, logging, policy enforcement, instrumentation |
| Evaluation Interface | V | Action trajectories, intermediate states, success signals |
Key empirical evidence that harnesses matter:
Conceptual contribution: We formalize the agent harness as an architectural object with six governable components (E, T, C, S, L, V), elevating it from implicit infrastructure to an explicit research target.
Empirical scope: We systematically review 110+ papers spanning academic research (evaluation benchmarks, security frameworks, memory architectures) and production deployments (Stripe, OpenAI, Cursor, METR), establishing that harness design is a binding constraint on deployed agent reliability.
Methodological advance: We introduce the Harness Completeness Matrix β a structured assessment framework mapping which of the six components each system implements β enabling direct comparison across heterogeneous agent systems that prior surveys could not evaluate on common terms.
Open challenges identified: We document nine technical challenges where current research provides partial solutions but no production-grade infrastructure: formal security models, cross-harness portability, protocol interoperability (MCP/A2A), context economics at 1M+ tokens/task, Byzantine fault tolerance in multi-agent systems, and compositional verification.
Practitioner-academic bridge: Unlike prior surveys focused exclusively on model capabilities or isolated components (memory, planning, tool use), we synthesize peer-reviewed research with production deployment reports to show where theory meets practice β and where critical gaps remain.
Intended audience: Researchers designing agent infrastructure, practitioners building production systems, and evaluators seeking to understand why benchmark performance often fails to predict deployment outcomes.
| Year | Milestone | Significance |
|---|---|---|
| 1997β2005 | JUnit, TestNG, xUnit family | Software test harness paradigm; standardized observe-assert lifecycle |
| 2016 | OpenAI Gym (Brockman et al.) | RL environment harness; step/reset API becomes canonical interface |
| 2022 Nov | ChatGPT public release; LangChain emerges | LLM-native agent frameworks begin; tool-use as first-class citizen |
| 2023 | ReAct, Toolformer, MemGPT, Reflexion, Voyager, AutoGPT | Core agent patterns: reasoning-acting, memory, reflection, skill accumulation |
| 2023 | CAMEL, ChatDev, Generative Agents | Multi-agent coordination; social simulation harnesses |
| 2023 | AgentBench, SWE-bench | Agent evaluation infrastructure emerges |
| 2024 | MetaGPT, WebArena, ToolLLM, SWE-agent, OSWorld | Full-stack harnesses; real-world environment benchmarks |
| 2024 | CodeAct, LATS, Tree of Thoughts | Structured action spaces; search-augmented planning |
| 2024 Nov | Anthropic releases MCP protocol | First major toolβharness standardization (2β15ms latency) |
| 2025 | HAL, AIOS, LangGraph | Benchmark unification (21,730 rollouts); OS-level scheduling (2.1Γ speedup) |
| 2025 | Google releases A2A protocol | Agentβagent standardization (50β200ms) |
| 2025 | MemoryOS, SkillsBenchβ , AgentBoundβ | Memory OS abstraction; skills-as-context (+16.2pp); safety certification |
| 2026 JanβMar | AgencyBenchβ , SandboxEscapeBenchβ , PRISMβ , AEGISβ , SkillFortifyβ , Schema Firstβ | Compute economics; 15β35% escape rates; runtime security; schema discipline |
β preprint
Legend: β full support Β· β partial Β· β absent
| Category | System | E | T | C | S | L | V |
|---|---|---|---|---|---|---|---|
| Full-Stack Harnesses | Claude Code | β | β | β | β | β | β |
| OpenClaw / PRISM | β | β | β | β | β | β | |
| AIOS | β | β | β | β | β | β | |
| OpenHands | β | β | β | β | β | β | |
| Multi-Agent Harnesses | MetaGPT | β | β | β | β | β | β |
| AutoGen | β | β | β | β | β | β | |
| ChatDev | β | β | β | β | β | β | |
| CAMEL | β | β | β | β | β | β | |
| DeerFlow | β | β | β | β | β | β | |
| DeepAgents | β | β | β | β | β | β | |
| General Frameworks | LangChain | β | β | β | β | β | β |
| LangGraph | β | β | β | β | β | β | |
| LlamaIndex | β | β | β | β | β | β | |
| Specialized Harnesses | SWE-agent | β | β | β | β | β | β |
| Capability Modules | MemGPT | β | β | β | β | β | β |
| Voyager | β | β | β | β | β | β | |
| Reflexion | β | β | β | β | β | β | |
| Generative Agents | β | β | β | β | β | β | |
| Concordia | β | β | β | β | β | β | |
| Evaluation Infrastructure | HAL | β | β | β | β | β | β |
| AgentBench | β | β | β | β | β | β | |
| OSWorld | β | β | β | β | β | β | |
| BrowserGym | β | β | β | β | β | β |
What we classify: We categorize agent systems by harness completeness β which of the six components (E, T, C, S, L, V) each system implements β distinguishing full-stack harnesses (all six components) from specialized frameworks (partial implementations).
Why it matters: Prior taxonomies classified agents by application domain (coding, web navigation, embodied AI) or model architecture (single-agent, multi-agent). These categorizations cannot explain why systems with similar models achieve different reliability outcomes. Our harness-centric taxonomy reveals that production-grade systems converge on full ETCSLV implementations, while research prototypes often implement only 2-3 components.
Key finding: No agent framework can achieve production reliability without implementing all six governance components. Systems missing L-component (lifecycle hooks) cannot enforce safety policies. Systems missing V-component (evaluation interfaces) cannot debug failures. Systems missing S-component (state persistence) cannot recover from crashes.
Scope: We identify nine open research problems where current harness infrastructure provides partial solutions but no production-grade, generalizable frameworks. Each challenge represents a gap between what academic prototypes demonstrate and what deployed systems require.
Evaluation criteria: For each challenge, we assess: (1) Academic coverage β peer-reviewed solutions, if any; (2) Production maturity β whether any deployed system has solved it at scale; (3) Blocking severity β whether the unsolved problem prevents deployment or merely limits performance.
Cross-cutting theme: Most challenges stem from the composition problem β individual components (security sandboxes, memory stores, evaluation metrics) work in isolation, but combining them into a coherent harness surfaces emergent failures. Formal verification, portability testing, and protocol interoperability all require compositional reasoning that current research has not addressed.
Challenge: Agent sandboxes must prevent malicious tool use while permitting legitimate system access β a harder problem than traditional application sandboxing because agents intentionally interact with sensitive resources (file systems, network APIs, shell commands).
State of the art: SandboxEscapeBench shows frontier models can escape containers; PRISM demonstrates zero-fork defense-in-depth is possible but requires OS-level instrumentation. No generalizable sandbox exists that works across all agent use cases without manual per-task configuration.
Open problems: Compositional security properties (proving agent + harness + environment satisfy a safety specification) remain unsolved. Current defenses are reactive (detecting escapes) rather than preventive (proving impossibility of escape).
Key numbers: SandboxEscapeBench β frontier LLMs achieve 15β35% container escape rates; PRISM β 10-hook zero-fork runtime reduces escape to near-zero with <5ms overhead.
Key numbers: HAL unified 21,730 rollouts, compressing weeks of evaluation to hours; OSWorld reports 28% false negative rate in automated evaluation; METR finds benchmark-passing PRs have 24.2pp lower human merge rate, widening at 9.6pp/year.
Key numbers: MCP (toolβharness): 2β15ms latency; A2A (agentβagent): 50β200ms; ACP (intent-level, IBM) β three protocols serve complementary roles.
Key numbers: SkillsBench β curated skill injection yields +16.2pp improvement; "Lost in the Middle" effect documented; long-context models shift the problem from retention to salience.
Key numbers: Vercel found removing 80% of tools helped more than any model upgrade; Schema First (Sigdel & Baral, 2026) β a controlled pilot showing that schema-based tool contracts reduce interface misuse but not semantic misuse, with end-task success at zero across all conditions, suggesting interface design alone is insufficient for tool reliability; CodeAct outperforms on 17/17 Mint benchmarks with β20% turns.
Key numbers: Mem0 achieves 90% token reduction vs full-context; Zep temporal knowledge: +18.5% QA accuracy; Agent Workflow Memory: +14.9% on Mind2Web. Six architectural patterns: flat buffer β hierarchical β episodic β semantic β procedural β graph.
Key numbers: SWE-agent ACI study shows interface design outweighs model capability as the primary performance determinant. LATS integrates MCTS with language model feedback for state-space search. Plan-on-Graph enables adaptive self-correcting planning on knowledge graphs through guidance, memory, and reflection mechanisms.
Key numbers: AgencyBench β agents achieve 48.4% success on native SDK harness vs substantially lower on independent harnesses, demonstrating tight harness-agent coupling. Byzantine fault tolerance remains an open problem for adversarial multi-agent settings.
Key numbers: OpenRouter reports 13T tokens/week (Feb 2026), doubling every 4 weeks; AgencyBench measures 1M tokens/task average; 1000Γ agent compute growth projected by 2027; AIOS achieves 2.1Γ throughput speedup via proper agent scheduling.
Production deployment experiences from Stripe, OpenAI, Cursor, METR, and other frontier practitioners.
Eight open research directions identified in the survey (no curated paper list β these are forward-looking):
See BibTeX at the top of this README.
| Version | Date | Changes |
|---|---|---|
| v1 | 2026-04-03 | Initial release |
| v2 | 2026-04-07 | Repo updated |
| v3 | 2026-04-09 | Preprint added |
| v4 | 2026-04-14 | Citation Updated |
β denotes preprint, not yet peer-reviewed.
This survey is under active development; the full manuscript will be released soon.
Maintained by Qianyu Meng & Liyi Chen. PRs welcome for missing papers or updated links.
17 commits
Agent Harness for Large Language Model Agents: A Survey
10
17 commits
38 linked in READMEs
updated May 14, 2026
β This repo is actively maintained. If you find it useful, please star the repo to stay updated and help others find it.
The agent execution harness β not the model β is the primary determinant of agent reliability at scale.
This survey formalizes the harness as a first-class architectural object H = (E, T, C, S, L, V), surveys 110+ papers, blogs and reports across 23 systems, and maps 9 open technical challenges.
π Read the Paper π Preprints Version (v3)
βοΈ Corrections & suggestions: gloriamenng@gmail.com (Qianyu Meng); wangyanan@mail.dlut.edu.cn (Yanan Wang); chenliyi@xiaohongshu.com (Liyi Chen)
If you find this survey useful, please cite:
@article{meng2026agentharness,
title = {Agent Harness for Large Language Model Agents: A Survey},
author = {Meng, Qianyu and Wang, Yanan and Chen, Liyi and Wu, Wei and
Li, Yihang and Jiang, Wenyuan and Wang, Qimeng and
Lu, Chengqiang and Gao, Yan and Wu, Yi and Hu, Yao},
year = {2026},
doi = {10.20944/preprints202604.0428.v3},
url = {https://www.preprints.org/manuscript/202604.0428/v3},
publisher = {Preprints},
}
LLM agents are increasingly deployed in agentic settings where they autonomously plan, use tools, and act in multi-step environments. The dominant narrative attributes agent performance to the underlying model. This survey challenges that assumption.
We introduce a formal definition of the agent execution harness as a six-component tuple:
| Component | Symbol | Role |
|---|---|---|
| Execution Loop | E | Observe-think-act cycle, termination conditions, error recovery |
| Tool Registry | T | Typed tool catalog, routing, monitoring, schema validation |
| Context Manager | C | What enters the context window, compaction, retrieval |
| State Store | S | Persistence across turns/sessions, crash recovery |
| Lifecycle Hooks | L | Auth, logging, policy enforcement, instrumentation |
| Evaluation Interface | V | Action trajectories, intermediate states, success signals |
Key empirical evidence that harnesses matter:
Conceptual contribution: We formalize the agent harness as an architectural object with six governable components (E, T, C, S, L, V), elevating it from implicit infrastructure to an explicit research target.
Empirical scope: We systematically review 110+ papers spanning academic research (evaluation benchmarks, security frameworks, memory architectures) and production deployments (Stripe, OpenAI, Cursor, METR), establishing that harness design is a binding constraint on deployed agent reliability.
Methodological advance: We introduce the Harness Completeness Matrix β a structured assessment framework mapping which of the six components each system implements β enabling direct comparison across heterogeneous agent systems that prior surveys could not evaluate on common terms.
Open challenges identified: We document nine technical challenges where current research provides partial solutions but no production-grade infrastructure: formal security models, cross-harness portability, protocol interoperability (MCP/A2A), context economics at 1M+ tokens/task, Byzantine fault tolerance in multi-agent systems, and compositional verification.
Practitioner-academic bridge: Unlike prior surveys focused exclusively on model capabilities or isolated components (memory, planning, tool use), we synthesize peer-reviewed research with production deployment reports to show where theory meets practice β and where critical gaps remain.
Intended audience: Researchers designing agent infrastructure, practitioners building production systems, and evaluators seeking to understand why benchmark performance often fails to predict deployment outcomes.
| Year | Milestone | Significance |
|---|---|---|
| 1997β2005 | JUnit, TestNG, xUnit family | Software test harness paradigm; standardized observe-assert lifecycle |
| 2016 | OpenAI Gym (Brockman et al.) | RL environment harness; step/reset API becomes canonical interface |
| 2022 Nov | ChatGPT public release; LangChain emerges | LLM-native agent frameworks begin; tool-use as first-class citizen |
| 2023 | ReAct, Toolformer, MemGPT, Reflexion, Voyager, AutoGPT | Core agent patterns: reasoning-acting, memory, reflection, skill accumulation |
| 2023 | CAMEL, ChatDev, Generative Agents | Multi-agent coordination; social simulation harnesses |
| 2023 | AgentBench, SWE-bench | Agent evaluation infrastructure emerges |
| 2024 | MetaGPT, WebArena, ToolLLM, SWE-agent, OSWorld | Full-stack harnesses; real-world environment benchmarks |
| 2024 | CodeAct, LATS, Tree of Thoughts | Structured action spaces; search-augmented planning |
| 2024 Nov | Anthropic releases MCP protocol | First major toolβharness standardization (2β15ms latency) |
| 2025 | HAL, AIOS, LangGraph | Benchmark unification (21,730 rollouts); OS-level scheduling (2.1Γ speedup) |
| 2025 | Google releases A2A protocol | Agentβagent standardization (50β200ms) |
| 2025 | MemoryOS, SkillsBenchβ , AgentBoundβ | Memory OS abstraction; skills-as-context (+16.2pp); safety certification |
| 2026 JanβMar | AgencyBenchβ , SandboxEscapeBenchβ , PRISMβ , AEGISβ , SkillFortifyβ , Schema Firstβ | Compute economics; 15β35% escape rates; runtime security; schema discipline |
β preprint
Legend: β full support Β· β partial Β· β absent
| Category | System | E | T | C | S | L | V |
|---|---|---|---|---|---|---|---|
| Full-Stack Harnesses | Claude Code | β | β | β | β | β | β |
| OpenClaw / PRISM | β | β | β | β | β | β | |
| AIOS | β | β | β | β | β | β | |
| OpenHands | β | β | β | β | β | β | |
| Multi-Agent Harnesses | MetaGPT | β | β | β | β | β | β |
| AutoGen | β | β | β | β | β | β | |
| ChatDev | β | β | β | β | β | β | |
| CAMEL | β | β | β | β | β | β | |
| DeerFlow | β | β | β | β | β | β | |
| DeepAgents | β | β | β | β | β | β | |
| General Frameworks | LangChain | β | β | β | β | β | β |
| LangGraph | β | β | β | β | β | β | |
| LlamaIndex | β | β | β | β | β | β | |
| Specialized Harnesses | SWE-agent | β | β | β | β | β | β |
| Capability Modules | MemGPT | β | β | β | β | β | β |
| Voyager | β | β | β | β | β | β | |
| Reflexion | β | β | β | β | β | β | |
| Generative Agents | β | β | β | β | β | β | |
| Concordia | β | β | β | β | β | β | |
| Evaluation Infrastructure | HAL | β | β | β | β | β | β |
| AgentBench | β | β | β | β | β | β | |
| OSWorld | β | β | β | β | β | β | |
| BrowserGym | β | β | β | β | β | β |
What we classify: We categorize agent systems by harness completeness β which of the six components (E, T, C, S, L, V) each system implements β distinguishing full-stack harnesses (all six components) from specialized frameworks (partial implementations).
Why it matters: Prior taxonomies classified agents by application domain (coding, web navigation, embodied AI) or model architecture (single-agent, multi-agent). These categorizations cannot explain why systems with similar models achieve different reliability outcomes. Our harness-centric taxonomy reveals that production-grade systems converge on full ETCSLV implementations, while research prototypes often implement only 2-3 components.
Key finding: No agent framework can achieve production reliability without implementing all six governance components. Systems missing L-component (lifecycle hooks) cannot enforce safety policies. Systems missing V-component (evaluation interfaces) cannot debug failures. Systems missing S-component (state persistence) cannot recover from crashes.
Scope: We identify nine open research problems where current harness infrastructure provides partial solutions but no production-grade, generalizable frameworks. Each challenge represents a gap between what academic prototypes demonstrate and what deployed systems require.
Evaluation criteria: For each challenge, we assess: (1) Academic coverage β peer-reviewed solutions, if any; (2) Production maturity β whether any deployed system has solved it at scale; (3) Blocking severity β whether the unsolved problem prevents deployment or merely limits performance.
Cross-cutting theme: Most challenges stem from the composition problem β individual components (security sandboxes, memory stores, evaluation metrics) work in isolation, but combining them into a coherent harness surfaces emergent failures. Formal verification, portability testing, and protocol interoperability all require compositional reasoning that current research has not addressed.
Challenge: Agent sandboxes must prevent malicious tool use while permitting legitimate system access β a harder problem than traditional application sandboxing because agents intentionally interact with sensitive resources (file systems, network APIs, shell commands).
State of the art: SandboxEscapeBench shows frontier models can escape containers; PRISM demonstrates zero-fork defense-in-depth is possible but requires OS-level instrumentation. No generalizable sandbox exists that works across all agent use cases without manual per-task configuration.
Open problems: Compositional security properties (proving agent + harness + environment satisfy a safety specification) remain unsolved. Current defenses are reactive (detecting escapes) rather than preventive (proving impossibility of escape).
Key numbers: SandboxEscapeBench β frontier LLMs achieve 15β35% container escape rates; PRISM β 10-hook zero-fork runtime reduces escape to near-zero with <5ms overhead.
Key numbers: HAL unified 21,730 rollouts, compressing weeks of evaluation to hours; OSWorld reports 28% false negative rate in automated evaluation; METR finds benchmark-passing PRs have 24.2pp lower human merge rate, widening at 9.6pp/year.
Key numbers: MCP (toolβharness): 2β15ms latency; A2A (agentβagent): 50β200ms; ACP (intent-level, IBM) β three protocols serve complementary roles.
Key numbers: SkillsBench β curated skill injection yields +16.2pp improvement; "Lost in the Middle" effect documented; long-context models shift the problem from retention to salience.
Key numbers: Vercel found removing 80% of tools helped more than any model upgrade; Schema First (Sigdel & Baral, 2026) β a controlled pilot showing that schema-based tool contracts reduce interface misuse but not semantic misuse, with end-task success at zero across all conditions, suggesting interface design alone is insufficient for tool reliability; CodeAct outperforms on 17/17 Mint benchmarks with β20% turns.
Key numbers: Mem0 achieves 90% token reduction vs full-context; Zep temporal knowledge: +18.5% QA accuracy; Agent Workflow Memory: +14.9% on Mind2Web. Six architectural patterns: flat buffer β hierarchical β episodic β semantic β procedural β graph.
Key numbers: SWE-agent ACI study shows interface design outweighs model capability as the primary performance determinant. LATS integrates MCTS with language model feedback for state-space search. Plan-on-Graph enables adaptive self-correcting planning on knowledge graphs through guidance, memory, and reflection mechanisms.
Key numbers: AgencyBench β agents achieve 48.4% success on native SDK harness vs substantially lower on independent harnesses, demonstrating tight harness-agent coupling. Byzantine fault tolerance remains an open problem for adversarial multi-agent settings.
Key numbers: OpenRouter reports 13T tokens/week (Feb 2026), doubling every 4 weeks; AgencyBench measures 1M tokens/task average; 1000Γ agent compute growth projected by 2027; AIOS achieves 2.1Γ throughput speedup via proper agent scheduling.
Production deployment experiences from Stripe, OpenAI, Cursor, METR, and other frontier practitioners.
Eight open research directions identified in the survey (no curated paper list β these are forward-looking):
See BibTeX at the top of this README.
| Version | Date | Changes |
|---|---|---|
| v1 | 2026-04-03 | Initial release |
| v2 | 2026-04-07 | Repo updated |
| v3 | 2026-04-09 | Preprint added |
| v4 | 2026-04-14 | Citation Updated |
β denotes preprint, not yet peer-reviewed.
This survey is under active development; the full manuscript will be released soon.
Maintained by Qianyu Meng & Liyi Chen. PRs welcome for missing papers or updated links.
17 commits