ZeroHour
arXiv cs.AI / cs.LG / cs.CLpublished ()ingested Run-Ze Fan1
Part of a story covered by 3 sources: “Coding-agent harness design advances: ModularRSI recursive self-improvement and an empirical study of 176 harness configurations” — merged summary and timeline →

An Empirical Study of Harness Design for Coding Agents

infoAI researchimportance 35
AI summary · glm-5.3-flash

Empirical study of coding agent harnesses across 176 settings shows context management prevents overflow failures and bash-only interfaces cut costs for capable models.

The study uses a lightweight coding harness with a fixed execution loop while varying planning, action space, and context management, evaluating 176 matched settings across four models on SWE-Bench Verified and Terminal-Bench 2.1. Context management becomes more valuable as context-window budgets tighten, mostly by preventing context-overflow failures, with rule-based elision before LLM summarization the strongest strategy. Planning shifts from an accuracy scaffold for weaker models to a cost saver for stronger ones, and bash-capable models work well with a bash-only interface at substantially lower cost, informing model- and budget-aware harness design.

  • 176 matched settings across four models on SWE-Bench Verified and Terminal-Bench 2.1
  • Context management mainly prevents context-overflow failures as window budgets tighten
  • Rule-based elision before LLM summarization gives the best efficiency among strategies
  • Bash-capable models perform well with bash-only tools at substantially lower cost
  • Planning matters more for weaker models' accuracy; stronger models use it to save cost
Full article247 words · extracted from arxiv.org · click to collapse

Coding harnesses shape how autonomous coding agents translate model capabilities into long-horizon software-engineering performance, yet existing work typically evaluates harnesses as monolithic systems, leaving the effectiveness of individual components unclear. To enable component-level comparisons, we study this question with a lightweight coding harness whose execution loop is fixed while three components are varied: planning, action space, and context management. Across four models evaluated on SWE-Bench Verified and Terminal-Bench 2.1, we evaluate 176 matched settings spanning five context-management strategies, four context-window budgets, and targeted ablations of planning and action space. We find that: (1) Context management becomes increasingly valuable as the context-window budget tightens, with most of its benefit coming from preventing context-overflow failures. (2) Staging rule-based elision before LLM-based summarization provides the strongest overall efficiency among the context-management strategies, whereas making elided content recoverable adds machinery that models rarely use and yields no accuracy gain. (3) Planning shifts from an accuracy scaffold for weaker models to a cost saver for stronger models, with little change in accuracy. (4) Predefined tools improve performance for models with weaker bash proficiency, whereas bash-capable models can operate effectively with a bash-only interface and achieve substantially lower cost, especially on command-line-centric tasks. Trajectory-level analysis explains these effects: context management extends execution trajectories without substantially altering agent behavior, planning changes where trajectories stop, and the action space changes the granularity at which code is written. These findings inform model- and budget-aware harness design and provide a modular framework for evaluating future harness components.

Text extracted automatically; images, tables and formatting may be missing. Original: https://arxiv.org/abs/2609.20804