UC San Diego's AIBuildAI Tops OpenAI's Kaggle Benchmark With 63.1% Medal Rate
A hierarchical multi-agent system from UC San Diego tops MLE-Bench with a 63.1% medal rate, matching expert Kaggle competitors across 75 tasks.
PRO- AIBuildAI ranks first on MLE-Bench with a 63.1% medal rate across 75 Kaggle tasks.
- Uses a hierarchical architecture: manager plus designer, coder, and tuner sub-agents, each an LLM agent.
- Beats 26 baselines including R&D-Agent, ML-Master, AIDE, AIRA-dojo, and MLEvolve on the leaderboard.
- Achieves 77.3%, 61.4%, and 46.7% medal rates on low, medium, and high complexity splits respectively.
- Runs on a single A100 with a 24-hour budget using Claude Opus 4.6 as backbone LLM.
- Code released at github.com/aibuildai/AI-Build-AI; main limitation is heavy token consumption.
A research team at UC San Diego has released AIBuildAI, an autonomous agent that takes a task description and a training dataset and hands back a trained model plus an inference script. It just claimed the top spot on MLE-Bench, OpenAI's benchmark of 75 real Kaggle competitions, with a medal rate high enough to place it above every prior autonomous ML engineering system on a suite curated to test real-world skills like training models, preparing datasets, and running experiments.
The headline number is 63.1%. When MLE-Bench launched, the best setup at the time was OpenAI's o1-preview with AIDE scaffolding, which earned a Kaggle bronze medal in 16.9% of competitions. AIBuildAI nearly quadruples that, and the authors argue it matches the capability of experienced human AI engineers.
Why AutoML kept hitting a ceiling
Building a competitive ML model is not one job. It is a sequence of very different jobs: sketching a modeling strategy, writing and debugging the training code, watching the loss curves, tweaking hyperparameters, and then ensembling whatever survives. Classic AutoML tools automated a slice of that pipeline, mostly hyperparameter search and model selection inside a predefined space, but they still required humans to define the search space and glue everything together.
The newer wave of LLM-based coding agents like AIDE, AIRA, and MLEvolve reframed the problem as a search over code. Each candidate solution is a script, and a single LLM call mutates one script into a slightly better one. This works, but it caps how much can change in any given step. AIBuildAI's authors argue that a single call cannot hold enough context to redesign an architecture, debug a training loop, and re-tune hyperparameters all at once. Their fix is to stop treating solution refinement as a one-shot code diff.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.