Latent Space ★ 81 4 min

Academia is for Ambition — Alex Zhang, MIT

🔗 https://www.latent.space/p/rlm

📌 MIT學者談RLM:模型外的「哈尼斯」才是關鍵

TL;DR:Alex Zhang從GPU kernel優化談到遞迴語言模型與代理群,核心論點是包裝模型的系統設計才是能力上限所在。

如果現在的前沿模型其實還有大量能力被浪費在原始的系統設計裡,那麼真正的突破點,或許不在下一個更大的模型,而在包住模型的那層「殼」。

🤔 從GPU Mode到RLM的研究路徑

Alex Zhang是MIT博士生,同時活躍於GPU Mode社群(前身為CUDA Mode,由Mark Saroufim、Andreas與Jeremy Howard發起,最初是一個教人寫GPU kernel的Discord)。他在Snapchat實習、對推薦系統工作感到無聊時,因為嘗試為Google的Infinite Attention論文寫專用kernel而加入社群,進而參與催生了KernelBench,一個測試LLM能否自動化生成GPU kernel的基準。Latent Space這次專訪延續他們挖掘「新星博士生」的傳統,前兩年分別介紹了後來打造OpenAI Operator、現任騰訊首席AI科學家的Shunyu Yao,以及共同創辦估值6億美元Engram的Jack Morris。

🧩 RLM:讓模型自己管理上下文與子代理

今年稍早,Zhang提出的Recursive Language Models(RLM,遞迴語言模型)概念在社群內引發討論,核心想法包括context offloading(上下文卸載)、程式化的子代理呼叫,以及共享記憶的持久子代理(persistent subagents)。根據Latent Space的描述,一個基於RLM的任務執行框架是最早「近乎解出」ARC-AGI-3的方案,時間甚至早於OpenAI的Astra。訪談中也談到Prime Agent、持久化的代理間溝通,以及一個更激進的想法:未來你所查詢的「語言模型」,底層可能其實是一整群看不見的代理(agent swarm)在協同運作,只是對外呈現一個簡單的介面。

💡 代理群背後的規模與浪費

Latent Space提到OpenAI曾做過一次上萬代理(10,000-agent)規模的實驗,輸出token量達1,300億(130B),相當於投入約4,000萬美元等值的運算去解決問題。但對談中也點出,這類大規模代理群當中很大一部分搜尋其實是浪費的,讓多個代理的結果收斂(convergence)仍是困難的問題。訪談同時比較了Kimi與OpenAI在多代理系統上的不同取向,並提及Sakana AI在開放式(open-ended)生成與「從大量產出中找出隱藏寶石」方向上的探索。另一個被提出的觀點是「能力過剩(capability overhang)」:現有前沿模型可能已經具備遠超目前任務設計所釋放的能力,推測性的程式化工具呼叫與重疊工具執行等做法,都是試圖把這部分能力榨出來的方向。對談最後也拋出一個開放問題:英文、程式碼、還是某種全新的「Neuralese」,才是真正限制模型推理方式的語言載體。

🎯 給工程師的啟示

Zhang的核心論點值得工程團隊借鏡:Claude Code、Codex、Pi這類工具在結構上其實相似度很高,真正拉開差距的往往不是底層模型,而是任務執行框架(harness)的設計,也就是它如何做組合式的泛化(compositional generalization)。與其一味等待更強的模型,不如投資在如何設計更好的上下文管理、子代理協作與任務邊界。

🔗 來源

#RLM #RecursiveLanguageModels #AgentSwarm #GPUMode #KernelBench #AIAgents #LLM #MIT #CapabilityOverhang #AIResearch

原始資料 Latent Space · 收集於 2026-10-02
來源原標題
Academia is for Ambition — Alex Zhang, MIT
作者
Latent Space
原始標籤
blog
原始連結
https://www.latent.space/p/rlm

摘要原文

Last call for regular tickets for AI Engineer NYC ! As an exclusive for Latent Space subscribers, the first 30 of you can take a 30% off code if it helps - for new tickets only, no refunds! See you in 2 weeks! While we tend to cover industry on the pod, every so often we celebrate a clearly emerging superstar PhD. In 2024 we featured Shunyu Yao , who went on to build Operator at OpenAI and is now Chief AI Scientist of Tencent . In 2025 we featured Jack Morris , who went on to cofound Engram at $600m and is now a leading voice on continual learning . This year we are proud to feature the work of Alex Zhang of MIT. From GPU kernels and KernelBench to Recursive Language Models , Mismanaged Geniuses , and massive multi-agent swarms, Alex Zhang is exploring how much capability we’re leaving on the table by wrapping increasingly powerful models in primitive systems. RLMs took over the timeline early this year: and an RLM based harness was the first to ~solve ARC-AGI-3 before OpenAI’s Astra: and is even today, influencing new research that has more extreme implications than RLMs: We go deep on GPU Mode and AI-written kernels, research taste and why academics should take bets industry labs won’t, GEV and alternatives to the standard autoregressive language model, and the idea of harnesses as compositional generalizers. Alex explains RLMs, context offloading, programmatic subagent calling, Prime Agent, persistent subagents, and why the “language model” of the future may actually be an invisible swarm of agents underneath a simple interface. We also discuss OpenAI’s massive agent experiments, Kimi swarms, open-ended research at Sakana AI, speculative programmatic tool calling, capability overhang, Neuralese, and where Alex thinks the next big research opportunities may lie. Why AI-generated GPU kernels still leave substantial room for human expertise How one expert insight can potentially replace enormous amounts of brute-force token search Why PhD students should take research bets that initially look trivial, weird, or pointless What SWE-bench, RLMs, ReAct, and Quiet-STaR reveal about research taste GEV and why a language model does not have to mean an autoregressive text-to-text decoder Why Claude Code, Codex, and Pi are structurally more similar than they look How harness design can improve compositional generalization across tasks and domains RLMs: context offloading, code execution, recursive subagents, and shared memory Prime Agent, continual harnesses, and persistent agent-to-agent communication Why the model you query in the future may secretly be an entire swarm or scaffold OpenAI’s 10,000-agent experiment, 130B output tokens, and ~$40M-equivalent problem solving Why much of an agent swarm may be wasted search — and why convergence is still hard Kimi versus OpenAI and different approaches to multi-agent systems Open-endedness, Sakana AI , and finding hidden gems in enormous amounts of generated work Why current frontier models may already have a large capability overhang Speculative programmatic tool calling and overlapping tool execution with generation Whether English, code, or an entirely new “Neuralese” constrains how models reason AI for science , fast-moving benchmarks, and how Alex chooses what research problems to bet on Website: alexzhang13.github.io 00:00:49 GPU Mode, KernelBench, and AI-Written Kernels 00:07:38 Human Expertise vs. Brute-Force AI Search 00:13:20 Research Taste and Taking Big Bets 00:19:28 GEV and Rethinking the Language Model 00:29:03 Video Game Agents and the Harness Problem 00:31:01 Why Claude Code, Codex, and Pi Are So Similar 00:36:42 Harnesses as Compositional Generalizers 00:52:01 Prime Agent and Persistent Subagents 01:00:30 OpenAI Swarms and the Future of Language Models 01:07:26 Open-Endedness and Sakana AI 01:15:52 Kimi vs. OpenAI Agent Swarms 01:20:06 Capability Overhang and Speculative Tool Calling 01:28:19 Neuralese, Future Research, and AI for Science Swyx [00:00:00]: All right, we’re here in the studio with Alex Zhang, I guess most famously of, RLMs, but you have a few other affiliations. Welcome to the show. Alex Zhang [00:00:12]: Yeah. Thank you for having me. Swyx [00:00:13]: Yeah. I guess GPU Mode as well? Alex Zhang [00:00:15]: Yes, GPU Mode as well. Swyx [00:00:16]: You were shepherded in by Mark Saroufim. Not everyone gets that kind of welcome. Alex Zhang [00:00:19]: Yep. Yeah. Yeah. I’m very close to all the people in GPU Mode, so yeah Alex Zhang [00:00:23]: We often end up working together in various capacities, like even beyond just GPU Mode itself, so. Swyx [00:00:29]: Yeah. Can we explain, so people who are not that close Don’t know about this. It’s just a-- it’s a Discord. It used to be focused on, I guess, CUDA Mode, and then generalized a little bit. it was started by Mark. Swyx [00:00:42]: It was basically like. To me, it’s like the hiring pipeline of the PyTorch team. Swyx [00:00:45]: And then you left PyTorch. Alex Zhang [00:00:49]: Yeah. So it used to be, I think, it started actually around when I was in college, in like 2023. I think it was started by Mark, Andreas, and Jeremy Howard. The original premise was just like, it was a GPU-- or it was a Discord dedicated to learning how to write GPU kernels, and they had, like, lectures. That was basically the extent of it. and I got interested in it because I was writing GPU kernels. It was actually out of, like, pure chance. I was interning at Snapchat at the time, and Alex Zhang [00:01:23]: Yeah, I was very bored with Rexis. So, they had a project where, like, they were interested in writing. It was this paper called Infinite Attention. It was like a Google paper. Swyx [00:01:35]: Yes, we’ve covered it on Paper Club. Alex Zhang [00:01:36]: Yes, yeah. So I was interested in whether or not you could write specialized kernels for it at Snapchat. it didn’t. Nothing really came of it, but I joined GPU Mode. At the time, it was called CUDA Mode, I think for, like, legal reasons or something, they changed the name. But I met Mark, I met Matei, I met a bunch of other people that were very involved in the community. And then Mark had pitched this idea called Popcorn, which was now what you see as the leaderboard today. But the general idea was like. I think all of us had this, like, intuition that GPU programming is, like, very similar to if you guys have done, like, competitive programming. It’s a, it’s a not. I don’t mean to say, like, they’re transferable skills. Swyx [00:02:17]: You have constraints. You code golf a little bit. Alex Zhang [00:02:19]: Yeah. And there’s like. There’s actually a surprisingly small space of optimizations that people do. and there’s actually not that many kernels per se that people are interested in optimizing. And so we kind of had this thought that, like, if you had enough data, like, in the same way that Codeforces, there’s millions of problems. If you could do this with GPU code, like, you could scale and automate kind of GPU kernel development, which for researchers is a huge deal. ‘Cause I think one of the bigger bottlenecks. Like, if you look at, like, Mamba, for example, like, they release the paper with kernels because otherwise, like, you can’t really use it in any meaningful way? And not everyone has, like, a Tri Dao on their team. So we’re very interested in this. KernelBench kind of spawned from that too, of like, can we get LLMs to automate, GPU kernel code? And I think that was like a. It was a very fun time. It was like between college and my PhD, and yeah, I had a really pleasant time doing stuff with GPU Mode. Now I kind of just help with the lectures sometimes. I’m not as involved, and I think in general, like, we don’t have as many competitions as we used to. But, yeah, I still keep in touch a lot with everyone there. Swyx [00:03:27]: Is there a friendly rivalry? Because I think the previous community that used to do this was like MLSys, MLPerf Swyx [00:03:32]: Kind of thing.

由 claude-code/sonnet 自動生成