ReproBridge: Building Reproducibility into ML Research Artifacts

Yubo Wang, Rui Meng, Jaehyun Nam, Tomas Pfister, Jinsung Yoon

ReproBridge: Building Reproducibility into ML Research Artifacts: 32 upvotes on Hugging Face Daily Papers, #7 of 39 papers on 2026-11-10. Day-by-day upvote history.

Upvotes over time

It had 30 upvotes by its first day, 31 upvotes by the next day, 32 upvotes by day 3, 32 upvotes by day 7, and has 32 now. It ranked #21 of 133 papers in its week and #63 of 340 in its month.

Reproducing machine learning experiments requires reconstructing procedures from information scattered across papers, released code, and supporting artifacts. For coding agents, reproduction success can therefore depend on their ability to fill in missing details, rather than on the released artifacts alone. We ask whether preserving recovered procedures and decisions improves subsequent independent reproduction. We define a standardized artifact design comprising a refined codebase, environment setup, experiment launchers, and a reproduction guide, and introduce ReproBridge, an agent workflow for constructing these refined reproducible artifacts. ReproBridge-Bench provides 1,029 tasks from 387 experiments across 36 papers, anchored by five human-verified reference scores per task. Agents attempt tasks in fresh sessions with raw code or refined artifacts; a separate Auditor checks execution evidence. Across four evaluated models, refined artifacts raise mean reproduction success from 76.4% to 92.6% and reduce downstream API spending by 19.7% on average. The cross-model success-rate spread narrows from 21.6 to 3.9 percentage points, with all four models achieving mean success rates above 90%. Removing any component reduces success in the ablation study, with the largest losses from code and environment removal. These results suggest that preserving execution knowledge helps even models with lower raw-code success reproduce experiments more reliably and at lower API cost.

Paper page on Hugging Face · arXiv

Data: hysts-bot-data/daily-papers-stats and the Daily Papers API. Open data: tardellirs/paper-pulse-data. Sister project: Model Pulse, the download history of every model on the Hub.