Abstract
AutoMedBench presents a comprehensive benchmark for autonomous medical-AI research that evaluates agent performance across five workflow stages, revealing validation as the weakest stage and highlighting the importance of reliable pipeline execution and verification in medical AI workflows.
Autonomous agents are increasingly expected to support end-to-end medical-AI research workflows, moving beyond isolated prediction tasks or short-form clinical question answering. However, existing medical agent benchmarks primarily evaluate final outputs, providing limited visibility into agent behavior within the research process. To address this gap, we present AutoMedBench, a workflow-aware benchmark for autonomous medical-AI research across diverse medical imaging and multimodal inference tasks, organizing agent execution into a unified five-stage workflow (S1-S5): Plan, Setup, Validate, Inference, and Submit. It comprises long-horizon tasks with each run averaging 33 agent turns, spanning five research tracks: segmentation, image enhancement, visual question answering (VQA), report generation, and lesion detection. Each task is evaluated under two difficulty tiers, Lite and Standard, which use the same data and metrics but differ in the amount of task-brief scaffolding, and each run is scored using both final task performance and S1-S5 stage scores, enabling stage-level analysis from the initial task brief to the final submitted artifact. Across thousands of recorded runs, stage-level scoring reveals that Validate is the weakest workflow stage on average, whereas Setup is the strongest, suggesting that current agents are better at making pipelines executable than at verifying their reliability. Post-run error analysis further shows that verification and submission failures dominate tagged errors, accounting for 37.7% and 38.1% of fired codes respectively, whereas task-understanding errors are rare at 0.9%, and runs with one fired error code have a 48% lower overall score than runs with no error code on average.
Community
-- Your medical AI agent didn't fail because it lacked medical knowledge. It failed because it didn't verify its own work.
A strong agent produces fewer errors and recovers gracefully from the ones it makes.
πOur Paper -- AutoMedBench, is now online: https://arxiv.org/pdf/2606.01961
π Leaderboard: https://automedbench.github.io
AutoMedBench is a long-horizon medical imaging + multimodal benchmark with 5 tracks, averaging 33 agent turns per run. Tasks come in Lite and Standard tiers and are scored across 5 stages: Plan β Setup β Validate β Inference β Submit.
Main finding: Validate is the weakest stage, while Setup is the strongest. Current agents are better at making pipelines executable than at verifying reliability. β οΈ
Error analysis confirms it:
π verification/recovery errors: 37.7%
π¦ deliverable/submission errors: 38.1%
π§ task-understanding errors: only 0.9%
Runs with one fired error code have a 48% lower overall score than clean runs.
βThe problem: Most medical agent benchmarks score the final answer. But real medical-AI research is a workflow, and failures are often hidden inside that workflow.
βThe solution: AutoMedBench provides the workflow-aware evaluation of LLM agents in AutoResearch tasks, and covering wild range of tasks from segmentation, image enhancement, VQA, report generation and lesion detection
π€ What makes AutoMedBench different:
AutoMedBench ranks LLM based on agentic and task scores, as:
- Agentic score: stage-level S1-S5 workflow scoring
- Task score: held-out medical metric for the final artifact
- Overall score: 0.5 * Agentic score + 0.5 * Task score
Furthurmore, AutoMedBench applies the combination of online LLM judge and determinstic score, where S1-S3 are judged from saved artifacts + execution traces; S4-S5 use deterministic checks for inference completeness and submission validity.
This makes the benchmark useful beyond ranking: it produces feedback signals for agent self-refinement.
Did the agent write a valid plan? Did it run a pilot? Did it inspect outputs? Did it debug and rerun? Did it submit the right schema?
βΌοΈ AutoMedBench tells us where to refine the agent, not just whether it failed.
Get this paper in your agent:
hf papers read 2606.01961 Don't have the latest CLI?
curl -LsSf https://hf.co/cli/install.sh | bash Models citing this paper 0
No model linking this paper
Datasets citing this paper 0
No dataset linking this paper
Spaces citing this paper 0
No Space linking this paper
Collections including this paper 0
No Collection including this paper

