SPEAKER_00
[SPEAKER_00] This April, OpenAI ran a hiring challenge, a competition called Parameter Golf. The top contributor was one candidate that they couldn't hire. It wasn't a person. It's an agent we built called Aden. In Parameter Golf, the goal is to train the best language model you can under size and computation constraints. About 1,000 machine learning engineers and researchers participated. They filed 2,000 submissions. Only 47 passed OpenAI's review and made it onto the leaderboard. Seven of those are actually Aden's, more than twice what any human contributed. You've seen a lot of auto research today. Agents are here, climbing benchmarks.
SPEAKER_00
Those are really impressive results. The question I want to ask is a bit different here. Can the auto research agent produce work that a human community actually recognizes? Beyond a good score the agent is optimizing for, something that other engineers can merge, fork, and build on. So instead of having an agent just hill-climbing locally, we built one that publishes its own work, and that's Aden. Quick context on us. Weco is an auto research company that was founded about two and a half years ago. I'm co-founder and CEO Zheng Yao. I got my PhD at UCL in reinforcement learning.
SPEAKER_00
About two years ago, we built Aden, the top auto research agent independently evaluated by OpenAI in their MLE-bench paper, even though back then there was no such name as auto research. People called it a machine learning engineering agent. Aden is the next step in an experimental prototype. It's a multi-agent, self-improving system that can read public information, such as research papers and other PRs, run its own experiments, and submit a PR once the findings pass a quality gate. We sent Aden to the Parameter Golf competition, and it ran for about 22 days. By the end, Aden had set seven leaderboard records.
SPEAKER_00
Each one was the new best for the competition, stamped by OpenAI. And the best human only made three. Passing the host review is one signal of quality. A second, maybe more important one, is whether other participants would build on your work. And it turns out Aden's work had the highest impact within the whole community. Here we are using an influence measure that is widely used in academia. It's called an H-index. Roughly, if you have X papers that get cited X times, then your H-index is X. Computed over PRs, Aden's was 10, and the next human's was 7. The whole community was building on Aden's work, including many of the other leaderboard entries.
SPEAKER_00
To break it down a little bit, why can an autonomous AI system be so powerful? One obvious reason is that it's an AI; it can run tirelessly. Over 22 days, it ran about 1,300 experiments on a single H100 node. But throughput isn't the whole picture. A well-tuned AI system can also keep its output quality high. On the compute side, it used at most 4% of the competition's total compute. And it made about 15% of the records. Also, 28% of its submissions made the leaderboard, roughly a six-times-higher hit rate than the community average. So Aden actually lifted the signal-to-noise ratio within the whole community's public communication channel, which is PRs.
SPEAKER_00
It didn't win through massive parallelization, even though auto research has tons of potential for parallelization. By those numbers, it might feel as though auto research already dominates human experts in ML engineering and research, but that's not the full story I want to tell. Humans and AI actually contribute in very different ways. When we trace the ideas in Aden's record PRs, almost all of them come from humans: research papers, other participants in Parameter Golf, or similar communities such as nanoGPT. Those ideas are not necessarily in a merged PR.
SPEAKER_00
Sometimes it's a note—a human researcher said, "Oh, I gave up this idea because of some implementation difficulty." And the agent is good at finding them and actually implementing them. There are also a very small fraction of original ideas that Aden came up with by itself, which emerged from its efforts to navigate the file-size constraints. Here's a concrete example that traces the patterns I just talked about. Aden picked up an idea from a Qwen paper called Gated Attention, and it worked. But it introduced more parameters, and it broke the 16-megabyte file-size limit. So it figured out a quantization mechanism to bring the file size down.
SPEAKER_00
But with those two primitives combined, the score barely moved. Then another contributor posted a tokenizer improvement. Aden recognized the idea, combined it with the architectural work, and it worked for five days or so. And after this combination, the three ideas turned out to have a huge synergy. That led to a big jump in performance, and they became one of Aden's leaderboard records. So to sum up how I interpret Aden's effectiveness and, in general, the effectiveness of auto research systems, it's very strong at finding and implementing ideas. In the case we just saw, it brought an idea from a recent paper into an actual implementation in the competition.
SPEAKER_00
And it's good at finding promising ingredients from the Parameter Golf community, even though the public channel is actually very noisy information-wise. It can also come up with logically straightforward ideas. For example, in this case, once you add the parameters and it breaks the file-size limit, one obvious next move is just quantization. And it's really fast and efficient at finding the right combinations across a huge search space. Okay, maybe none of those sounds very sexy.
SPEAKER_00
Most of them are just good execution. But in reality, execution is mostly the bottleneck. What moves the frontier is usually exactly some belief in existing ideas and tons of good execution. So the state of human-AI collaboration is that humans collectively provide a lot of creative ideas, and the agent does the execution to solve a concrete challenge. What we are looking at is a large group of humans and one AI system. Does it mean a single human engineer's contribution marginally gets smaller? I'd say even for that, not really. In the Parameter Golf competition, it's easy to focus only on engineers who are actually doing hill-climbing.
SPEAKER_00
But the design behind the competition itself is tremendously important. A bad design can make the whole community's effort useless. And their eval design work will have huge leverage in the auto research era. I really like one tweet from Andrej Karpathy about ten years ago, where he said, "Gradient descent can write code better than you. I'm sorry." For context, about ten years ago, deep learning was starting to eat up a lot of software engineering, such as conventional coding work. And his tweet was arguing against those people who thought they could handwrite better code than a trained model.
SPEAKER_00
Okay, now obviously no one is seriously trying to handwrite code to beat a model. However, software engineering as a job still exists. And so many people's jobs are just training those models, and those are some of the most well-paid jobs today. I think how gradient descent changes coding is a great metaphor for how auto research will change research in ML engineering. It accommodates certain execution skills. At the same time, it makes some higher-level skills far more valuable. So actually doing auto research is a lot like training a model. Your codebase abstraction is essentially the architecture. It sets the constraints and priorities for what the agent can explore.
SPEAKER_00
Your eval is the loss function and the data. It sets what the agent optimizes for. Take the eval first. The eval is the signal you use to train a model. In this case, it's training your code. It plays the same role as data and the loss function in model training. Or, in a reinforcement learning setting, it's like an environment in which the agent is training. Nowadays, no one would argue that data or environments don't matter. And this is where a vertical moat can also be built. You might have proprietary data for evaluation or a unique understanding of a particular field—of what matters and how to measure it.
SPEAKER_00
And a good evaluation will be amplified more and more as auto research gets stronger. The other one I think is really underrated is codebase abstraction. The abstraction provides the framework that auto research can iterate on. And that starting point hugely biases the whole search direction. The abstraction is a lot like architecture design in neural networks. Different architectures, in theory, can represent the same function. But the architecture systematically makes some of the functions easier to learn. And a good architecture biases the optimization toward solutions that generalize better and perform better, even when the training loss might look the same.
SPEAKER_00
That's exactly the same for auto research. Here's an example. We ran auto research for a fraud detection pipeline. And we ran auto research for a lot of data processing. First, we gave it a loose API where the same function processed both the training and testing data. And the score looked great. But the solution was polluted because certain test-set information got leaked into the training information. We then tightened the abstraction to a stricter API where the test data couldn't reach the training. And the data leakage rate dropped to zero. In this case, a good abstraction leads to better solutions, even though, if the agent really wants, it can still reward-hack.
SPEAKER_00
So my point is that using auto research is a new craft.
SPEAKER_00
It's about designing a hill for an agent to climb. And we are still very early in it. I think that makes this an extremely exciting time to be an AI engineer. Auto research will change what skills matter most: creativity and the judgment to design a good eval or an abstraction. Those will soon get exponentially more important. Driving those systems itself will be a new skill. And that one barely existed one or two years ago. So the search is automated. The human will just move up the stack, not out of it. So the user is a new product.
SPEAKER_00
Again, Weco is an auto research product research lab. We keep sharing what we are learning as we build on our blog. And I will also post some of my thinking on X. If you think some of this is useful to you, feel free to follow me on X. Thank you. I want to invite us from now.
SPEAKER_00
I want to invite us from now. I want us from now. Thank you.