Understand this story
Google published a paper proposing OO-Harness, a method for evolving task-specific agent harnesses by task type. The method evolves harnesses along code-class lines: each specialized harness inherits from a parent class and changes only the parts that its task cluster needs adjusted; a router then selects a specialized harness or keeps the base result based on the base run's results. The paper reports that on AutomationBench business workflows, the method scored 77.41%, versus 61.62% for the base harness and 63.92% for the global method Meta-Harness; on unfamiliar applications, it kept the base harness and maintained a 59.18% pass rate, while Meta-Harness's global harness dropped to 44.90%. The authors recommend using the base harness as a fallback for mixed workloads and routing to a specialized harness only when a run exposes a known problem.
AI-generated from public reports
Latest development · Report
Google paper proposes OO-Harness: evolving specialized agent harnesses by task typeDevelopments
1 confirmed developments
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 22
Rohan Paul
Google paper proposes OO-Harness: evolving specialized agent harnesses by task type
A new Google paper proposes OO-Harness, which evolves agent harnesses by code class: each specialized harness inherits from a parent class and changes only the parts that its task cluster needs adjusted, after which a router selects a specialized harness or keeps the base result based on the base run's outcome. On AutomationBench business workflows, this method scores 77.41%, versus 61.62% for the base harness and 63.92% for the global method Meta-Harness; on unfamiliar applications it retains the base harness and maintains a 59.18% pass rate, while Meta-Harness's global harness drops to 44.90%. The authors recommend using the base harness as a fallback for mixed workloads and routing to a specialized harness only when a run exposes a known problem.