Probe-and-Resume: When and How to Evaluate Agent Execution
Test-time search can improve agent performance by exploring alternative actions and using a critic to select promising branches.
ProofPaper ↗
Key points
- We study this approach in terminal-based computer-use environments, which expose only a partial view of a large underlying state, and find that the Monte Carlo tree search (MCTS) configuration we evaluate does not significantly improve task success.
- We identify two sources of poor critic performance: the agent's observations omit environment state needed for evaluation, and intermediate states offer limited evidence of whether a trajectory will succeed.
- We study when to invoke a critic and what access to give it to evaluate a node.
- We call the resulting design Probe-and-Resume: when the agent claims to be done, the critic probes a fork of its state, and a rejected agent resumes where it stopped.
Sources (1)
- [1]Probe-and-Resume: When and How to Evaluate Agent ExecutionarXiv (AI, ML, NLP, CV, robotics, multi-agent) · Oct 15, 01:42 AM
Test-time search can improve agent performance by exploring alternative actions and using a critic to select promising branches.
We study this approach in terminal-based computer-use environments, which expose only a partial view of a large underlying state, and find that the Monte Carlo tree search (MCTS) configuration we evaluate does not significantly improve task success.
Extractive summary: sentences quoted from the sources.
Before this
- Oct 15, 2026ARC-SORT: Adaptive, Robust, Compensated Multi-Object Tracking with Interacting Multiple Models
- Oct 14, 2026NVIDIA/TensorRT-LLM v1.4.0rc0
- Oct 14, 2026Beyond the Trial-and-Error Loop: Hybrid Projection and Automated Tuning for Distributed Training
- Oct 13, 2026Agentic Self-Awareness: Aligning Knowing, Acting, and Holding
- Oct 13, 2026Knowledge Graphs as Files: An Agent Harness Where Tool Creation and Tool Use Co-Evolve
- Oct 13, 2026Build long-horizon agents with Grok 4.7 on Amazon Bedrock