Trajectory-Level Speculation with Semantic Verification for Tool-Using Agents
SpecAgent has a weak model draft grounded tool steps and a strong model verify them in one prefill.
SpecAgent turns a strong model into a reviewer of tool-using steps drafted by a weaker model. The weak model executes read-only tools while drafting and holds the first environment-modifying action; the strong model verifies the segment in one prefill, commits the longest semantically valid prefix, and repairs the first rejected step. On tau-squared Bench it stays within one point of the strong model's success while roughly halving memory traffic and wall time, and it closes 44-75% of the quality gap on AutomationBench and VitaBench and 53-75% on MCP-Atlas.
- A weak model drafts steps and executes read-only tool calls.
- The strong model verifies a segment in one prefill pass.
- On tau-squared Bench, success stays within one point of the strong model.
- MCP-Atlas edge-cloud tests close 53-75% of the quality gap.
Full article280 words · extracted from huggingface.co · click to collapse
Large language model agents solve tasks through long sequences of tool calls, and the prevailing design has a single strong model generate every step, although many steps are routine enough for a much smaller model. Existing ways of sharing this work keep the strong model as the generator: routers and collaborative agents decide which model handles each query or step, and speculative methods check a small model's drafts one step at a time, usually against the strong model's own action. We introduce SpecAgent, a collaboration protocol that turns the strong model from the author of each step into a reviewer of steps drafted by a weak model. The weak model executes read-only tool calls as it drafts, so that every step is grounded in real observations, and holds the first action that would modify the environment. The strong model then verifies the drafted segment in a single prefill pass, commits the longest prefix it judges semantically valid, and repairs the first rejected step. Because verification replaces autoregressive decoding with parallel prefill, the strong model decodes only short verdicts and occasional repairs rather than every step. On τ^2-Bench, SpecAgent comes within one point of the strong model's success rate while roughly halving memory traffic and wall time, and on AutomationBench and VitaBench it recovers 44-75% of the quality gap while lowering both. In an edge-cloud deployment on MCP-Atlas with three cloud models, it closes 53-75% of the weak-strong quality gap while the strong model generates at most half as many tokens. These results suggest that a strong model need not author every step of an agent: reviewing grounded drafts retains most of its quality while cutting both latency and memory traffic.
Text extracted automatically; images, tables and formatting may be missing. Original: https://huggingface.co/papers/2610.21463