Agent harnesses should be retested every time the model changes
hugobowne · x · 2026-07-23
Hugo Bowne-Anderson argues that much of an agent harness is really a guess about what the model still cannot do.
His advice is to re-test compaction, retries, routing, and planning scaffolds every time the model changes, and remove anything that no longer improves the system.
The linked slide makes the point bluntly: yesterday’s necessary workaround can become tomorrow’s dead weight.
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