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
- Dev builds interactive 3D product experience with GPT-6 Astra + Hyper3D Rodin — nikola_mr64990 · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- 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