Hanhua Hong, Yizhi Li, Luu Gia Huy, Jian Yang, Ming Zhou, Chenghua Lin
NLPCC Shared Task
Current LLM agents still fail to reliably reproduce published scientific experiments, with execution and result matching (not code writing) as the bottleneck, best system scoring only 49.64% overall on a new process-oriented benchmark.
NLPCC 2026 Shared Task on AgentActionBench: 150 papers (120 ML from ICML/ICLR/ACL/NeurIPS, 30 AI4Science), over 10,000 rubric items, agents run in a standardized MCP-recorded environment; scores from 3 participating teams plus a GPT-5.4-with-Codex baseline, evaluated by GPT-4o-mini on importance-weighted rubric pass rates across five workflow stages.
Best team scored 49.64% overall (46.69% ML, 61.25% AI4Science); the frontier baseline (Codex-GPT-5.4) scored only 24.19%; one team scored 7.03%. Execution (2.84-18.04%) and result matching (0.39-17.24%) were far below paper observation and plan writing, showing the gap is in running and verifying code, not writing it. Scope: 4 systems, 2 L40S GPUs, papers in a narrow ML/AI4Science slice, rubric scoring by a small evaluator model.
Authors concede GPT-4o-mini as evaluator may be unreliable, rubric evaluation cannot eliminate hallucinated judgments, and AI4Science coverage is preliminary. Unstated: only 3 teams participated, human annotation covers just 15 papers (10%), model-generated rubrics were validated only by correlation on that small subset (n=15) and distort stage weighting toward Code Implementation, and the overall numbers rest entirely on model-judged rubrics.
With 3 teams and a homegrown rubric pipeline judged by a cheap model, the 'current agents are far from reliable' claim rests on weak evaluators and possibly unfair or noisy rubric items; a single strong-lab system under prompt-optimization pressure could score much higher; correlations of 0.93/0.88 on 15 papers do not establish rubric validity at the claimed 150-paper scale; the benchmark may reward process-theater (logging the right actions) over actual reproduction.
Little or nothing yet in direct economic terms. The relevant signal is directional: agents that can write plausible code but not run and verify it will not yet displace lab-scientist or ML-engineer reproduction work, so any near-term AI ROI claims in R&D automation remain speculative for at least the next 12 to 24 months.
Technical Capability: Quantifies that the execution stage of agentic coding, not code generation, is the binding constraint, which is where capability work should focus.
Labor & Knowledge Work: Suggests research-engineer and scientist reproduction tasks are not yet automatable, tempering near-term claims about AI replacing experimental research labor.