At each point the model has to write code to read the weights in with Python and some other Python code to perform analysis, like this: https://github.com/RikiyaT/lm_understand-logs/blob/main/exp3...
My complaint is that the post presents a confusing mix of experiments that imply capabilities that are more than the sum of their parts. This experiment 3 has nothing to do with experiment 1 for instance. In experiment 1 the model does read in the raw weights like it's reading an image.
Note that being able to both inspect raw weights and run Python code to perform additional analysis means the model has multiple possible techniques at its disposal (generally considered a positive, rather than a "confusing mix").
The blog post claims to show that frontier LLMs can understand and craft neural network weights natively. The experiments where the model completes coding tasks are not relevant to this conclusion. Those experiments require the model to demonstrate an analytic understanding of how a network might behave under various conditions, along with reasoning skills, coding skills etc. As a coding task this is a significant challenge. But it's entirely different from "natively reading and writing neural network weights".
Would you also consider it a benefit if there were experiments showing that a frontier model can download and run PyTorch, or write its own network and optimiser? That's another technique it has at its disposal to improve an ML model. It's just not one that's relevant to the paper's core claims.
You can let the AI generate training code for the next architecture too.
It's not like the AI is randomly losing its ability to write software just because it involves AI.
Even any small model update a company puts out is guaranteed top of HN