Harness Handbook maps agent behaviors back to source code and lifts plan accuracy
omarsar0 · x · 2026-07-23
The paper Harness Handbook: Making Evolving Agent Harnesses Readable, Navigable, and Editable proposes a behavior-centric way to localize code behind agent behaviors.
What it does
- Builds a three-level map from runtime behaviors to source locations using static analysis plus LLM-assisted structuring.
- Introduces BGPD (Behavior-Guided Progressive Disclosure), which guides coding agents from a system overview down to relevant stages, functions, and files, then checks candidates against the current source.
Reported results
On 60 modification requests across Codex and Terminus-2:
- Planning win rate rose from 28.3% to 38.3% on one benchmark and 26.7% to 45.6% on the other.
- Planner token usage dropped 12.7% and 8.6%.
- File- and symbol-level F1 improved in all 24 comparisons against GPT-5.5 and Opus 4.8 reference plans.
- Complete localization misses fell by up to 25.9 points.
The authors argue that evolving large agent harnesses is not just about generating edits, but also about finding where those edits should happen.
Related event: Harness Handbook Maps Agent Behavior to Source Code(2 posts)→
More from coding & agent
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11