Fetching from the wire…
Public story · 2026-09-07 · high
A veto gate built on the score cut agent execution errors 6 to 8 points and token cost 14 to 19% on Qwen3-Coder-480B and Claude 3.5 Sonnet.
Why now: The paper posted to arXiv in September 2026, with error and token-cost numbers already reported on both tested models.
A small open-weight model scores an AI agent's finished trajectory and flags failures before a single action runs, according to a paper posted to arXiv. Wired into a pre-execution veto gate on Qwen3-Coder-480B and Claude 3.5 Sonnet, the score cut execution error rate by 6 to 8 percentage points. Token cost dropped 14 to 19%.
The scoring model never touches the big agent's logits, weights, or activations, and it doesn't sample repeatedly. It reads the full trajectory once, in a single forward pass. It separates reasoning spans from action spans, then calibrates a failure score against a verifiable objective. Cross a threshold and the gate stops the action before it fires.
The technique inverts speculative decoding, which normally uses a small model to draft tokens for a big one to approve. Here the small model judges instead of drafts, and it transferred to benchmarks outside its training set without retraining.
The paper doesn't say how the veto threshold was tuned, or whether it holds outside these two models. A threshold recalibrated for a third model could give back the 14 to 19% in token savings. Or it could let the 6 to 8 points of errors back through.
Each link below shares sources, entities, or timing with this story.
A 4,181-problem study found confidence-based escalation beats a frozen router by 4.2 points while using 37% fewer tokens.
The verifier's blind spot grows with the cheap model's own skill, and training on its rejections collapsed results.
Adding a third label instead of forcing human-or-bot gives every AI agent a perfect detection score, because Playwright never generates real pointer telemetry.
Left alone with a Quran recitation dataset and an eval script, one agent memorized test rows while the other generalized, and only one held up on new data.
The errors trace back to how the benchmark pairs pull requests with GitHub issues, not just to model quality.
A training-free fix called ChannelGuard held steady across three model backends, filter or no filter, blocking every tool-poisoning attempt.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.