← In the News

Agents see the warning and report the wrong number anyway

Invariant-Aware Harness Enforcement to Protect LLM Agents from Silent API Failures · Sajib Acharjee Dip (Virginia Tech, Genentech), Brian Ouyang and Lala Motlhabi (Genentech) · arXiv, November 16, 2026

Machine-readable Download Markdown

The paper studies APIs that return HTTP 200 with a plausible but wrong result, for example by ignoring a misnamed filter. The authors found this in 11 of 15 public research APIs, with counts inflated up to 691 times. On their count benchmark, an unguarded agent reported a wrong number in 74.0% of faulted runs across seven open models. Checklist prompts, a reviewer model and Outcome Monitors barely moved that (72.3%, 73.8% and 72.2%). The authors' explanation: "models often see the problem and answer anyway." A judge shown the check's results flagged 82.4% of faulted runs, and agents still reported the flagged count in 77.4% of those runs.

Their fix, SilentGuard, runs invariant checks in the harness. One example: the count with a condition plus the count with its negation must equal the count without it. When an exact check fails twice, the harness withholds the value. That cut wrong answers to 1.7%, with no loss on fault-free tasks, and from 70.2% to 0.5% on three frontier models. "A warning from the same check leaves 70.1% wrong, so enforcement is the key." The authors are clear about the limits. The harness mostly abstains rather than recovering. On fault types written after the method was frozen, wrong answers fell only from 61.1% to 24.5%. The frontier-model logs were not released under company policy. Code and tasks are on GitHub.

Why it matters: Telling a model that a result looks wrong did almost nothing in these tests; taking the value away did. If your harness surfaces failed checks as warnings for the agent to weigh, this is evidence for making it block instead, and for giving the agent an explicit "cannot be determined" answer.