Fetching from the wire…
Public story · 2026-07-30 · high
It logs each failure's trigger and fix, then rewrites only that record, leaving the agent's tools and context untouched.
Why now: This lands in the July 30 coverage simply because that's when the preprint surfaced, not because the failure mode itself is new.
Living-Harness rewrites an AI agent's setup after each finished task so a fixed bug doesn't return, per a paper posted to arXiv.
The paper targets one failure: an agent fixes an error mid-task, then repeats it on a later task because nothing carried the fix forward. For teams running agents across repeated tasks, that gap is the cost, not the model's raw capability.
The fix works through what the paper calls an Evolution-SOP, a domain-level process for updating two things after each run. One is episodic memory: what triggered the failure, what the failure pattern looked like, and which recovery action worked. The other is a state graph, built from nodes, repair edges, and transition rules, that routes the agent around the same trap next time.
Tools and the agent's base context stay fixed throughout. Only the procedural layer changes: no bigger model, no new toolset, just accumulated repairs. The authors tested this on eight environments from τ²-Bench and MultiWOZ-2.4, established agent and dialogue benchmarks, rather than building a new one for the paper.
Each link below shares sources, entities, or timing with this story.
Shared entity: Bench / Same source domain / Shared topic / Earlier coverage / Tension
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (action, agent, bounded).
Shared entity: Bench / Same source domain / Shared topic / Earlier coverage
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (action, agent, bench, context).
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (action, agent, harness).
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (agent, bounded, context).
Shared entity: Bench / Same source domain / Shared topic / Tension
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (action, agent).
Shared entity: Bench / Shared topic / Earlier coverage / Tension
Both cover Bench; overlapping topics (agent, context, harness); earlier Bench coverage from 2026-05-14.
Shared entity: Harness / Shared topic / Earlier coverage / Tension
Both cover Harness; overlapping topics (agent, context, harness); earlier Harness coverage from 2026-04-01.
Shared entity: Harness / Same source domain / Shared topic / Earlier coverage
Both cover Harness; reported by the same outlet (arxiv.org); overlapping topics (agent, context).