Back to deep dives

Core Automation says transformers cannot continually learn and is automating kernel generation to find a replacement

  • AI For Science
  • AI Infrastructure, Compute, Chips, And Energy
  • Frontier Models And Capabilities
Thumbnail for Core Automation says transformers cannot continually learn and is automating kernel generation to find a replacement
Image: Sequoia Capital

Audio deep dive

Listen to this deep dive

Spotify

This Recap covers a Sequoia Capital interview with Core Automation founders Jerry Tworek and Rohan Anil, hosted by Sonya Huang and Pat Grady. It is about the founders' claim that transformer architecture now limits further progress because deployed models cannot continually learn from real work. It matters because Core Automation is building an automated research lab to search for a replacement architecture, starting with the GPU kernels needed to run new ideas efficiently.

Jerry Tworek says architecture has become the bottleneck after large-scale pre-training and reinforcement learningSource1:57

I think at this moment what the bottleneck is to better models and to smarter systems is the architecture itself. It is this moment to revisit uh the train we've been riding for the last 6 years of trying to add more and more parameters to essentially two of the same operations, which is MoE and and attention.

Tworek says the field has mastered large-scale pre-training and reinforcement learning. Most architecture work now makes transformers cheaper rather than more capable.

Current coding agents automate parts of his work but still need a person to choose, direct, and judge tasks. He believes more attention and mixture-of-experts scaling will not remove that dependence.

Higher reinforcement-learning benchmark scores did not solve messy real-world tasksSource5:48

I saw us training model after model. This model was getting better and better. All the benchmark scores were going up. And did we also solve all the real-world tasks at that moment? Unfortunately, unfortunately not. We we we we still have work.

Tworek expected scaled reinforcement learning to close the gap to AGI. Asked in 2024, he would have predicted AGI in 2025.

Benchmark scores improved without covering the full range of real tasks. He says training tasks and evaluations resemble each other, while production work is wider and messier.

Tworek wants models that learn during use without short contexts or catastrophic forgettingSource7:33

So my personal belief is we need to find an algorithm that we can we can meta learn, that we can express on the architectural layer, that can represent how does how does learning look like. How does learning look like that can work on much much longer horizons.

Tworek wants models to learn from users and their real tasks during deployment. In-context learning is short-lived; he says he often has to compact Codex after about 20 minutes. Continual fine-tuning can retain more data, but he says it is inefficient and causes catastrophic forgetting.

He wants a learned mechanism at the architecture level that can keep adapting over much longer periods. He also says alternatives may need substantial compute before their advantages appear, so small experiments can reject them too early.

Core Automation is pursuing transformer alternatives while frontier labs compete on current productsSource12:47

If Transformer is profitable and if you can spend more efforts and more resources scaling Transformer to win in the next quarter, it's very hard to put at least a lot of attention and a lot of energy to work on something that will that will maybe better or maybe or maybe will will redefine the field in a year or two.

Tworek says frontier labs are competing on current products and coding agents. A profitable architecture gets resources that a possible replacement may not.

Anil treats architecture as a decision about how to spend computation. Autoregressive generation adds one token at a time. Core Automation intends to work across architecture, training, optimization, kernels, and hardware because a better model is useless if it cannot run efficiently.

Transformer depth grows through serial token generation and still depends on retrainingSource19:11

if there are there are new types of tasks, if there are new code bases, new tools to use, transformers are getting a lot of their usefulness and all value through the things that are that are valuable have to be present in in in in in in training.

Anil says chain-of-thought reasoning adds computational depth through a longer token sequence. Stronger results therefore require more serial generation.

Tworek says pre-training can compress existing knowledge and reinforcement learning can install known workflows. The model still depends on a lab to retrain it as events, tools, codebases, and tasks change.

Tworek says reinforcement learning is only one form of learning from experienceSource23:22

When I when I when I learn mathematics, it's very different type of thing. It's it's like reading about hard concepts and thinking about them very deeply inside my head until until things click and I until until I have them connected. And both of those in some way are learning from experience.

Tworek treats pre-training as compression and imitation. Reinforcement learning lets a model generate experience and learn from outcomes.

He expects other methods because physical practice and conceptual learning use experience differently. Both are learning, but they do not follow the same process.

Anil says architecture and optimization must be designed together to use compute efficientlySource26:41

We should be looking at the end-to-end. What are we training these models for? Look at the outcome. Like for example, I train this model and give it to Jerry. Jerry will do RL and destroy all the perplexity metrics that I have created, right?

Anil says pre-training perplexity does not measure the final system after reinforcement learning changes it. He wants both stages optimized together.

A stronger optimizer can train architectures that a weaker one cannot. Anil also calls reinforcement learning inefficient because a long generated trace may deliver little feedback to the model.

Core Automation is designing its lab so a small team can run more experimentsSource34:24

the way you can do research today is very very different because a single researcher can do much more. In the end the speed of iteration the speed of research the speed of how quickly you can you can move through ideas and how quickly you can get data on your ideas is something something very very different

Tworek defines automation as giving each researcher more agency. Core Automation is organizing a small team and its processes around coding agents so it can test ideas faster.

His threshold for AGI is a model that can improve itself without humans in the loop. He says human-model teams work well today, while models alone have not taken over complete work loops.

The six-month roadmap starts with automating high-performance GPU kernel generationSource39:45

But it requires the highest taste human like there's maybe three people on the world to and spend about $100,000 on these coding agents over span of 4 weeks to get to a solution that's 60x faster. So these models today are no way close to getting that 60x faster kernel.

Anil says the first target is kernel generation. New architecture operations must run efficiently on GPUs before researchers can test them at scale.

He describes a QR-kernel result that required rare human skill, four weeks, and about $100,000 in coding-agent spend. He says it reached a 60-times speedup for the target case, which current models could not produce alone.

Core Automation wants to automate the path from an architecture idea to an efficient implementation, then search for systems that continually learn. Its test is whether the systems get better at doing the scientists' work from one day to the next.

Tags

  • Research Labor Productivity
  • Test-Time Compute
  • Post-Training