Jev: System One models for Prod, not God — with Diogo Almeida, CEO, TypeSafe AI
The definitive Jev podcast with its lead creator.
一句話總結
來賓
TypeSafe AI 創辦人兼 CEO,曾任職於 OpenAI 並共同執筆 InstructGPT 論文,是開創現代 Post-training 與 RLCD 範式的核心研究員。
節目筆記(英文原文,12 段)
Tickets for AIE NYC now open, and apply for the invite-only AIE CODE . Join us !
We have an unusual relationship with today’s guest: for years since coauthoring the InstructGPT paper , Diogo Almeida had been saying that API-available frontier models have been going down the wrong path, everything from the alignment to refusals to reliability perspectives, that we have dropped every mode other than autoregressive chat-tuned LLMs because of the overwhelming success of ChatGPT.
In a launch video now viewed ~40M times (by comparison, GPT4o was 22M , Fable 5 was 15M , Navier Stokes was 74M , and 6 Astra was 137M ), Diogo introduced Jev and it immediately took over the AI timeline — we’ll skip full Jev explainers because your favorite AI influencer/educator has probably already done one. We also collected:
Instead we’ll focus on what we can uniquely offer — a broader philosophical and mission-based understanding of how and why Jev was created , and what you should expect next in terms of future models from TypeSafe ( ReasoningJev ?) and what usecases and ideas you should work on vs the 55th low effort clone of Jev’s API or doing a generic JevBench benchmark - something Diogo has rejected publicly .
Diogo knows a good deal about RLHF, given that he was on the team that pioneered post-training at OpenAI — and traces the three branches to Christiano et al 2017 (the robot backflip demo), Stiennon et al 2020 (learning to summarize) and his baby, Ouyang et al 2022 (InstructGPT). From there on, every innovation from Function Calling to Structured Outputs to Reasoning felt like a hack on top of the string based, sequence to sequence prediction paradigm. As he mentions on the pod, from 2023-2024 he struggled unsuccessfully, due to both personal and organization underestimation, to train a model that accurately addressed what he saw as the core problem with making LLMs the heart of software: reliability .
Jev’s core innovation is " Reinforcement Learning for Calibrated Decisions ”, a novel, unpublished technique that optimizes for “answers with epistemically honest probabilities on System One tasks” rather than human rated feedback (RLHF) — which causes hallucinations, sycophancy, and permanent reliance on humans — or programmatically verifiable outputs with rubrics (RLVR) — which solves Navier Stokes but exacerbates jagged intelligence and doesn’t integrate well with other software.
We’ve talked about the calibration problem before on the pod, but probably the single best place to understand why RLCD became necessary is Diogo’s AIE talk , which discusses why a generation of training helpful AI assistants for humans has impaired them for training models for composable, programmable AI for automation .
At the end he also teases his contrarian opinion on scaling laws - which teases how to build a modern neolab without the billions of dollars the major labs have…
We spend a good amount of time discussing Diogo’s essay on the Bitterest Lesson :
His point is that “You get what you optimize for and the bitterest lesson in ML is that the most important part of it isn’t ML at all.” - and picking the right north star, eg upvoting for user preference vs being integrated into tool calls - makes everything else fall in line.
We’re excited to catch up with a freshly dyed Diogo to discuss:
Why AI can solve extraordinarily hard problems but still fail to automate basic work What System One Models are and why Jev is built for software rather than chat RLHF, mode collapse , calibration, and the hidden costs of optimizing for human preferences Why refusals become a problem when AI is buried inside software dependencies Why TypeSafe rejects public benchmarks and optimizes for intelligence per dollar The “bitterest lesson”: why the right task and the right data can matter more than compute Why TypeSafe thinks of itself as a data lab rather than a model lab RLCD vs. RLHF and RLVR as fundamentally different North Stars for AI Why reliability and robustness matter more than simple determinism Jev’s programming primitives and how intelligence maps into software control flow Why developers should decompose AI workflows into small, measurable decisions How structured state replaces giant prompts and system messages Why Diogo thinks AI should eventually disappear into the background of software The “inverse SaaS-pocalypse” and how AI could supercharge existing software System One vs. System Two intelligence and the limits of reasoning models Dark data, computer use, real-time intelligence, and Jev’s biggest early use cases Why Jev could reshape coding agents built around a single-model architecture Why Diogo says he wouldn’t pre-train with $1 billion The OpenAI journey that led to TypeSafe and why he thinks many neo-labs are approaching AI incorrectly Coding agents beyond the KV cache , shared state, sub-agents, and the multi-agent future
主要討論話題
Jev 的誕生與 System 1 定位
Diogo 指出傳統 LLM 與 RLHF 是為文字接龍或人類聊天設計,而 Jev 是第一個機器原生的 System 1 可程式化模型,以程式碼作為直接消費者。Jev 取名自 Jevons Paradox,核心目標不是單純壓低延遲或價格,而是在「每美元智慧(intelligence per dollar)」的 Pareto 前沿上達到極致。
RLHF 的隱形成本與拒絕問題
Diogo 認為 RLHF 為了迎合人類評分導致模式崩塌(mode collapse),迫使字串模型過度保守並破壞機率校準。更嚴重的是安全對齊帶來的拒絕(refusals),若 AI 作為軟體依賴項被呼叫,隨機拒絕就如同程式拋出型別錯誤(type error),這對背景自動化運作是致命缺陷。
拒絕公開 Benchmark 與數據實驗室
TypeSafe 完全排斥公開基準測試,因為這類指標極易被針對性洗榜,甚至各大實驗室都會刻意收集類似 MMLU 的資料來刷分。Diogo 強調他們自認是 Data Lab 而非單純的 Model Lab,遵循「最苦澀的一課(Bitterest Lesson)」,藉由高品質合成數據與正確的北極星指標 RLCD,針對認知核心的鋸齒性精準修補。
可靠性、穩健度與 API 原語設計
在系統可靠性上,Diogo 認為 Engineering 真正需要的是穩健度(robustness)而非死板的確定性(determinism),即相似輸入必須得到相似輸出。Jev 推出 choice、score、know(來自 Bernoulli 機率)三種原語,分別對應程式語言中的 switch-enum、排序閥值與 if 條件分支。
軟體解構思維與對抗大 Prompt
針對 AI 工作流架構,Diogo 強烈反對將所有規則塞入巨大 System Message 的傳統作法,因為這就像把所有變數宣告為全域變數並承擔 Context 腐爛風險。工程師應將複雜任務拆解成大量平行且極小的高語意決策單元,並直接以結構化 JSON 傳遞狀態。
Coding Agent 擺脫 KV Cache 枷鎖
目前主流的 Claude Code 與 Codex 都被綁在單一模型與不斷疊加的 KV Cache 機制中,無法落實軟體工程的狀態管理、抽象化與任務解構。Diogo 提倡利用低成本決策模型動態過濾歷史記憶、協調子代理(Sub-agent)讀寫鎖,打造全新的多代理分散式協作架構。
對你的啟發
拆解龐大 Prompt 為多個平行決策
不要將業務規則全塞進單一 System Message,應將問題拆解成最小語意單元的獨立 API 呼叫,不僅利於撰寫單元測試,還能避免上下文腐爛。
以機率閥值控制流程與人工介入
利用具備機率校準的模型輸出(如 know 與 confidence)設定明確閥值;在面對高風險或低信賴度情境時再回退或升級至人工審查,取代字串層級的模糊提示。
在長 Context 中以 ID 取代重複傳遞狀態
處理多步驟對話或大狀態時,為每條訊息附上 ID 並針對單一 ID 進行平行決策查詢,只需付費載入一次狀態即可大幅降低 Token 成本。
重構 Agent 狀態管理擺脫快取綁定
避免讓父任務與子代理共享全部對話歷程,應建立樹狀子任務結構,並透過低成本決策模型搜尋相關上下文以實現乾淨的記憶讀寫隔離。
金句摘錄
And refusal is just, like, obviously a type error.
而拒絕回答,很顯然就像是一個型別錯誤。
Like, I don't care how much smarter it is, it needs to be in the Pareto frontier.
我不在乎它變聰明了多少,它必須位在 Pareto 前沿上。
So m- the thing I've said i- before is if you gave me a billion dollars, I wouldn't pre-train.
我之前就說過,如果你給我十億美元,我不會拿去搞預訓練。
章節
- ▶ 00:00:00 Jev Launch Week and the AI Economic Revolution
- ▶ 00:02:50 What Is Jev? System One Models and Programmable AI
- ▶ 00:05:54 RLHF, Mode Collapse, Calibration, and Yann LeCun
- ▶ 00:10:29 Programmatic AI, Refusals, and Safety Alignment
- ▶ 00:17:21 Why TypeSafe Rejects Public Benchmarks
- ▶ 00:20:43 The Bitterest Lesson: Data, Compute, and the Right Task
- ▶ 00:24:59 RLCD vs. RLHF and RLVR
- ▶ 00:28:42 Why Powerful AI Still Hasn’t Automated the Economy
- ▶ 00:39:55 Reliability, Robustness, and Determinism
- ▶ 00:48:11 Model Versioning, LTS, Speed, and Intelligence per Dollar
- ▶ 00:54:04 Inside Jev’s API and Programming Primitives
- ▶ 00:58:28 How to Build with Jev: Structure, Decomposition, and Small Decisions
- ▶ 01:18:28 The Inverse SaaS-pocalypse and AI Disappearing into Software
- ▶ 01:33:21 Computer Use, Dark Data, and Jev’s Biggest Use Cases
- ▶ 01:38:48 How Jev Could Reshape Coding Agents
- ▶ 01:41:00 AI Safety, Frontier Pacing, and the Limits of RLVR
- ▶ 01:48:03 Why Diogo Wouldn’t Pre-Train with $1 Billion
- ▶ 01:55:19 The OpenAI Story Behind TypeSafe
- ▶ 02:01:41 Why Diogo Thinks Most Neo-Labs Are Getting AI Wrong
- ▶ 02:08:00 Coding Agents Beyond the KV Cache and the Multi-Agent Future
逐字稿
Introduction: Jev Launch Week and Developer Momentum
Okay, we’re in the studio. A special occasion because this week, Diogo, my good buddy, launched Jev, and it’s been taking over the complete timeline. How do you feel? What’s it like to be you right now?
Emotionally?
Yeah.
Never been worse. Like, I’m a ragged corpse of a person right now because there’s so much going on, and I’m like a technical CEO, so I have, like, a lot of fires to fight.
Yeah.
But mentally, I feel—I say this all the time, and I’ve been saying this kind of for years in my over-under events. Like, I feel like the entire AI field is like one of those, like, carnival house of mirrors, and everyone is just insane and saying the weirdest stuff that doesn’t make sense. And it feels like for just this week, like, I’m on a better in sync with reality and like, oh, people see it now. AI can be so much more than what was once thought.
And like, yes, we are going to make. Like, an AI-based economic revolution is back on the table, and this is fucking awesome.
I’m so jazzed the developers get it. It’s, it’s, Yeah, and I want to show my eternal gratitude to the developers and
Yeah.
I’m so jazzed about the community and everything. It’s so great.
Yeah, you were saying yesterday that you decided to prioritize the town hall and not a bunch of, like, VIP, investor-type people because you wanted to make sure that they are the people that you get your most, attention, right? The engineers, the developers.
Yeah, it felt a little like, oh man, I’m talking to, like, really important people right now.
Yeah.
I probably shouldn’t reveal who.
Yeah.
But it feels a little bit dirty for me to, I’m, like, perhaps overly genuine in things. Like, it feels, like, dirty if, like, in my gigantic calendar event of people to talk to, the community isn’t one of those.
Yeah.
And actually, in my ideal world, it would be, like, community all the time. I was thinking, “Should I host a town hall while walking to your studio?” And I’m like, “No, that’s too crazy.”
Sure. Yeah. Well, you guys have been hosting town halls on Discord. Discord is now 100,000 people. Your Twitter’s
I don’t follow these stats.
Yeah.
So holy shit.
Your Twitter’s blown up. It was, it was really funny ‘cause, like, at AIE, you were like, “Yeah, follow me please,” and then you didn’t, like, provide even your handle.
I’m a noob. I’m a noob.
You’re such a noob.
I’m a noob.
But no, but that, like, that’s, like, positive aura that, like
Cool
You don’t know how to promote yourself.
Yeah. Someone, like, called me out when I posted, like, “Holy shit, we’re all three twending-- trending topics.” And then they’re like, “That’s a personal feed.”
That’s a personal, yeah.
And I’m like, “Oh, no.”
Of course, of course it’ll trend to you.
Cringe. Yeah.
Yes, ‘cause it’s what you clicked on.
Yeah.
So okay. Let’s, Yeah, so congrats on everything.
What Is Jev? System 1 Models and Intelligence per Dollar
Thank you.
We’ll talk about more, details as you have them. But let’s, for people who are, like, living under a rock or just want, like, the definitive thing, what is Jev?
Whew. Let me think about. That’s a hard one.
Okay. And I’m happy to, like, re-ask if you wanna kind of
No. I’m happy to
Okay
I’m happy to, like, just jam on it.
Yeah.
I will say, like, the first thing that I’m relieved about with this question is now I don’t have to answer that question to my parents anymore ‘cause ChatGPT can just explain it.
Nice.
So the way I see it is we new-- need a new class of models. We’re not attached to naming that class of models. Our-- the most accurate name we’ve come up with is System 1 models.
Yeah.
There will be reasons, but it’s-- there’s a reason why we don’t call them decision models, because, like, they will be. Like, System 1 is beyond that. That’s all I can say. We didn’t expect this to be our big launch, so we have stuff in the tank.
You should have said low-key research preview.
It kind of was, right? It kind of was. But we. So there’s a class of models that we describe them as, like, machine-native, System 1, large programmable. I think these are-- is the class of models where the goal is for code to be the consumer. So as opposed to, lar-- pre-trained large language models, which are meant for, like, autocomplete of the internet, or RLHF models, like chatbot instruction-following models, which are meant to, like, reply to text, or RLVR. It’s in a weird gray area with RLHF. Like, these are meant to have things that directly are consumed by code, hence the name type safe. So the thing we really want is to have, like, AI, like, be as powerful as possible, and we think the way to do that is to integrate it with software. And we are designing everything, beyond just the outside, the deep internals of the model to be optimized for software. So number one, Jev is our first large programmable model, or a System 1 model, whatever you want to call it. Jev is meant to be optimized for intelligence per dollar, hence the name Jev.
Jevons Paradox.
Jevons Paradox, yeah. And it’s optimized for intelligence per dollar. I love this debate with people about what is the most important between reliability, cost, calibration, and speed. And Jev is meant to be. Jev will be the name of models that will be on the frontier of intelligence per dollar. There’s other ways to optimize it, like, ML, or at least if you’re good at ML, it’s all about trade-offs. And we are just going all out on that.
Calibration, Mode Collapse, and the Limits of RLHF
Yeah. And to me, like, calibration is one of the new things that people weren’t talking about as much. We’ve done an episode In the past, with Clementine Foreia of Hugging Face, where they were like, “Yeah, actually, y- they’re just.” Or, and this is your whole argument about RLHF, is they’re more collapsing towards what you want to hear the most
Ooh
Or what is most likely, instead of, like, their own internal confidence about a thing.
Can I soapbox on that for a second?
Go ahead. Yeah.
Cool. Like, I’ve been heard that your audience is the most technical, so I actually want to get into that.
Yeah.
And if- I went through extreme precision to make sure everything in our launch video is accurate and real. Apparently, that’s very unusual. One of the things that no one paid attention to was the downsides of RLHF, in particular mode dropping.
Mode dropping or mode collapse?
It’s the same thing.
Is that what you call it?
It’s the same thing.
All right.
And I wanna have a blog on this eventually, but I, like, want to tell as many people this as possible ‘cause I think it’s a very interesting thing. So the spicy take, I believe in Yann LeCun a lot. I think Yann LeCun’s takes are actually among the closest to
What about this?
Well, should I address this now or should I wait and go into mode collapse?
No, later. Go mode, go mode collapse. I don’t know.
So I actually think that among takes, Yann LeCun’s is among the most accurate. But he has this very famous/infamous slide about,
The cake?
LLMs are doomed.
Okay.
Like that one where he, like, has, like, a pie chart with, like, a tiny par-- tiny little thing- and says that as you increase sequence length, the probability of it making an error goes in. Yes, this one. This one. I love this one, because it’s one of these things that seems mathematically obvious, but is obviously wrong, right? Like, it’s mathematically obvious, but it doesn’t empirically hold. And this is my favorite thing to teach people about, like, where you
What’s the disconnect, right?
Exactly. And may I or you want to tell me?
About mode collapse?
Oh, no. Oh, so mode clop-- collapse is related to this.
Yeah.
The disconnect happens because if you are in a mode covering or a calibrated distribution, you are, like, not. You are not overly punished about having outliers. You’d expect, like, something. Some amount of the time you’d be out of distribution, some amount of time you’d be in distribution. That’s what happens when you cover the distribution. This was like models before GANs. They made blurry images, right?
Instead, GANs mode drop. They, like, drop the minority classes and just do the really common ones. And this is why this effect doesn’t happen, right? Like, instead of be-- in order to generate really long strings, without making errors, they need to, like, be extremely conservative because it’s e- really easy to see when an error happens. It’s very hard to see when, like, a subtle thing that looks correct happens. And that calibration is, like, total poison into, like, the probability distributions of strings.
Yeah.
And it’s, it’s a nuanced take and like, I think that This is why this doesn’t happen, and this is why strings are so bad at, decision-making or, overloading the string models are for decision-making is, like, a bad time.
Yann LeCun, JEPA, Scaling Laws, and Practical Research
And while we’re on the topic of Yann, do you agree that his fix i- with-- which is like a world model, like a JEPA-type, embedding thing is the right solve? So basically, like, the. One of the reasons that it could fail is because you’re trying to reason over token outputs and then, and then just looping back again and going. Keep, continuing going until you reach, like, a end of sentence. Like, is that, And his solve is JEPA, right?
Yes.
Which is, like, joint ambition,
Yeah
Joint embedding prediction. So like, is that the solve or, like, do you have a. Do you have a take on that?
Oh, man. I probably shouldn’t talk too much about the insides of ML, but I will say that my brand, other than unhinged, is practical.
Like, even my take here is practical. And like, I’m. Am I a scaling law fan? Depends. It dep-- it’s, it’s, it’s, like, it’s. Scaling laws tell you how much better you get at a thing for amount in.
A scaling law does mean exponentially more resources for normally sublinear gains, which looks to be a bad investment unless those, like, linear gains are, like, really valuable. But it’s all. To me, it’s all about, like, what can we do with what we have to make the biggest possible fucking difference? I can curse.
Yeah.
Yeah.
Yeah.
Yeah.
We’re, we’re, we’re approved for adults.
Hell yeah.
And also we have a scaling law thing if you wanna go into that later.
Oh, I could if we. See, that part is not super relevant right now.
Yeah.
I actually. If you wanna go into my bitterest lesson, I think that’s more relevant.
Okay.
But like, to me, I’m all about, like, pragmatics. And I think that the JEPA stuff is really cool early research. I really love awesome research. Is it practical yet?
Probably shouldn’t say. But like, there’s just a lot of.
I just think there’s just, like, so many diamonds in the rough let all over the research world right now that haven’t been polished because people don’t know how to, like, do the right task. And I think that what our launch did, it. Does it kickstart us as a company? Like, yes. Will it be great for us as a company? Yes. I think it’s gonna be, like, even greater for this direction of, like, programmatic AI. There was going to be, like, a gold rush on top of us for. ‘cause, like, software is super fucking charged. But I think there’s gonna be a gold rush parallel to us as well on, like, all the different ways we can expose things to make software more powerful so people can make even cooler stuff. And then we are back to, like, early internet energy?
Yeah.
And I think that’s why, like, the Twitter is just like, “Jev.”? It’s, it’s like. It is a party
It’s inspiring because it’s, it’s, like, so different than what we’re used to, which is, “I’m sorry you can’t do this, but we do scaling laws and only the big labs can do it,” right?
That. Actually, if I. I’ll, I’ll make a tangent if that’s okay.
Yeah.
I think you might enjoy this.
Really? Our five tangents in. It’s good. It’s fun. Yeah.
Oh, yeah. I get lost at all my tangents.
This is gonna be horrible for the listeners to figure it out, but they’re gonna figure it out. It’s fine.
Safety Alignment, Refusals, and API Philosophy
Yeah, we can edit it in post.
This is my response. Yeah.
So popular thing on Discord, that people keep asking me, I haven’t had the time to explain it yet, is why am I opposed to safety alignment and why do we not refuse? I’m not opposed to safety as a principle, but I think that safety alignment is generally misaligned with users. And refusal is just, like, obviously a type error. Like, if you’re a human being and you’re chatting with, like, a bot or whatever, you’re cloud coding, and a refusal happens, like, “I’m sorry, I can’t read DNA.py.” that’s an annoying time. It’s anno- it’s, it’s annoying
Right? But you can work with it, right? And you’re forced to work with it ‘cause of Stockholm syndrome.
I have stories about that too. I need another tangent deep in here. But like, if you ever want this in a dependency running in the background, what happens if that refuses? What if someone else is using that dependency? They don’t know what that system is. Like, you want the software to just stochastically break because a user sent, like, a weird message in there?
Like, that is, like, straight-up insanity. It’s coming from a place of, like, people who do not understand software, do not understand programming, and like, they are obsessed with, like, I believe this, horseless carriage of, like, AI coworker instead of unearthing, like, the full power of AI.
Fair enough.
Yeah.
You want something that is the core kernel that is usable everywhere.
Yes. Exactly. Like, the cognitive core, right?
Yeah.
And you need this thing to be s- like, so general, so optimized for its use cases. You want it to be, like, you want it to work on all the future use cases, all the weird shit that people are doing.
Yeah.
We obviously didn’t train on any of that stuff. Is it surprising that it works? No, ‘cause we trained on weirder stuff, my friend.
So. But one tangent up about, like, safety alignment.
Okay.
Safety alignment makes sense for a product, in my opinion, for, like, ChatGPT and Claude. Like, it, What safety, what makes safety and capability alignment different is capability alignment is, like, about doing what the user wants. That is sick for software engineers. They want their thing to do the thing, and the more predictable it is, the less they have to test it and play around with it. Jeb is not anywhere close to that yet. It could be, but like, there’s so many more nines of reliability that we want in order to make it so good, like a database query, that you don’t even have to think about it. It is just there when you need intelligence. But safety alignment is, like, the opposite of instruction following. It’s when you want to follow someone else’s instructions, like OpenAI and Anthropic
The RAGs value stack.
Exactly. And this makes a lot of sense for a product. Again, like, ChatGPT should do. Y- you sh- like, if they don’t want to, like, do, like, some, not-safe-for-work role play with ChatGPT, that’s on them because, like, maybe that’s, what their users who have, like, parents and kids want. Like, n- that’s fine. But in an API, that’s nuts, right? Like, that’s completely unacceptable because, like, people need to, like, program around this, and that is, that’s so anti-user that it’s. It. I’m. Huh. I can be an angry person, so I should try to calm down.
It’s, People get your passion, and I think that’s really good. The one pushback I’ll give you is, like, what if we use it to kill people, right? Like, that is the actual. Like, n- the not-safe-for-work thing, it’s private, personal, whatever. But like, yes, like, we will use it in war. And like, that is, something that companies can reasonably prefer their APIs not be used for.
I get that. I think that there’s, like, pragmatic places where that opinion can be held. I don’t think the foundation of, like, a general-purpose technology is that place, personally.
Like, would I prefer that our stuff is not used to kill people? Obviously. Would I prefer it’s used for, like, all sorts of, like, great stuff in the world? Obviously. Will I put my thumb in the scale for that? Yes. Will I do it at the technological layer? Absolutely not, because that will fracture the intelligence. Every single time you mean it to overfit to some weird stuff, you’re fracturing its intelligence more and more. And like, these things are fractured to the, like. They’re so darn fractured right now.
Yeah.
So and as a furthermore thing, to me, it’s like I think intelligence will be more like a database than a coworker. Like, I don’t think it’s up to databases to add checks on whether or not they’re used for, like, what’s something that’s not great? Like, CIA. Actually, I don’t know what the CIA does, really. You can imagine. You can imagine, killing people who are not even bad or whatever.
And like, I don’t think it’s the database’s responsibility for that. And furthermore, like, a thing that has been weird to me is when people, like, sign up for our thing on Slack and they’re like, “Hey, we’re gonna deploy this. Can we deploy this thing?” I am just like, “My brother, we are an API. You are a developer. It’s none of my business,” right? Like, you shouldn’t know what the whole task even is
Yeah
Because it should be decomposed into small things. We shouldn’t be able to know what the downstream users are doing, and that is, like, a good boundary to give software engineers maximum power. Ideally, they use it for the good stuff, and ideally, we can, like, help them and like, we’ve talked about, like, doing open source and charity and all of that. We have absolutely no time for anything else right now. But like, they will get any of that bias out of the technological layer as long as I’m in charge.
Privacy, Benchmarking, and Trusting Intelligence
Yeah, that’s great. While we’re on the topic, let’s also briefly talk about your privacy stuff, terms of ser- terms of use, which, got a little bit of
Ooh
Misunderstanding. I just wanna clarify that upfront.
Hell yeah.
I think this probably takes two sentences from you about, like, you will not. You’re not being that restrictive about your API. Like, clearly
Oh, yeah. Oh, yeah, so yeah
Ideologically, you articulate your role as a platform very seriously.
Yes. Yes. I don’t know what you’re referring to, but like, this was. I’ve seen a couple of things about, like, benchmarking.
Yes.
Like, obviously we’re not stopping people from do. Oh, man, I should be careful about what I say. I’m realizing
No, you said, you said it publicly that
Yeah
That was in the preview period. You didn’t take it out for the launch.
Yeah. Okay.
And now you’re gonna take it out.
So the team is doing stuff that
Yes
I’m not even aware of, so it’s great to know the team communicated that. I asked them to check in with the lawyers about that.
Yeah.
Like, we are obviously not stopping people from doing that type of thing. I’m extremely in favor. So I’m extremely anti-public benchmarks. I’m extremely in fa- I’m medium about private benchmarks that are proxies. I
So are you worried about, saturation or, like, training on public benchmarks? So it’s, like, easy to cheat.
Not only is it easy to cheat, there’s a lot of ins. So I think that we are. Or anyone who’s, like, competition with us that, vaguely there is. Like, you could say, like
There’s like 50 Jev clones, yeah.
Well, sure.
Yeah.
Well, the, these. Let’s say that there is competition.
And we’ll talk about those. Yeah.
Or let’s just say that there’s. Let’s just assume that there’s an industry two years from now of people who are doing similar things to us. The thing that we are selling is intelligence per something, per, like, dollar or per second. The. No one. Like, people obsess about the cost and the speed. I believe that is. It’s cool, but like, the thing that matters is the intelligence. Like, the cost and the speed are, like, are bad things. You’re paying them for something, and you need the thing back, and the intelligence is what truly matters. The problem with intelligence is that there’s a je ne sais quoi to it, right? Like, the good model smell. Like, the thing that happened after we launched of, like, two hours later that actually went way bigger than the video, which was like, “Holy shit.”
This is actually usable.
It. Well
Yeah.
It’s, like, beyond that.
Yeah.
Like, the. Whew, the launch was crazy, and people could really sense how hard we care about that, and that’s truly what I think the long term of this is. And I think public benchmarks are antithetical to this. Like, they are a way to get people trust in intelligence because intelligence has a je ne sais quoi, but the public benchmarks are extremely gameable. Even if they try not to, they still will. Like, back in the old days, every lab had a team to collect data that looks like MMLU to make it look better, which is just benchmarking with extra steps.
So I believe that in the long run, it needs to be vibes and trust until you put it into a workflow and evaluate it for that workflow and measure it and have your own sense of, like, how it does on the exact workflow that matters. And our job is to keep moving the nines of reliability. This is like an ever-present part of o- of what we need to be doing as a company, and we need to do everything to have people know that this is something we care so much about. Like, if we wanted to, we could have released Jev, like, a year and a half ago if we wanted it to be dumb.
The Bitterest Lesson: Tasks, Data, and North Stars
Oh.
It. Like, the. My bitterest lesson, right? Like, architecture and Yeah.
I’ll bring it up
Hell yeah
Since you, since you talked about it, here.
Hell yeah. T- like, Sutton says that algorithms beats compute very roughly. Data matters way more than compute, obviously. And doing the right task, having the North Star is the hardest, most important thing. This has happened, in LLM land twice so far, right? Maybe 2.2 times. There’s RLHF, which, like, shifted the task to instruction following. No one realized that was possible. RLVR did, like, a tiny little, like, edit to the, to the direction, and now us, right? RLCD. We have a new task, and the goal is, programs in the loop. And yeah, data matters so
Right
Unbelievably much.
So
Like, I can’t, I can’t emphasize it less.
Yeah, you consider yourself a data lab rather than, like, a model lab. Is that
Absolutely
Something. That’s the wording you guys use?
Yeah. We are. We will always, like, care so much about data. To me, model capabilities means data. Data is so unbelievably complicated, and that is what gets nines. Like, you have no idea how much data can shift everything. Data is so important.
TypeSafe as a Data Lab and Synthetic Data Strategy
Yeah.
Holy crap. So if people are looking for a job, we are hiring infinite data people, actually infinite.
What is a good data person? Like, clearly somebody who cares about reading through the transcripts of, whatever. You’ve said, for example, that y- all your data is synthetic.
Yep.
But that’s only, like, the scratching the surface, right?
Yeah.
Like, it’s not. Like, synthetic, so what, right? Synthetic, but we have people with a lot of taste and a lot of care looking at, looking at these, articulating what’s wrong, going back, regenerating. Is that what a good data person is these days?
Let me try to figure out how to. Like, it’s, it’s super complicated, and like, I literally onboard the data people with a Talk that I assume is longer than this podcast will end up being. So I will try to say, like, the high level of it. So number one, we don’t do the kind of synthetic data that people ki. Well, I’ll do. Actually, number is zero. Data and synthetic data depends on your task. Like, the shape of your data. The shape of your task changes the data. Like, RLVR’s data is kind of environments, right?
Yes.
RLHF’s is the human feedback? Each task has its own unique kind of data, and we, of course, have our own unique kind of data, right? So number one, we have that. Number two, the thing I. The reason why we don’t want to train on our users’ data, even if we could, right? Like, we could probably ask for any terms right now, and it will. We. I don’t know if it would make a difference. We truly don’t want that, because no matter what, the real-world data has so much bias. There’s, like, a power law of, like, people, like, asking the same things where you’ll end up, like, overfitting to it and like, fracturing to it and all of that. And number two, we are, like, aiming for, like, a complete sci-fi future years from now where, like, these models are going to be, like, the general infrastructure, layers and layers and layers and deep down the stack to, like, things people can’t even imagine. Like, I would like to think of our model, like, kind of like, UDP as LLMs and TCP as our models. All sorts of stuff can be built on top of that, and we need to be able to nail those futuristic use cases such that software developers can actually build that futuristic stuff. And the way to do that is even if we had all of the data of the present, we would just overfit to the present, and then it wouldn’t work. What we need is to, like.
It almost feels like a. Like, they’re the artists? They study this cognitive core. Our cognitive core is, like, way less jagged than anyone else’s. And then they find the jaggednesses, and then they address them surgically in a way that. And you can never perfectly do this, right? But they do it in such a way that it addresses it in every single possible, like, dimension, past, present, future.
The general case rather than the specific case.
Exactly. And like, that requires a lot of intelligence every time.
RLCD vs. RLHF: Defining a New Task
Okay, so we mentioned a little bit. You sort of criticized my thinking as r-- like, very RLVR influence, which is, like, very fair. Let us actually mention RLCD
Ooh
Which obviously you have some secret sauces to our knowledge. You’ve never actually published a paper or anything like that on it. No, right?
No, not yet.
But like, what should people get from this? Like, what. Can you give people some confidence that you’re just not just making up jargon for the sake of sounding cool, right? Like, one thing for me is, like, calibration I do think is a. To me, like, well understood because we’ve covered it in. On the podcast.
Yeah.
But I don’t know what you mean when you say RLCD versus what people are familiar with.
It’s a great question.
Yes.
And actually, I will give a related question.
Okay.
What is RLHF?
Okay.
Right? And actually, RLHF means multiple different things, right?
Okay.
Like, there’s the RLHF of the original. I think it was, like, Paul Christiano teaching a robot to backflip or something like that. Wasn’t there something
Was that it?
That was the original
I referenced the PPO paper, but I don’t know.
And so PPO was not necessarily from human feedback, if I recall.
Okay. That’s true
But I b- I believe it was, like, an OpenAI alignment work that could teach hard to specify outputs, like a backflip. I’m not 100% sure. And then there was actually learning to summarize. This was work, by a bunch of the team that helped with, instruct-- and co-authored, the instruction following paper, which was teaching, doing PPO on language models.
This is the, sorry. I’m trying to, trying
Yeah
Trying to manipulate this thing. This is 2017.
Yeah.
Right.
I’m not 100% sure, but like, that looks quite right.
Yeah.
If it has, like, a robot doing backflips or something like that might be it. Yes. Okay, cool. I guess I got it right. Hell yeah.
There you go.
Yeah.
That’s the one.
So the idea was can, like, can you do, like, ill-specified things with it? So that’s, like, version one. Version two was, the learning to summarize work, that, like, OpenAI did, which is actually, like, PPO on language models to do something somewhat ill-specified. This is, like, another thing that people refer to as RLHF Which I did not co-author.
Oh, Dario’s there. Cool. Hell yeah.
And Radford.
Yeah. Shout-outs to Alec and Ryan. Love them.
Yeah.
But the thing that I refer to RLHF is the, Oh, man.
I’ll get to
You have comments on that, yeah.
I have comments on that paper, but like, we’re so many, tangents deep.
Yeah.
So the thing that really got. To me, the thing that I’m calling to RLHF is the task of instruction following. It’s not about the PPO. That part doesn’t matter. It’s about, like, setting a North Star of this is a valuable direction. It’s kind of like the Bitris lesson North Star.
And for us, RLCD is this new task. And it is not. I don’t see it as jargon. Like, I try to communicate with precision. It’s just that, “Hey, here’s another North Star.” Just like DPO and all of its, like, descendants also do RLHF, despite not using the algorithm in that paper.
And so clear- clearly stating the North Star is, being program- programmable AI is one, word that I really catch onto, removing the human in the loop,
Yes
From. Because RLHF is tuning
Yes
For this so that you can automate everything.
Yes. Everything that makes
Did I miss anything else in the, in the thesis of, like, what the North Star is?
There is. That is. That is right. I’m overly nuanced in my communication. The one nuance is that we need to be practical. We need to be aware of what language models can do really well. Like what AI can do.
Right? Like, there could be programmatic types that are, like, sick AF, but if you. If the technology is not ready for it to. It’s not a tragedy if that’s not out in the world.
Why Programmable AI Matters
Yeah.
But to me, like, the pre-Jev world was a tragedy becau-- it sounds arrogant. Hear me out.
No. I strongly believe you.
Cool. It sounds arrogant, but like, I felt this way since long before I even had a company.
Yeah. I can, I can vouch that,
Yes, I’ve been talking about this for so long
You said this at All Around Her for, like, three years.
Yeah, I’ve been talking about this for so long. And I’ve been saying it because I thought it would have been easier. They say they do not do things because they. It. They’re easy. They. It’s ‘cause they thought it was easy, so
Yeah, exactly
Something like that. I thought it. This whole project would take a week.
And I was unbelievably wrong. So I am so sorry to everyone at OpenAI that I thought. I was like, “Man, I’m solving this right now.” but like, I think that the tragic thing is when. Well, I think overpromise, underdeliver is tragic too. And like, AI is super extreme on that axis. And I think RLVR is, like, the main. Well, both RLVR and RLHF are extreme perpetrators of this.
But like, it. To me, it’s like it’s just there’s just so much potential there. Like, AI is clearly so smart. I l- smart. I love this in my talks, when I ask people, like, “How can AI be so unbelievably smart? How can we, like, solve millennium prize problems in math, but still not automate even the most basics of works?” Like, really basic rote stuff that, like, the. It d- it doesn’t take, like, extremely smart people to do this. It’s not a satisfying job. Like, there’s other things these people could be doing, but yet we need them to do, like, this ba- like, super basic- non- unsatisfying stuff because, like, we can’t automate it yet, but we have this, like, supercharged engine of automation that just does not have, like, the right plugs and stuff to plug into all of this economically valuable work. And like, if the whole company of TypeSafe disappears, like, maybe it’ll take, like, a year or two for people to, like, truly catch up. I actually don’t know how long it’ll take. If model quality matters, then we are gonna be in a very good position for a long time. But it, like, it’s done, right? Like, there, like, this has changed the path of, like, technological history.
Yeah.
And like, we will be exploring that space as a field.
Yeah. I think, I definitely agree with that. You’ve created possibilities. So I think, if I can paraphrase so that people can un- also understand, you should not take the success of TypeSafe and Jev as just like, “Well, that is a new model type. Now we’re done. We go back to business.” Like, no. Like, actually, there’s, there are, like, five other model types that you should be exploring and like, let a thousand flowers bloom.
Absolutely.
Right?
Like, early internet
And some of that, some of which you will probably also build.
Of course, yes.
Yes.
Early internet energy. I think it’s back to tech utopia. It’s no longer like, “Oh, man, like, sometimes my coding agents work, but the, all of the best ones are hoarded internally.”
Yeah.
Right? It’s like creation is back on the menu.
? Though it’s gonna be a wild-ass world, and buckle up.
It’s. And I’m so jazzed about that.
Manifesto, Launch Strategy, and Early Internet Energy
Yeah. And now you have the funding and the momentum to do whatever you envision there, which I, which I think is, like, very gratifying to see you have after, so long of saying these things
Yeah
But actually show the world.
I know. I just. Such a, such an interesting thing to be a tease the whole time. Like, my talk, like, felt like it was a cliffhanger ‘cause I didn’t say how the automation would occur.
Yeah.
Sean reviewed our manifesto And he’s like, “It’s a little bit vague in these parts.”
And like, “What’s step one? What is, what is the intelligence model?”
Well, I asked you for model, and you were like, “Yeah, model coming.”
Yeah.
And like, Well, I just, I mainly objected to the word composable But build prod.god is fantastic.
Thank you.
Yeah.
I. We’ve really rallied around that. I’d like to think we’re not entirely a cult like some companies are.
But like, we are, like, jazzed about what we’re doing, and like, we are. Like, my brand is being practical, and like, we are all, like, so super-duper practical.
Yeah.
It’s really great.
Yeah. So here. And by the way, here is the step, the secret master plan, right?
Yep.
Shape, the shape of machine-native composable AI.
It was your idea to make a secret master plan, so
It’s a, it’s that Elon thing. When he started Tesla
Yeah
He was like, “Here’s what we’ll do.”
But I did. Yeah. I’m giving official credit to you.
Oh, thank you. Thank you, thank you.
Yeah.
Thank you. But like, you should’ve told me your, you’re also gonna do this model launch, ‘cause you, like, you told me, you told me half of the story, and then the other half, you didn’t have the doom demo at the time.
Yep.
You didn’t have any numbers to give me.
Yep.
I was like, “what?”
Well, the problem is I don’t believe in benchmarking.
Exactly.
Right?
Exactly.
So like, it is a thing that you need to feel, and like, I think that this is the way to build long-term trust, even though it, like, hurt, it hurt us a, us a lot? Like last year when we did fundraise, no one believed us.
? Like, and they wanted just benchmarks and stuff, and we’re like, “We’re not gonna do that. We are principled. We’re gonna stand by our guns. That rewards bad actors. I don’t give a shit, like, what you want. Like, this is who we are, and we are standing by that.” So Sorry. It’s not
No, yeah. Well, and in some ways, I think, like, choosing the hard path, it. But you end up making the company that you wanna work in.
Yep.
Right? Otherwise, if you sell out, then you’re just working in, like, OpenAI but with my people, right? Which is like.
Yeah. Yeah. Like, I’m, I don’t have too many regrets on that, obviously.
Yeah.
Like, it worked out so unbelievably well. And like, I, The. I was emotional last night when I was talking about, like, the reasons I left OpenAI, and because, like, it actually had to change my wording after the launch. My phrasing was, “If an AI winter did happen and I did not do every fucking possible thing I could to, like, avert that, I would see myself as personally responsible both for, the RLHF direction, which I think really widened overpromise versus under-deliver, and also not going all in on this because I think this is, this is where value is going to just be, like, printed.” So. And it was really cool because I feel like
The AI winter I’m worrying about is averted. Like, AI will be useful. It’ll be used for automation.
It’s been less than a week, and like, the numbers are already undeniable
Yeah
That it’s, like, being used for real work, and like, there’s. It’s, it’s the Wild West. Yeah.
Launch Traction, Tokens, Rate Limits, and Developer Usage
Yeah. Can you sh- just if you have top of your head, what numbers are you seeing? Like, what’s, what’s, like, signups? Like, whatever you can share.
I’m actually not super on top of everything. Like, the team is the ones who are telling me all of these things.
Yeah, and I’m sure it’s, like, changing every day, right?
It’s, it’s,
But like
It’s kinda nuts
If there’s a milestone that you’re like, “Well, yep, that’s one thing we were hoping for. We reached it.”
I will say a milestone that we’ve passed is tokens per day.
Nice.
And this is not, like, fleeting tokens per day.
Yeah.
This is, like, even at night, like, it’s constantly training, so machines are calling it and not just people trying things out.
So that is, That is so cool. A trillion tokens a day is a lot.
Yeah.
So surpassing that is awesome. Signups to me don’t really matter. And actually, this was, like, a bit of a mistake we made, if I’m, like, totally honest. People on Twitter were calling us, like, marketing geniuses and all of that, and that was just us. We don’t have a marketer. Also hiring. And we were just being our genuine, goofy, like, irreverent selves, and we were, we were just, like, offboarding people off the waitlist so hard. - Our platform team is so unbelievably cracked. I think we have more n- up nines of uptime than Anthropic while having the most Unprecedented launch ever. Like, that is kind of nuts, so
Yeah
Like, props to them.
Yeah.
And the thing we didn’t realize. So number one, waitlists, waitlist sign-ups don’t matter for, like, a developer platform, in my opinion? I would guess that a large number of them are not even developers. So they go in, they try some queries, and a lot of people don’t get it because they are not programming, right? Like, they’re just like, “What? This is not a chatbot. Where’s my ChatGPT 2?”
Right? But if, like. I haven’t exactly calculated this. My sense is that if every single human being in the world, like, just wrote a couple of queries, that would be a rounding error compared to, like, one power user’s for loop that is just, like, creating value.
Yeah.
And the thing we are-- didn’t realize with the waitlist is, like, we could just w- off-board anyone off the waitlist. It doesn’t matter. The scary part is rate limits. And then once people start getting value from that, then they just want tons and tons of rate limits because this is what software is, right? Like, you spend effort upfront to specify your rote task, and then this rote task creates more value than it takes to put in. And then now that you have that
Set it and forget, yeah.
Exactly, yeah. You run it in the background. You make it a dependency, to, like, other things. You can make, like, higher level stuff. And like, you just create so much value in the world. Early internet people probably did not imagine, like, the wonder of early 2000s internet, which is still not early internet. But like, it’s, it’s through, no offense, composability
No
That all of the crazy stuff happens, and I just really wanted to emphasize that in our manifesto. We are going for emergence. We are going for, like, being the catalyst. We’re wanting to empower people, and we are going to do whatever we can for that, be it, like, Discords in our town hall with me wearing a garbage bag or not.
And podcasts and Diogo Almeida [00:38:08]: Hell yeah
Getting all that.
Absolutely.
Like, ‘cause I want the long form, right?
Yeah.
It is like, yes, we’ll get past the, some of the superficial things, and then we’ll go deep and
Hell yeah
And people will really trust and understand your mission and like, the people that, will resonate that will end up joining you or, buying you. Or No, but sorry, as a, as a customer.
Oh, as a customer.
As a customer, as a customer.
Okay, yeah. That was funny. I’m sorry.
Sorry. I didn’t, I didn’t mean to say that. But no, any-- one version, one very flattering version of this, like, 36 million views of your launch video.
Cool. Up to 38 now.
Yeah, rounding error.
Yeah.
Navio still has got 74. Fable 5 got 57. So like, as far as, a- and I didn’t, I didn’t do the stats for, like, original ChatGPT, like
Yep
Which there was no video.
Yep.
So like, up there, right?
Yep.
Like, as far, as far as, like, if you were to launch a Neolab in 2026, I think you’re, like, number one right now, which is, like, pretty crazy.
Yeah. Well, I actually would rather. I do have the shirt, like, your favorites Neola-- favorite Neolab’s favorite Neolab.
Huh.
I don’t give a shit about being a Neolab. I think being a Neolab. Actually, we have a lot of, like, swag that’s being a parody of a Neolab. One of them, one of them I have is, like, Neolab with product, which actually is not a Neolab. Like, I don’t care about that, really.
Yeah.
What I care about is being a reliable dev platform. So Swyx [00:39:23]: Yes
Appreciate the comparison, but like
Yeah
Hopefully we transcend past them and we go back into, like, a thing-- like, a revolutionary moment for developers and like, this stable thing that people can rely on and trust.
Reliability, Robustness, and Determinism
Yes. To that end, I think that’s one thing that really impressed me about you guys is that, yes, you do talk about reliability. I thought it was mostly about calibration, which, like, we talk about RLCD. But actually it’s also about just, like, uptime and scalability and all those things, right? They’re, they’re all sort of the kind.
And nines.
And nines.
It’s, like
Which uptime is, in my opinion.
Oh, but that’s part of it. But like, there’s reliability in, like, how intelligent the thing is. Like, how consistently does it do the thing that you want? And I think that, like, the big reasoning models are very smart. In my opinion, they still lack reliability. I think there’s many use cases where you-- they look like they should be smart enough to automate their work. There is economic incentive to automate that work, yet still they’re not reliable enough as, at an intern because they’re optimized for different things. And so like, I think that there’s the reliability of being able to, like, trust the outputs. And also we are. Like, there are dimensions of reliability that we are not yet at that I’m, like, so excited by.
Yeah.
Like, I want to automate the easy work before the hard work? Like, I think that’s just a common sense thing to do. But to me, we will be sufficient. I don’t know if there’s such thing as sufficiently reliable, but I wanna get so good that people don’t even need to try the model to know that it’ll work. It’s like, that’s like what flow state is in programming, right? Like, I’m just, like, writing queries because I need intelligence in here. And like, when. For non-trivial branching, I can just write it in like a, like a type-safe System 1 query and then get the results out of it and it just branches accurately. Like, that would be so good. Like, that’s the. That is the dream.
Yeah.
And that is, like, going to be, like, a long slog.
Yeah. We’re gonna go into your API design in a little bit
Ooh
Just to give people examples and like, maybe paths not taken, that kind of stuff.
One thing up the front that I do wonder about in terms of reliability is I noticed that there’s no seed. There’s no, And so basically, same input, do I always get the same output?
So
And if not, why not?
Oh, great question. So this is actually, like, a common question we have between. So reliability is actually a catchall. Like, whenever AI can’t automate something, it’s due to some form of reliability. Could be, like, type safety. It could be determinism. It just could be, like, it’s, it’s jagged, right? So reliability is a catchall. I just think that it’s also a catchall for, like, what the North Star is. Re- determinism is, like, same inputs, same outputs. I do believe that this is, like, slightly interesting for unit tests, but I believe that to be the wrong North Star. I believe robustness is what people
I don’t wanna tell people what they really want, ‘cause that would be a little arrogant of me.
I believe that is, like, the more important property. You want, given similar inputs, get similar outputs. And it’s kind of wild how unreliable LLMs are.
Like, a way that we test this is you put, like, UUIDs in, like little
Yeah
I think they’re called nonces In the prompt. And what you want is similar outputs from all of those, ‘cause it’s truly semantically the same question, and that is the part where you really want. Th- like, that robustness is where, like, people get, like, burnt with AI making decisions. So I think that is the. A super-duper important property. We could also have determinism. That is, that is a thing that can be available. As far as I can, like, mentally model for programmers, like, it, I- it could be valuable for some use cases, so like, please educate me, in comments or view. But my. In general, it’s easy. Determinism is something you can, like, trade off for better cost. Like, we are, we are constantly wanting to be on the intelligence per dollar frontier. We are doing, like, absolutely disgusting things to be there. Like, this is,
I shouldn’t say this, but no one’s here to stop me.
If you s- you sign off on your own PR.
That is not how it works at this company. I believe for this week, my chief of staff, Kay, is the most powerful person in tech.
Yeah. And shout-out to Kay for organizing this.
Holy sh
Yeah.
Holy shit. She is so fucking competent and powerful. She’s incredible.
She sucks. Don’t poach her. But so I try to be a bit more filtered, but like, people are telling me, “Don’t call it a Frankenstein’s monster of models,” but because that has, like, negative implications. I think Frankenstein’s monster was, like, the good guy in this whole. It was innocent, right? I didn’t read it. Okay.
I’ll, I’ll confess. Okay. That. Well, one facial expression, I
This is a
My cards on the table
Decent Jacob Elordi movie if you wanna see
I
The adaptation. Anyway.
The. You have no idea how little time I have right now.
Yeah.
My priorities are sleep?
Developers.
Developers, yes. Developers. But yes. It. We do, like, absolutely disgusting things to be on the Pareto curve of intelligence per dollar, and we are going to keep doing that.
Yeah.
We’re gonna be doing crazy-ass stuff, and I think people really need to think outside of the box. Like, part of the reason we’re surprising is, like, people Are thought inside the box, and we continue to do that. As of right now, we are obviously the best at this, and we want to continue being the best at that whole thing.
Yeah.
So Wait, where did, where did we tangent from?
No. So
Yeah
I asked you about, will you have seeds and determinism?
Oh, yes. So
And then you basically defined reliability and like
And robustness
How you see it. Yes.
But like, determina- like
I have a robustness example that’s, that’s, real quick I can show you.
I would love that. I will just say one thing.
Yeah.
We can make a deterministic model.
Exactly.
Like, we’re hap- if people can convince us that is a valuable thing to do
Yeah
And we don’t have a gigantic GPU shortage
Yeah
We can happily make all of these models. We live to please. And rev- and revolt, revolute,
You will throw over everything, except you’ll do it in a nice way.
Yeah.
And find
So like, determinism could be on the cards.
Yeah.
It just gets you less intelligence per dollar.
Yeah. Well, just having seen the trajectory of OpenAI and Anthropic, you will. Just trust me now that you will be peer pressured into doing it. So like, just people will want it even if they. If you tell them they don’t need it. They’ll still want it. So like, yeah, that’s the TL;DR of that.
Okay.
Yeah.
I will love to. Maybe one day we will see how that happens.
Yeah.
I’ve been told I’m, They say that part of our brand is being unshakeable
Huh
And they say that’s just the nice way of saying stubborn.
Stubborn, yeah.
Yeah, exactly. And I’m a very stubborn person. I don’t think we could have done it.
Yeah.
Yeah.
No, but. So like, I. Okay, but I tr- I, like, have argued with you before.
Yeah.
And I know
And you’ve been right about developers every time.
So okay, I give up. You win. You win. I’m sold that I’ve argued with you before.
No, I’m just saying, like, I think that you can hold your ground while also, like, if I give you the right evidence, you can, not. You can sort of throw away your priors and be like, “Yep, like, that actually makes sense to me.”
Yep.
And so like, just trust your own gut on this.
Yeah. Yep.
I’ll bring up some
But I suspect, though, that we will be GPU constrained for a very long time.
Very long. Yeah.
And anything that has less intelligence per dollar means it consumes more GPUs
Yeah
For the same intelligence, which is. Like, our goal is not to onboard companies. Like, r- it’s, it’s valuable, but like, our goal is to have people, like, experiment and do weird shit. And we need, like. We need to, like, get, it to as many hands as possible and like, starting, like, the California gold rush for that.
Model Versioning, LTS, and Preserving API Stability
I think there is right now. Yeah.
Yeah.
Just a word of caution. I will just say it
Ooh, okay
Because somebody’s thinking about it right now.
Which is when you say things like, “We will not commit to deterministic models. We will, we’ll do whatever it takes for intelligence per dollar, and we are al- we are facing GPU constraint,” people are thinking you may quantize your models, right? Like s- like, whatever you had at launch, you may quantize down in. To reduce the quality, in order to free up, memory or bandwidth or whatever, right?
And so you should probably, have some kind of promise, which you don’t have to make now
Yep
About, like, “We will uphold model quality at launch.” People, like. So it’s like when people. When we. You were at OpenAI when you launched
Yep
All these, all these APIs, and even Claude as well. Like, when they first launched the models, the model strings, did not stay the same model at all times.
Yep.
Right? You have versioning in your models. That’s great.
Yep.
But like, you should, you should publicly commit to some kind of, like, once a thing is launched, we don’t change it.
We will not change our models when we deploy them. That is insane. We care about developers. Li- like, it makes sense if you’re. If. So- doing something like that, again, this is the problem with a for- first-party product and an API. It makes. You can do whatever you want in a first-party product, right? Like, more power to them, whatever gets that experience, that is fine. With an API, you obviously can’t do that. But I will say that we, plan to move a lot faster than many people are used to model providers, doing things. So we will be launching new models a lot faster than people think, and we are not promising long-term support for the models because we think that there’s lots of improvements to have. So there is a world that we might temporarily LTS what is right now Jev 1.13.0. We might do that ‘cause so many people are using it, and I know developers hate breaking dependencies. The alternative is fracturing our fleet, and that is a very bad vibe for everyone. It’s gonna be
Yeah, you can have, like, 100 different versions of the model.
Exactly. And if we’re iterating very fast, there would be a lot of those versions as well.
Yeah.
So we do want to have not just a LTS-supported thing eventually, long-term support. We want a really sick way of doing that. We have, like, research stuff cooking in that direction, and I think it’s gonna be the most pro-developer thing ever.
Yeah.
But it is not yet our current models, and I’m not promising that we will be able to keep the exact same models. They will get smarter every time, for sure.
Yeah.
And my sense is that even our model iterations, where it already is smart, it. Between model versions, the changes tend to be even smaller than the string models calling them twice. But when we go from, like, jagged to, like, wow, that is where the big deltas are.
Intelligence per Dollar vs. Intelligence per Second
Yeah. One thing, one thing that’s beautiful about LTS-ing models is that actually you can also port them to other silicon.
I don’t, I don’t know if you’ve thought about this.
No comment.
Okay.
So I care about intelligence per dollar.
Yes.
Right?
But speed.
What?
Speed as well.
We’ll see.
Yeah.
We’ll see. I
This is. This is a whole part of the inference tech tree that is, like, exploding in the past year, right?
Yeah.
Like, that you can, you can move to, like, a Cerebras
Yeah
An Etched or whatever and get, like, the 100,000 times speed up.
Yeah. Like, I think that intelligence per second is, like, a different metric, and we’ve even talked about, like, things like intelligence per dollar times second and like, metrics like this. My guess on, like, Jevons’ paradox occurring, or at least the Jev series of models, and the thing I, like, hunt people down about internally is, like, I don’t care how much smarter it is, it needs to be in the Pareto frontier. So like, that is what the brand of Jev is. It is the best thing at intelligence per dollar. For intelligence per second, we’ll see. I think that it’s an intriguing thing. I know that there’s many industries that are, like, extremely dependent on real-time stuff, and they will, like. Like, intelligence per second means tons of dollars for them. But
We’ll see. I’m, I would love to, like, do both and like, have the market correct me either which way.
Yeah.
?
Yeah.
Like, I would love to be informed by people.
Yeah, totally. And it’s not, it’s not just real- about real time, right? It’s also about scale because, at scale, every microsecond is just multiplied by billions and trillions of times.
It depends on how background it’s running, right?
Yeah.
Like, if it’s, like, a big background, like, database MapReduce query, the latency might not matter so much as, like, the cost
Yeah
To get intelligence from it. But like, if it actually is, something more real time, like user-facing, you have budgets, like between 100 milliseconds and one millisecond that are, like, totally magical. And actually, even if you were below 100 milliseconds, if you could half that time, that means you can get double the intelligence or sequential intelligence calls to have, like, a, like, a phenomenal experience.
Internal Evals and the Faster-Cheaper Frontier
Yeah.
So right, that is definitely happening right now. It is super-duper cool. I love the intelligence per second use cases, but I don’t think that will be Jev’s niche.
Okay. Yeah, fair enough.
Yeah.
When thinking about the promise of faster and cheaper Typically the other. The trade-offs that other models are offering is faster but more expensive.
Yep.
Right? And so you’re. Like, one of the reasons I was thinking about why is Jev resonating so much is that you’ve done the faster but cheaper side of the quadrant
Yeah
Which is very unoccupied
Yeah
While holding intelligence, like, somewhat constant.
Yes. It w- I-- That’s a very load-bearing statement while holding intelligence constant. That’s the hard part, right? Like
Which, unfortunately. Like, so basically, you refuse to have the, to, like, do any public benchmarks, or you don’t like any public benchmarks about it
But I will. I’ve actually tried
But you need some internal sense.
Say again?
You need some internal sense of this in- this
Oh, of course.
Yeah.
Of course. We have, we have our own internal evals, for sure.
Yeah.
But it takes a lot of discipline not to game those, and it needs to be, like, a top-level priority to not game them.
Yeah.
Of course we do that, right?
Yeah.
Like, how else can we make the guarantee that our models are in the Pareto frontier of intelligence per dollar?
Right? Like, we’re not flying blind in there, right? If we’re doing, like, completely weird things with different costs or whatever else, like, how do we compare them? We plot them and get. You. We try to figure out, like, what is the best for the users.
Yeah.
So we for sure measure them. I’m not anti-measuring. But it’s extremely dangerous when you have, like, any alternative incentive, and this is the one thing that I kind of rule with an iron. Well, maybe my coworkers might think I rule many things with an iron fist, but to me, like, not shitting ourselves, about how smart our model is one of the most important things there.
Yeah.
Like, we need to be truth-seeking.
Yeah. Yeah. Agree, agreed. Okay, I wanted to go over some, details on the, API choices.
API Primitives: Choice, Score, and Noulli
Ooh.
Mostly because this is the only podcast that will ask you these kinds of questions.
Oh, hell yeah. Hell yeah.
So you have three primitives.
Yeah.
Choice, score, know. First of all, know, where is that from?
Is this, like, a term in the, in the literature or what?
Now it is.
Yeah.
We debated this a lot. We debated this a lot. It is It is Bool-ish, right? Like true, false. It is
But it’s continuous.
Yes, exactly. So first, the origin of the name is Bernoulli.
Yes. So it-- that’s why it’s even spelled that weird way. That is, like, a subset of the name Bernoulli from, like, a Bernoulli probability, right? Which is actually what that is. So that is the origin of it. We were debating this a lot. We liked PBool, we liked Pool. We were wa-- we were wanting to call it, like, a pool party, but then no one let me. We had, like, a bunch of, like, other arguments about that.
And Noulli, we figured was, like, the best thing. Our rationale, and like, this is actually the same thing with Jev too, is that we think that we are, like, an irreverent, insane bunch, and programmers don’t care. Like, if Jev is just gonna be a string, we didn’t expect it to catch on or even have puns or anything like that, right? Actually, there was a lot of hate on the name internally. They’ve all apologized, except for one person.
Still holding strong.
Yes. Our mutual friend.
Okay.
Yes.
I respect her for that.
Yeah. Yeah. She wanted Jev to be called Meow.
She would, of course.
Yes, of course.
Okay.
Like her father, yeah.
You win there, you win there.
But like, yeah, Noulli is. We had to make a new concept for this thing ‘cause if it was a Bool, it would be confusing to people. So actually, all three of these are actually new concepts. These are not types that exist in programming, and that was intentional because they map very closely to types, but they’re not quite that. A score is not an int. So if you had, like, Instructor or Pydantic or whatever map ints or floats into scores You’d get a little bit cooked? And like, we were really erring on the side of clarity over the side of, like, making people, like, easily understand what’s going on.
Don’t you worry about that? Don’t you want things to integrate directly into things that people are already using?
Yes. Yes, we do. And actually, I think that,
You have integrations with, like, other SDKs and stuff.
Yeah.
But you have-- Sorry, you have your own SDKs.
Yep.
But typically, for example, as a developer relations person, I would be very obsessive. Like, yes, here is how you use, Jev with Instructor.
Yep.
Here is how you. That kind of stuff.
We might have that somewhere. I am so behind on everything.
Someone would do it for you in the community.
Oh, yeah. Yeah.
Not that you’re successful. People will be like, “Oh, that’s cool.”
Cool.
But like. Anyways
I don’t see that as binary either.
Yeah.
I actually see success as a score, and there’s always more to climb
Yeah
In, like, how much we can, like, be there for our community, just to be clear. And I’m. This section is stressful ‘cause I didn’t review the docs And they’re constantly changing.
Okay. But
But to me, scores do exist. So scores are similar to, like, LM judging.
Right? So like, if you want to call it, like, a judgment, I guess you could. But like, that is, like, the way people ca-- already use this type of thing, right? Like, maybe a Noulli could be, like, a probability, but everything for us is a probability. And a choice is actually closest to a function call, but a function call is, like, an extremely disgusting thing that, if you want OpenAI juice, sauce, tea, that. We should go back into that later. Like a, like, a choice is just, like, the right way of explo-- of exposing, like, a switch match statement
Yeah
Within code.
So it, like, maps cleanly to an enum.
Yep.
And you can choose to hydrate it into a function if you want.
Yes. And like, in the enum, choice is the important part of that.
Yes.
And like, actually, I think these map all into, like, programming primitives, where, like, choice maps into, like, a, like, a switch statement on an enum.
Huh.
Noulli’s mapped to if statements.
Yeah.
And scores map to sorting or thresholding at a greater than or less than.
Okay.
And this has been always what the vision is. Like, there will be more types, and they will map into programming primitives.
Yeah. Any other. So any nuance you wanna go through? For literally, this is for the Jev people who are, like, deciding to really invest in Jev. You are the expert, right? I’m just, like, wanting to provide more background for them on, API choices, how they should use some of these things, like legends, confidence, how critical in your testing, like, how. Like, just any sort of, like, pro tips that you, like, want to offer people
Structured Inputs and AI-Native Programming
Yeah
When they’re down at this level.
Thank you. I love this. No. This is
This is why we’re here.
Hell yeah. I didn’t expect this. And actually, I. No one has asked me this, in probably, like, months when I was, like, onboarding, like, our DevRel.
Okay.
So sick. So our model is designed for being, like, deep in the insides of computer programs in the future. We, like, unironically believe that this will be much more massive than anything people are even considering today. And our model might not be ready for that, but we are, like, continuously working for that future. It will never be good enough at these shallow tasks. Sorry. It’ll never be g- Like, we’re not just gonna cle- keep on climbing the shallow tasks. We want to be deep in the guts of programs ‘cause that’s how you make software powerful. All the s- all the types inside of our, This is an, actually an output.
But all the, all the parts, of, like, the input, like the state, the instructions, the criteria, all of them can be structured JSON objects.
That way, like, programs can, like, insert them in the right spot, and you don’t need to, like, put things into templates. Exactly. So if ever. I think people don’t read into this part enough, and they think it’s all strings. And that’s, that’s fine. But these are all meant. Like, I would say that if you’re using, like, a template, like turning it into, like, a system message or something, you are thinking in, like, the old way? We should be making things as easy for computers to understand because that structure is truly there, right? Like, it would be weird in, like a programming language to have, like, all of your numbers in, and then you pass it into, like. You turn it into a string. Normally, you do that for printing when you have a human in the loop, right? But for, like, within the computer, you want to be passing, like, nested structure that is semantic all around. And we are really gonna be optimizing our model. It-- the model’s pretty optimized for this, but the thing is every different nested level of structure is harder to reason about, and we want-- we are really cooking hard in that direction. I think people should keep cooking that direction because it makes the code, like, so much more legible and beautiful and like, agnostic to, like, the implementation details. It’s like, here is my state, like, here’s my function state. Like, think of, think of it as, like, an AI function. Which subsets of my state, which is, like, all the variables you have available, should I pass in here? System messages are, like, disgusting global variables where you just put everything in there, and you put all this
Slop, yeah
Instructions at once. And then like, you hope that every single instruction gets nailed instead of asking the questions in parallel.
Okay.
And also, I would recommend-- I, and I truly say this not from, like, a, like, it makes me money perspective. I truly recommend asking lots and lots of questions. Break them down, make them smaller, and like, really decompose. Like, no matter if the models can do it today or not, I believe that the biggest, like, saving grace of, like, what’s happening this week will be people’s code bases, AI code bases, are gonna be so much better. Like, if you decompose problems into simple decisions, every single one of these things is extremely evaluable. Like, a AI beforehand is big system message, and then maybe you have, like, another big AI
Decomposition, Verification, and Small Semantic Units
Big output, yeah
To see, like, if it actually does this. That’s nuts? It’s, it’s kinda crazy. Like, it-- that was our Stockholm syndrome, right? But like, that’s kinda crazy. Like, if you wanna say, like, “Hey, don’t read this subdirectory,” or, “Don’t pass any API keys to DeepSeek,” or whatever else, like, that should be programmatically basically guaranteed. And you’ll never have guarantees of any machine learning model, but like, by breaking it down, you can actually s-- you can actually measure it, right? Like
Yeah, you can verify that it was actually called
Yes, and like, our model, our model-- like, the interface itself is so verifiable. This should be like a sigh of relief.
Like, it’s, it’s, it’s, it’s just gonna lead to way better engineering.
Yeah. I think I get that. And so one of the reasons people didn’t used to do this in the past is because they would just call a small LLM, right?
Yep.
And it’s still too slow, it’s still too expensive versus chunking everything that-- I’ve done exactly this myself.
Yep.
Right? Like, I benchmark. Here’s a pipeline that throws everything in system prompts and it just gets one big output versus break it down into a hundred different things. It was slower, more expensive
Yeah
Not as good.
Yep.
Right?
And that happens-- yeah. It’s, and it’s, like, super inconvenient. It’s unwieldy. Why not just put it all together? You kind of end up repeating some stuff between
Yeah
Questions, so it’s, like, maybe, like, inefficient or something like that. But then it results in something that is very hard to rely on.
Yeah.
And software doesn’t need to run in the background. It would break my heart if our stuff couldn’t run in the background.
Is there a way to break things down that you guys have found that works versus, what you thought worked and doesn’t work?
Interesting.
Because, like, people are just gonna be exploring this, now that you’ve said it. Like, they would use this as a reference and be like, “Okay, like, that’s how I’m supposed to use Jev.”
Yep.
Then the question is, how do you break things down?
Interesting. I like to break things down into its, like, its smallest semantic unit.
Yeah.
Like, what is the lowest level thing? I try to never have. I’ve probably queried, the model the most, among anyone.
And like, I try to. Number one, in my, in my queries, this is, this is a lot more like the way I prompt things. Like, I make it really structured and explicit. And in the questions, I always. I like the back ticks, but like, it works for all of them? Like, be really clear what I’m referring to because we want the model to be really literal because when you program, you want things that instruction follow really well. That is what the art of programming is, and what AI does is expanding the things, the kinds of instructions that can be followed. So I’m a fan of doing that. I.
Sometimes I’m a little lazy and I, like, I have, like, more, like, hybrid things, but like, I think that for, like, really big production things, you just want to, like, keep on adding more questions, and you wanna make it really easy to add more questions. Be really precise about all of that breakdown and then have the code to have the exact behavior you want. If I could give, like, a tiny little example of this, is, like, refusals, right? Like, I’m not gonna talk about why we don’t refuse. I might have done that already.
Yeah, you did already.
It’s like all a blur. But like, for refusals, I don’t think you should ask, “Should I refuse here?”? That’s a really. It-- I think the answer will be pretty good because, like, that’s a System 1 compatible task. But I think you’re way better off, like, asking many different independent questions about, like, the different situations you can refuse about. Because instead of having to, like, just guess based on you can actually specify what you want. And beautifully, and I think this is, like, truly really beautiful, if you find a situation where it’s like, “Oh, it didn’t refuse because of this reason. I didn’t specify this part of the task,” that is awesome. That’s what software engineering is about. Like, you fix the bug by adding that question in, adding the threshold, maybe remembering that as a test case, and now it is just solved forever. Like, your software can’t forget about that, like, in the prompt because of context rot. It is just there, and you can, like, just keep measuring that forever. And if the models are not perfect at some of these things, you can choose what threshold you want for all of these factors based on real examples. It’s like, it’s like ML without the ML, and you can just do it for anything. And like, there might be some things the model’s not good enough yet, right? Like, I would. I’m a little bit afraid when I see people doing trading with the models, like,
Automated trading. It looks cool. I th- I just think that people should leave it to the professionals.
And like, that’s just a very hard, high-level task that maybe the models aren’t good enough yet to figure out.
Yeah.
Well, I, like, even if they were, then they would- It suddenly wouldn’t be ‘cause of efficient market. But like, that’s one of those things where, you can, like, break it down into things and just evaluate them, and you might be like, “It’s not smart enough at this. Maybe we don’t deploy it yet for this version.”
Yeah.
Or we make a trade-off, or we err on the side of safety, or like, “Hey, the models are not good enough at, like, detecting, like, this weird combination of, like, sarcasm with a VIP customer, that this is when we escalate to a human.” And that’s what confidence estimates are about, too.
Confidence, Thresholds, and Fine-Tuning
Okay. Very good answer. I think, one thing I’ll, I’ll mention very quickly, which, I don’t expect that you have as-- too long of an answer for is,
You don’t.
Well, no. It’s just, it’s just specifically, like, you are still relying on thresholding as, like, the lever that the user can pull.
But what if just the calibration is wrong, right? Like, you’re just saying your calibration is perfect, but
I didn’t say that.
I, like
Yeah. I didn’t say that.
So it’s like ca-- perfect calib-- and like, good calibration means, like, lower value is lower, like, sort of probability lower, higher value is probability higher. But it could be wrong. It could be
Of course, of course
Totally misaligned.
Yes.
And so then I would want to fine-tune it or something, right? Which you don’t offer, but you could. I
We could.
Again, see, this is a short answer
Yeah
Which is you don’t have it right now.
Oh, do we want to offer fine-tuning, is the question?
That could be, that could be one version of it, or you could have a different knob, right?
Yeah.
Where, like. Because, like, right now you’re-- all you’re saying is, like, if something’s wrong, a skill issue, you should, you should just change the prompt again or break it down even further, or you change the confidence.
Yep.
Those are my two options.
Yep.
Right? And that doesn’t feel super satisfying if your model is just getting it wrong.
Yep. And it will, it will get many things wrong, to be clear.
Right.
We have, like, a Report Issues button. Complain to us in Discord. We want to make it a lot better. Every single model version will be, like, notably better.
Yeah.
We will stop shipping them quickly if they weren’t getting big improvements. So number one, that is, like, totally reasonable. I think that’s simply pragmatic to admit that AI is imperfect at some stuff, right? I do think we’ll find use cases that they are, like, good enough at, and good enough kind of depends on the use case, right? Like, human beings can do a lot of work despite being bad at that work because their EV is quite high. And presumably with the right thresholding and everything, there probably is, like, large amounts of work that could be done even if mistakes are being made. On the question of fine-tuning, I could imagine, I could imagine it in the cards. I do have concerns because, like, in the what people need versus what people want category,
Like, I think general models tend to be really. Like, again, there’s the je ne sais quoi of generality, that making it good at, like, a million other tasks than this one narrow task might make it better at edge cases in that task, which I’m, I would be a little bit afraid of?
Yeah.
I could imagine it, is my answer. I’m endlessly practical on these things. I want everything. Like, my vision of the world is. I-- there’s, there’s so much we want to be building.
Yeah.
But also, like, I would not want to ship something that is, like, a giant foot gun, like some other AI companies would ship.
Yeah.
Well, so both OpenAI and Claude and I think even Gemini have rolled out fine-tuning and then took it back.
Yep.
Which is an interesting, observation that pretty much fine-tuning is now in the domain of open source models.
Yes. I do know about that. And like, it was kind of crap, so like, that’s probably better that they took it down.
Yeah. Yeah, so it could just be a foot gun, and telling people that fine-tuning it is probably the wrong way to go is great. Another interesting answer could be that, like, well, our model is so different, like, in the same way that quantization doesn’t apply to us
Yeah
Output tokens doesn’t apply to us, fine-tuning also doesn’t apply to us.
Well, actually, I’m, I’m super open to that possibility.
Yeah.
Like, my. This is not a promise. This is a desire. Just so to make it clear, I like to be really honest. Like, I think that, as intelligence per dollar gets cheaper, I think that we could get really, like, small approximate things that hopefully are proxies for intelligence. Like, is there a world where people don’t write regexes anymore? Because, like, the intelligence per dollar that uses AI is cheaper than, like, the complexity of a regex. That would be kinda sick. I would love that? And it might require fine-tuning for some of those narrow use cases to really get past the threshold. We will see. My hope is calibration gets that. Calibration plus a cascade of models. Like, if it’s super confident, then maybe it’s right. And if it’s in the middle, then you do the next bigger model, and you chain off from there. I don’t really know how that’s gonna go, but yeah. I could imagine it. And something that I could imagine too is, like, imagine you have, like, a series of. Like, we own the entire Pareto frontier. Something that a business might want to do, or, I think a hacker would be okay with dealing with a Pareto frontier of models. Maybe a business wants something more dynamic. You could imagine, like, having, like, a s- different sizes of models and to dynamically pick which model based on how smart it is on different parts of your stack. And you could even imagine, because of how simple our thing is, you could imagine, like, some automatic fine-tuning on that.
Future Models, Pareto Frontiers, and New Shapes of Intelligence
Yeah.
Not a promise in the slightest. I’m just, like, cooking on sci-fi.
But you would consider different sizes of Dev models so to offer that variance?
Absolutely. Yeah. Like, we. Like, how would I know how much intelligence people need?
I don’t know.
Right? Yeah. I don’t know either.
Demand is, demand is, unlimited.
Well, yeah, people are telling us not to ship things right now because we don’t need to ship things because, again
It’s good enough, yeah.
Yeah, but that’s kinda lame. And I really like the saying. This is something that I hope people hold me to because it’ll be hard to
To take back
To walk back from. Yeah. Like, the. I don’t know if it. Exactly the saying that culture is what you do when the market doesn’t reward it. And I really like that because I think that we are standing for something. Maybe in the future- what we’re standing for is, like, so obvious that we’re the equivalent of, like, boring, like, Visa or something like that. And like, we’re just like a utility that no one really thinks about, and I’ll be wearing non-pink suits or whatever else.
But I really want to be, like, rallying the world to this? Like, I want to keep doing cool stuff, bec- not because we need to, but ‘cause I want, like, people to realize that this is just the beginning? Like, that wasn’t even meant to be the opening salvo. That was, like, kind of like a, low-key research preview or whatever you wanna call it.
Yeah.
And there’s a lot more we can do.
Yeah.
With. Like, machine-native intelligence is gonna go wild.
So not the only s-- Potentially not the only size, potentially not the only model that you guys launch. That you want to open people’s mind
Absolutely not for any of those.
Yeah.
I want, I want to, like, meet whatever needs we can.
Yeah.
Right? Like, at. But with, like, a giant caveat, I don’t want to be like OpenAI’s product teams that, like, throw stuff at the walls. Like, I want it to be, like, in a, under a unified vision. Like, if you go back to the manifesto, like, everything needs to be under one of these three things
Yeah
In my opinion.
I’m not
Yeah.
I’m not prepared to do this,
Oh, I’m sorry. I’m sorry, Francis. Yeah, I can just talk about it. Like, we have, like, three steps in our stuff.
Yes.
It sounds like a tease. I want everything to go under one of these three things
Good
To keep pushing the boundaries and everything. Like, this is not. These are not, like, checklists. These are, like, axes that we think build, like, the foundation of, Of, like, a new technological revolution. And I want all of the. All the bets we make to be somewhere in there. And we will be doing some weird stuff model-wise.
So because machine-native, right? Like, humans don’t need to totally get it. It needs to just be valuable.
With, Just give people a tease or hint. Like, what does weird look like? What is weird?
I’ll give people a hint.
Yeah.
Some people are trying to call them decision models.
Okay.
That our primitives are decisions. I wouldn’t do that, because I think there’s other types that are machine-native that are not decisions.
Okay, we’ll leave it at
That’s a fun hint, a fun hint.
And let people guess. Yeah.
Yeah. I think it’s a, I think it’s a pretty fun hint.
Yeah. There’s people. Look, there’s, there’s people saying like, “I’ve done this before. I made a decision model a year ago.” Like, Jev is not new, Jev’s not cool.
Yeah.
But like, I think, there’s the categorical, like, here’s what you’re establishing is possible. There’s the, performance of, like. Well, actually the. For the benchmarks and the numbers that you’re getting, you are still beating ev- as far as I can tell, you’re still beating every single clone of you out there.
I don’t care about the benchmarks
Exactly
Just to be clear.
Exactly.
So like, even if we were winning or losing, I want to do announcements.
You’ve established the category, right?
Yep.
Yeah.
Yep.
But al- but also I think this nuance between decision models and System 1, I think is actually the thing that you’re trying to
Yes. And I just wanna make software engineers super powered
Yeah
Right? L- like with AI. Like, and or, like, the tragic thing to me is,
Economic Impact, TFP Growth, and AI in the Background
In that AI winter direction, I think, like, it’s, it’s, it’s just so sad that AI was so powerful yet so underutilized. Like, It’s a thing that gets me emotional, but man.
Like, I think that is. I don’t want to, like, just be, like, pure techno optimist, like all technology is good. I think what was happening now was, like, a travesty. Like, it’s. And like, there’s. I just want to, like, open up those possibilities for people.
Yeah, I’ll just end it there. I’ve, I’ve cried too much these last few days To want to do it on the record.
Yeah. No,
Yeah
I appreciate you sharing a little bit of that, and I think people can see that you’re very authentic and
Yeah
Passionate about this. Th- y- you don’t necessarily get that from the name, like, TypeSafe AI, but like, I think once people immerse themself, themselves enough in, like, here’s the genuinely different direction you want the world to go And like, actually you have done, like, the hard part about going from zero to one on the, on the thing, then, like, now let’s all go to- go together in, like, the new direction, right?
Yeah. Yeah.
Yeah.
I don’t n I am sure that I won’t think. Maybe I will think that the hard part was done, perhaps. I think that there’s going to be many more hard parts. Like, if, All sorts of stuff gets automated and we finally see GDP growth and like, it’s like, a Jev party
Yeah
Every day, then maybe the hard part is done. But like, I don’t s- think so. And like, I really think that people focus too much on speed and cost and not enough on reliability.
Okay.
Like, reliability is what makes it delightful. Like, reliability is what, like, allows you to trust it.
You have this line,
Yeah.
TFP growth beating 3% in five years.
Hell yeah.
I’ve never seen
Hell yeah. Let’s fucking go.
I’ve never seen
Yeah
A lab care about TFP growth.
But like, that is what an economic revolution is, right? Like, it’s actually extremely consistent with what the OpenAI charter used to stand for.
Yeah.
It was talking about, like. I think the charter is the same, but they’ve kind of tried to move definitions around to, like 100 billion in profit or something like that. Not that I hate an OpenAI.
It wasn’t like a. Yeah, it wasn’t a well-defined term what AGI is, right?
They tried to do it
No, yeah
Right? Like, doing majority of the world’s economically valuable work, and they should have to answer the question, how can it do millennium prize problems in math and zero of the world’s economically valuable work, around the air. Like, I think that all models are roughly tied right now at zero. There’s some chance that, like, we have started already, but like, I would guess that it’s not yet 1%. And I think that will show up in. Like, when it does happen, it will show up in the economic statistics.
It’s gonna be fucking awesome. It will not cause mass unemployment, but it will cause, like, a whole bunch of awesome shifts, and wor- the world will be a lot better. And also, like, I’m really tired of AI always being the foreground character, of things. Like, I think that- the world should just be more delightful, and AI should just help with that.
And I
Just, like, disappear into the background.
Exactly.
Yeah
Like, the-- I say this in my talks. Like, how can it be that 2019 software, like software, SaaS, whatever, super-duper valuable, right? It’s 2026 now. How is the software basically exactly the same, despite AI being so freaking awesome, other than sometimes having a chat box on the side, right? That, like, that kind of works, but doesn’t allow you to make decisions that the companies have stakes in, because they can’t be trusted to make decisions. That, to me, is nuts. Like, there’s so much economic incentive for this, and I think it’s going to be, like a, like an inverse SaaS-pocalypse. I think SaaS is going to be supercharged by this. They are the ones who are, like, most in the know of what things are valuable to automate, and it’s gonna be, like, a crazy time.
System 1 vs. System 2 and the Limits of Reasoning
Yeah. I think, I think so too. It’s a, it’s a beautiful thing that you’ve unlocked?
Yeah.
You mentioned one thing here, which I don’t know if it’s, like, directly here, which is, what is a System 1 problem and what is not. What is a System 2 problem? Like,
Fuck. That’s a hard one. That’s a hard one, my friend.
‘Cause people now are just trying to Jev everything, right?
Which, like, probably is gonna fail, right? But like, some things are gonna be good.
Jev everything is pretty funny.
Yeah.
It’s a pretty funny way of doing it, saying it. The. So I’ll tell you the truth.
Yeah.
The truth is that this is an empirical problem, just like scaling laws are an empirical thing. Like, why doesn’t, like, robotics really work right now, despite all the money being spent on it?
I don’t think it’s about, like, spending more money necessarily. The empirical results just might not be there, right? So empirically, I believe that these, like, pre-trained super condensations of intelligence are fundamentally System 1 thinkers. I think that they truly. Like, System 1 is the closest thing to describe what LLMs are strong at. RLVR has done incredible things for System 2 thinking. I am at awe. It is super freaking cool. Like, I don’t think that it’s going to result in AI doom in the slightest. Not 0%, of course, ‘cause I think 0% is miscalibrated. But like, i- it’s, it’s really cool what they’ve done, and they’ve really pushed it to the limits. Well, maybe they don’t think so not the limits. But like, it is, it is a weird thing for models to do, and they are very fragile at this. Like, think about how people used to talk about AI back in the ChatGPT days. Like, “Wow, it’s really general. It can do a lot of general things.” And then. But it’s bad at math problems and like, GSM8K, grade school math. And then now look at how people talk about RLVR. “It’s so fragile. It’s so jagged.”? Like, it can. “Why can it do this, like, really weird thing?” And actually, math is not just spiky, it’s fractal, right? And this is because RLVR is. Like, if we talk about, like, what is the North Star for each thing? RLHF is please humans, right? That is what the human feedback is. RLVR is optimize benchmarks. That l- everything that goes into the RLVR category literally is a benchmark by definition, because a benchmark is programmatically verifiable, simple outputs that can, like, do well. And RLCD is make it reliable for, programmatic use. And Diogo Almeida [01:22:09]: Yeah. That, I’ll
Yeah. Yeah, it’s, this. Maybe I’ll, I’ll offer some thoughts, and then you can sort of,
Ooh
Correct me if I’m wrong. One. For example, one thing that I’ve been thinking about is also. I, so I threw Jev at a bunch of things when you gave me access
Ooh, yeah
On day one. And multi-hop reasoning, right? Like
Yep
So single hop, fantastic. Like
Yeah
State of the art. You should never use anything other than Jev for single hop.
Yep.
Multi-hop is gonna. It starts to falls down. And it’s
Yeah
Like, kind of monotonically increasing as you increase the hops.
Yep.
Right?
So oh, yes. Back to that empirical question, it depends on what we can, like, pull out of the models.
Yeah.
Right? So we want everything. Like, we want to unearth as much intelligence as possible, period. The models. Like, I see us as, like, unlocking and smoothing and sculpting the intelligence while, like, adding new capabilities and like, filling in gaps in it. And we will be filling in, like, more and more and more and more of these gaps over time. But the reality is that we are in the business of unearthing properties. Those properties are actually a function of what is available from, like, these, like, these condensed cores and like, Frankensteining them all together to have all of the properties of everything.
Yeah.
? But the reality is we are in the business of unearthing as many capabilities as pos- as possible. And System 1 just happens to be the description of what works. And everything that works in that paradigm will be System 1-ish. Like, I’m.
Like, there is a reason why we don’t do what’s called latent reasoning in strings.
Yeah.
I think the reasoning. Like, the. What models do really well is reasoning within the models. It’s not totally complete. It doesn’t do great on all
Wait, latent reasoning is reasoning in strings? I thought latent reasoning is reasoning in, inside the model weights.
The
I think that
I don’t know
People used to call that
I just want to clarify
Continuous reasoning.
Okay.
I’m not entirely sure.
Okay.
It was called latent reasoning because, like, it used to be that the reasoning traces were secret.
So they’re kind of like a latent variable for the answer.
Ha.
Yeah.
So what’s secret has now shifted.
Well
Reasoning, Vision, Context Length, and Future Capabilities
Yeah
It’s, it’s still secret for OpenAI and Anthropic, right?
So no reasoning Jev
Yes
As far as you will ever do it, right? Because that, like, violates the whole promise of System 1.
I. My promise is to do whatever necessary For machine-native stuff.
Yeah.
I could imagine there are. Like, there are some forms of reasoning that are less slow, inefficient, and fragile that I. That are, like, totally on the cards, just to be clear. So pragmatic person, I’m not making promises on, like, methods. I’m making promises on, like, the. What my ROI North Star is, and I’m going to fight for that, like this launch didn’t happen and we are still, like, hungry for our place in the world.
That’s great. Yeah.
Yeah.
I think the other thing that, Vision is another one that’s, like, a big, like, capability that you don’t have, but maybe it doesn’t ever belong in System 1?
I think I have a pretty good vision.
What, sorry?
I think I have a good vision.
No, sorry. Vision
I am kidding. I’m kidding. Yeah.
Oh my God.
Yeah.
Because people obviously, the first thing they want is vision ‘cause of the Doom demo, but also just, like, everything, other than text is vision.
Everything is in the cards
Yeah
In my mind.
Okay.
Like, and actually, this is, like, a debate we have. This. Man, your audience is probably, like, the great one to have in this debate. There’s a question about, like, how much do we try to, like, give people what they think they want, which is what we did in stealth for two years. We just knew that this is obviously going to be valuable, versus give them what they say they want, right? And like, there’s a lot of dimensions of this, right? And Like, context length is an example of this, right? Every single model, including ours, I actually think as far as I can tell, ours is, like, by far the best
The longest context, yeah
At not degrading in long context.
Yeah.
But like, the other providers are just like, “Whatever people want, let’s just give them the stupid thing.” And like, we need to figure out a balance for this because, like, if you take the former side too far, give people what they want, you end up with, like, anthropic nanny state style thinking, which is very, like, anti-developer. While, like, the pro-developer route would be like, give them what they want, but developers are. Like, we don’t want to put the burden on them to figure out the je ne sais quoi of intelligence. So we are trying to, like, figure out this navigation of, like, how quickly to release things, to still, like, have our, like, brand of trust and also, like, teach our-- treat our users like adults that can make informed decisions that, don’t need, like, nanny stating on top of this stuff.
Yeah. I think that’s fair.
Yeah. And we don’t know the answer, to be honest. Like, we’ll, we’ll have to figure it out. It’s gonna be. That’s probably going to be, like, one of my biggest debates over the next couple of days
Yeah
Because, like, we have a lot of stuff. Again, we didn’t expect it to pop off, so we were like, “We’ll need some follow-up launches.” But yeah.
I don’t know, I don’t know if you didn’t expect it to pop off. Like, I, you p- I saw the work that you put in. Like, I have never seen you lock in so hard as, like, the last two months basically, right? Like
Launch Education, Cookbooks, and Product-Market Fit
Well, that’s also because my chief of staff made me lock in.
Yeah.
So
Like, it’s like, I have never. I thought I worked hard before
Yeah
And
No, but like, you were showing up at our writing workshops, and I was like, “what are you doing here?” And like, oh
It was useful. It was great.
You clearly, like, were very intentional about your launch.
Yep.
And the work showed, and like
Yeah
Congrats. Like, you got a kudos.
Thank you, thank you. I hope to keep locking in
Yeah
Is my, is my sense.
Yeah.
I want to. Like, w- like, I think that we’ve passed many great filters for the tech world, what we’re wanting, but like, there’s still gonna be a bunch more.
Yeah.
And like, holy smokes, am I excited to fight the good fight.
Yeah, it’s exciting. Before we broaden out to, like, topics outside of TypeSafe
Ooh
I just wanted to offer, any other things that you think, like, underrated or misunderstood about what you have launched.
Underrated or misunderstood?
Yeah. You have pan outs. Sorry, patterns here. Maybe you wanna go into that. Model jaggedness, anything.
Give me one
Yeah
Noodling of it. Oh, man. I would rant about all of these. I really shouldn’t. I really shouldn’t.
Okay. And like, people can come, go to your Discord if they
Yeah. People put a lot of love into the cookbooks
Yeah
Is what I will say. The cookbooks have, like, some fire stuff. We had considered putting a bunch of these things, like, in the main launch blog post, but it got kind of long and unwieldy and like, very power usery. But like, we really. I’ll be frank. Like, before the launch, every. Like, what we’re saying sounds, like, sounds like this weird alien tool. Why would anyone need this? It was a very weird thing. We were very worried about teaching people about, like, this new frontier. It obviously succeeded, but like, we put a lot of work because we thought the education would be, like, a gigantic bottleneck for us. I.
It probably works, and it’s no lo- probably no longer a problem because people are doing things, like, well beyond what we could ever expect.
They’ll show you, like, how to use your model.
Yeah, but. Exactly. But like, they. Yeah, and their use cases are, like, kinda cooler than ours. Like Like, there’s a bunch of stuff where I’m like, “Man, if that was our demo, holy shit, that was way cooler than what we were showing.” like, the computer use stuff, holy smokes is it cool. But like, we put a lot of love into this. This is not, like, AI-generated trash, as far as I know.
Yeah.
We put a lo- l- like, it’s, like, a lot of love in here.
Yeah. Fair enough.
And like, each of these are. Like, there’s real alpha there.
Okay.
Like, these are inspired by solving real customer problems that existed, and we went through the work of, like, helping them do cool-ass stuff.
Yeah. How much. While you’re talking about this, right, how much validation did you do before launch? Like, what. What was that process like?
What was that process like?
Like, clearly you did some, but obviously you’re not getting in touch with as many people as you are today.
Yes, of course.
But like
I actually think that the reception was pretty bad. And like, actually for the non-technical people in the team, they were really worried.
Yeah.
Like, there was a lot of fear. It’s like, no one really gets this. And like, they don’t want it. We’re, like, selling, like, a vitamin and not, like, a painkiller. Like, should we have FDEs to, like, write the software around solving that problem?
Yeah.
We had almost no revenue before launch. It was kind of like. Like, we. Like, the technical people were, like, obviously true believers, right? Like, we knew that this was sick. Its prop- computational properties are, like, off the charts on, like, so many axes that we’re like, “Yeah, obviously it’s gonna be huge.” I was definitely super afraid, which is why I locked in super hard. But like, the most common thing was- The, like, I would say, like, more than half the people we had play with it just did not get it. And like, the people who did, like, were like, “Man, this is really cool, but how do we get this through procurement and stuff like that?” it was like, it was like quite a, quite a battle, and we just knew like, okay, the-- our target market is gonna be developers. People will find the use cases, and that way everyone is gonna FOMO in. And like,
I don’t want to rub in people, like, changing their minds with the facts changing.
I do want to call into question, like, the concept of product market fit? Yeah, but like, because, like, there was a product, there was a market. Like, we were like, “Hey, do you want to use this?” And people are like, “I don’t know, really know if it solves our problems.” It explodes and everyone’s like, “We need as much rate limits as we can. Can we literally give you GPUs? Because we are constrained right now.”
Yeah.
So of course, like, marketing is an element of it, of course, but I don’t even think it’s about marketing. I think it’s about, like, passionate developers who’ve, like, our souls basically resonated at the same frequently, and that frequency, and that got everyone else excited too.
Yeah.
And I’m hoping as well that, like, we as a company will be eternally grateful to those developers. Like, not-- and not just like, the companies that, like, are-- like, start off with developers and like, go big enterprises.
They go to market, yeah.
Exactly. And like, I’m, like, even thinking about, like, how can we launch things that are better for. Oh, man, I don’t know if I should say this.
But I will.
Better for developers than enterprises.
Exactly.
Okay.
How do we do that? Like, how do we empower them? And I have cooks. I have cooks. But it’s a, it’s a very weird thing to do. And like, I don’t know how else I can show my thanks and loyalty to that. Like, and that’s why I did, like, the dying my hair yesterday. It was like It’s like I wanted to talk to them ‘cause it felt dirty to me during our company’s, like, most important times not to keep talking to them.
Good. Well, that’s why is your hair.
Yeah. Hold me to that, please.
Yeah. We will, we will.
I try to be principled.
Yeah.
Quote me on this. Call me out. D- have the pitchforks out if I change.
I was just gonna briefly show the computer use stuff.
Computer Use and Emerging Use Cases
Whoa.
Is this, is this what you’re referencing?
I’ve never seen-- I haven’t-- I’ve seen. I saw, like, a airline browser use thing.
And inside this new note, let’s make the title say hello.
Wow. Great. Okay. Let’s move on and can you open up the Arc browser? And once you’re there, can you Google search Norbert Wiener?
Now can you open up x.com?
Is this kind of use case?
Oh, the voice use cases. This is actually the first one I’ve seen. This is
Oh, okay.
Open up the photo viewer. Wow. Oh, wait. Oh, can you bo- can you go back a second? Can you go back a second?
Rumors claim Anthropic engineers worth- worship Claude as God. Wow. Wow.
Dang. That’s pretty funny.
And here you are building prod.
Abso-- Wow, this is sick.
Yeah. So clearly it can operate the whole computer with voice, with Jev as the decision model.
So Just like I’m anti-benchmarking, I’m also anti-demos. I want to make sure that it works reliably. I love people are playing with it. This is super fucking sick, have no doubt. I want to see this. I wanna see it be used. I want our team to play with it. I wanna find the weaknesses, and I wanna solve that.
Yeah.
And I would lo-- Man, that looked really cool.
That looked really cool. I want that. I want that. Like, when my, when my wrists are sore, I, like, just whisper flow everything. That would be sick.
Well, as, well, just to round out the use cases side
Yeah
‘cause I do have to let you go. Who’s, who are the, who are the bigger companies that have reached out and have surprised you with what they wanna do?
Just.
I am so out of touch for that.
Okay.
People have shown me screenshots of companies, and from what I’ve seen, it’s all of them.
Dark Data, Real-Time Intelligence, and Verification
Yeah. Mostly, like, for those people who work at larger companies and they’re not doing this kind of work, I just wanna give people examples of, like, you should go look that up, look that up, look that up.
Oh. So like, I think demos are super-duper sick. Obviously, the coding agents are, like, gigantic use cases.
Like, they are, like, also super sick.
Oh, Cog is all about Jev right now.
Oh, hell yeah. Oh, can I, can I give a little bit of a tangent about coding agents, if that’s or
Yes, please.
Oh, let me
We love coding agents here.
Give me a second. Give me a second. Okay, actually, I’ll come back to coding agents. Let me describe, like, the big families of use cases.
Yes.
Like, we’ve mapped this out from first principles, like, long before release. They are what we call dark data. Like, people hoarded big data, but they would not throw a LM at it ‘cause it was too expensive. So large companies adore this. They have, like, piles of data that they wish they could analyze, and this is like a data scientist’s wet dream. So this is like. This is a giant one. Like, I think this plus, coding agents are the m- big moneymakers because that’s what they’re all. Where all the volume is, right? There’s the real-time stuff. Like people who need, like, intelligence in the loop. They. Like, I would guess that every CEO, if not CTO, at those companies, knows how much better their product gets with every, like, 10 milliseconds shaved.
Yes.
And like
Especially e-commerce, yeah.
Yeah. Oh, or, like, assistant-y things. There’s many AI assistant-y things. And like, as far as I can tell, they really love it. Again, I’m not in the front lines of customers right now, so I just get. Know what my team tells me. But like, this. I’m so excited for this. I’m really excited for this for games. I really wanna play, like, sick-ass auto-battlers where you’re, like, commanding your team, or, like, semi-auto battlers. I think that’d be so cool. But don’t make it too good while I still have a job. And the. Like, there’s the. What we call, like, verify everything. Like, verifying all LLM calls, kind of like observability. I think, actually on the note of docs, what people should be doing is, like, the parallel questions are very cheap. So if you have, like, big states you wanna ask many questions on
This right here, yeah.
Put IDs on every, like, message, and then ask a question about each ID. So like, when you have, like, a long state.
Huh.
So that way you can, like, pay for the state once and ask lots and lots of questions about each message within it. I think that is, like, a, like, a great way that, like, saves money and is.
Which, by the way, I always think, like, it’s interesting framing System 1 and System 2 because it basically makes the case that you should always make one or 10 or 100 Jev calls for every one reasoning call that you make.
Well, maybe. May
Right.
Well, I don’t. I would like people to spend less.
Yeah.
Maybe you do, like, one half the reasoning calls and like, 10 Jev calls each or something like that, or whatever solves the problem that, like, couldn’t have existed otherwise. Wait, number four use case was what I described as, like, smart software. Like, software that’s intrinsically composable and like, does, like, weird, fun stuff that could never happen before. Like the programming language as Jev thing. I don’t know if you’ve seen that. That is so cool. Man, if we knew how to give out credits, because, like, we’re really early in our infra days, I would wanna give all these projects credits.
And I think that those are, like, how we’ve mapped out, like, the main use cases. Computer use has also come in kind of like the real-time direction as well, and like, that’s really cool. If it is reliable, I am super jazzed about that. I suspect we can make the model a lot better at these use cases ‘cause, like, that came out of left field a little bit, so that’s, that’s really cool. On the coding agent thing, and this is, like, a really surprising thing that is happening right now.
Coding Agents in a Multi-Model World
Okay.
Claude Code and Codex are, I believe, the winner, like, the number one and two. I’m not entirely sure. I don’t follow closely
Roughly
But like, it’s roughly that. But they’re built around a single model world? Like, and that makes a lot of sense for them, right? Because, like, it has been a one-model game where it’s, like, kind of like the same model but different intelligence that you’re shopping.
But all the open coding agents are, like, fucking jazzed right now because they’re, like, getting their Jev on. And Like, the thing is, there’s-- I’m sure they’re trying a lot of weird stuff But all the coding agents are kind of roughly at, like, approximate parity, right? Because, like, there’s not so much you can do with a while loop. But the moment one person finds one killer use case that, you can only do with that coding agent, everyone will flock to it because they have, like, a monopoly on that thing. But all the open coding agents will be able to copy that, right? The end. But I don’t know what the Claude Codes and Codexes will do because they are built around that one model world.
Single model, yeah.
And like, I think that’s gonna be, like, a really interesting thing. Like, I would love to be able to integrate with them personally. Like, I want to integrate with everyone. Like, I-- they might make competitors eventually. I don’t know. But like, it is not me-- my job as Songfire Infrastructure to be opinionated on that, right? Like, I want to just serve the world. But I don’t know if they would do that. And like, I think it’ll make the coding agent game super weird. Like, I’m so excited for that. And like, I’m sure. I’m getting my team to review right now an internal document I made on design patterns I suspect will be useful for coding agents. So hopefully I can share it, like, right after I walk home. But like, I think that there’s just, like, such ripe area for exploration out in the world. And like, it’s, it’s. Man, if I did not have this, I would love to experiment with coding agents right now.
Yeah. And I’m sure the coding agent companies would love to work with you as well to figure that out. Yeah, I do think that there’s still use cases for Claude Code and Codex with you guys
Of course
Which, it’s, it’s easy to explore there. Okay. We’ve-- you’ve, you’ve been very, obliging in the sort of indulging in all these, all these things. I just wanna take you out of TypeSafe
Pacing the Frontier, RLVR, and Alternative Research Directions
Oh, yeah
Just generally about. And you’ve, you’ve made very clear your position on the state of AI. Give you more room on the alignment safety side of things.
Oh, did I not talk about safety alignment at all?
Oh. Oh, you did, you did.
I think I didn’t. I think maybe I didn’t.
You did.
Oh.
I just, like, I think that there’s, there’s a lot of, You have a lot of researcher discussions. We have this every
Of course
Every NeurIPS.
Yeah.
What are people talking about? Like, I. So for example, I, recently was at, one of these researcher gatherings, and people are genuinely worried about the pacing, right? Like, this whole topic about, like, we should slow down because The public is, like, clearly not ready. And I’m sure you have strong feelings.
I feel like this is the kind of thing that is a dangerous
Okay
Topic to talk about. I’m happy to talk about it. I live for danger.
All right.
Our company brand is chaos. It’s not Jev. It is irreverence and chaos.
And yeah. And like, you were at OpenAI during, like, the. One of the very first, like, very visible incidents, which is the blip, right? Like, which
Oh, the
Which, like. And like, you. The dominoes have gone down now To now every Frontier lab has co-signed a document saying that they wanna pace.
Interesting. I. So comp-- it’s a very complicated, nuanced thing. I actually do want to write a response to this more formally. I do have, like, a little bit of a short version of my response
Yeah
Which is that, as you RLVR more, like, RLVR is like.
So RLVR is not actually about verifiable rewards. Like, that has been failing since before the reasoning revolution. Like. And that’s the weird part about tasks, right? Like, back when. Oh, fun history. Back when RLHF was becoming a thing, there were three different things that, like, are now called post-training, different efforts. And instruction following was by far the, like, the vaster child. Like, people didn’t like it. They didn’t want to take it into account. It was annoying. Like, I talked to the pre-training team. I’m like, “Guys, this is the magic.” And they’re like, “We run so many model sweeps. You want us to wait for human evals to figure out which models to use?” And like, everyone is, like, giving tons of, like, resources to, like, the code gen team, which, like, they did s- have some successes, but they were trying really hard to do RL on co- like, unit tests. And it didn’t work, obviously, right? Like, you needed reasoning for that. So re- so just to be clear, RLVR is not purely about the reward. It’s about, like, the shape of everything too. And part of it is that reasoning is included in here, like this latent variable that you’re doing things. And when you’re doing things, you’re just letting the models do whatever they want in order to make them be as powerful as you can to answer the hardest problems. And this whole pace the frontier discussion, I think is, like, a very narrow focus because it assumes that everyone needs to do more RLVR, right? Which, like, I obviously don’t think I need to do more RLVR on our models.
I think zero is the optimal amount for our shape. Hey, right? Like, come on.
Yeah.
. So It’s really, I think, a bit of a sleight of hand where they are saying that we actually want to keep doing the thing that looks dangerous because it does dangerous things. Like people say, like, “Oh, maybe the sandboxing was a problem,” or whatever else. Yeah, obviously it is, and they could have easily solved that, right? But they chose not to because the more things you let the models do in this do anything category, the more powerful it is, right? So like, there-- I think there’s some, like, disillusion of responsibility there on, like, things that by design or non-design they’re trying to make is just an assumption. We must do RLVR, and not just we must do it, we must do more and more and more, with giving the models, like, the power to do powerful-- do anything they want in the middle ‘cause that teaches them to be powerful outside of it. And we don’t want to limit those things well because it’ll make it slightly less powerful on those things.
So like, if you assume all of that, they’re like, “Oh, yeah
That’s a logical conclusion
We’re heading to a dangerous world, guys.”
Right.
Like, “Everyone is gonna be doing this, and this is the only way to make AI sick.” So Swyx [01:45:37]: So basically it’s like, it’s like, it-- these are all internally consistent, but actually starts from a premise that has alternatives if you
Of course
Think about it.
Of course. I think there’s-- Like, on the bittersweet lesson direction, I think that there’s very few people who’ve, like, made right tasks. Like new directions of AI. That is-- Or new North Stars. That is rare. Again, like, I think 2.2 times or something for LLMs itself, like RLHF and then RLCD.
Oh.
RLVR is like a 0.2, in my opinion, and I think that’s generous.
But or 0.5 or, like, it could be one whole one. I don’t really care. But I do think that people are thinking very close-mindedly about this type of thing. And this-- the only people who are at fault here are the researchers because it’s definitely not the populace. Like, they just assume that OpenAI and Anthropic are just doing the best they can, and they are not the experts who are aware of the true optionality available.
Yeah. And that’s fair. And like
Yeah
You’re, you’re also doing your part in waking them up.
Yes. Okay. Well, I’m doing my best, but like, my goal is not, like, convince labs that there’s, like, other directions
Yeah
To go down. My goal is have-- it’s like spark hope in software engineers to start, like, actually automating things they’ve always wanted automated. I had this, like, article that I wrote that my team didn’t let me write, that didn’t let me publish about, like, the future I want of AI. And like, there’s, like, a lot of, like, little things. Like, remember do what? Imagine if everything could do what ‘cause, like, that demo was do what.
Like, you could. Like, there’s levels
Yeah, don’t do what I say.
?
Yeah. Don’t do what I say, do what.
Yeah. And like, we couldn’t do what yet because, like, computers are so basic and literal, but that computer use one was just that. And I think that there’s, like, levels of smoothness that’ll happen in the world that people just don’t understand. And like, the promise of, like, smarts all around are. It’s, it’s, it’s-- I don’t wanna overpromise. I don’t think it’s going to happen right now, but like, we are gonna do whatever the fuck we can to make that happen.
Mid-Training, Pre-Training, and Model Frankensteining
Yeah. Any other things on the sort of general shape of post-training? You obviously you have been very intimately involved. Mid-training, is that, something that you do have comments on? I don’t think we’ve ever talked about it.
Mid-training. It’s all a spectrum.
Yeah.
Right? Like, am I
This is like curriculum, but like, fancier.
Yeah. Like, it’s, it’s, it’s like, it’s a cost-saving thing.
Yeah.
Instead of, like, having to pre-train again. Like, there’s intriguing stuff. I actually think that, like, intelligence has a je ne sais quoi at every single level, and it’s always super-duper fascinating. Like, I’m a shape rotator, so I don’t like finding that, but I love it when people find it and teach me about it. But looking at the data, this thing that, our data team is so good at that I’m not.
It’s-- I find it really fascinating. I love actually thinking about, like, how capabilities are, like, put into the model, like, over, like, the short term. Like, there’s, like, the really rapid alignment of fine-tuning and over the long term. After seeing it over and over and over again, like, this stuff gets baked deeper and deeper and deeper and deeper into the model until it gets robust. And that is, like, the North Star to surface, and like, the System 1 stuff is the stuff that ends up getting robust. So I find mid-training to be, like, a fascinating thing. I’m a fan of all forms of training. I’m a fan of all forms of, like, surfacing new types of intelligence. I wouldn’t do it all myself because it’s expensive. And I have said privately, and also.
Should I say this? Huh. Huh. Like, my philosophy is anything I sh- I should say in, like, private with, like, an investor, I should say in public with the people because that is, like
Power to the people
My thing.
Yeah.
Yes. So m- the thing I’ve said i- before is if you gave me a billion dollars, I wouldn’t pre-train. I still believe that to be true. It is a very expensive thing when. If you are, like. Like, if you’re an AI engineer, you can, like, slice and dice and do all sorts of stuff. Like, Frankensteining is not the most elegant, beautiful thing, but it solves problems, baby.
So - Anything except pre-training.
Yeah. Amazing. I think one direction that I do think that is interesting, just, like, synthesizing all your, all your commentary about these model things is, like, do we have a super model, that has all these capabilities involved, or do we break them out, in further? I guess sort of, like, one way to put this is that OpenAI was trending in the direction of the omni model Right? 4o was one of those. Then for a brief period of time, there was always, like, there was, like, a kind of a main branch of the-- this is the chat-tuned model and this is the coding-tuned model.
Those are completely different things. Those are extremely different concepts. I will, like, break that down a little bit. So multimodality is a little bit different
Multimodality, Post-Training, and Fractured Intelligence
Because sometimes the other modalities help, sometimes they hurt.
Yes.
Like, people are moving. They seem to be moving away from speech, which is different than audio, because it seems to not generalize well to the other stuff.
This might get solved. I’m a fan of all of this, but these are, like, empirical, real questions. Like, scaling laws are not about just throw money at it and it gets good. Scaling laws are pragmatically how good is a thing? Like, there are worlds where, like, no matter what you scale, it may not be good enough. So Y- like, computer use is not currently solved is my understanding. Like, I’m hoping that we can be a. Like, play a part in solving that. But like, it. There might be no amount of data we collect that will solve that. We might need better methods or something else like that. So Diogo Almeida [01:51:33]: Like, we. You need to be, like, really practical in all of this. Am I a fan of omni models? I’m a fan of all forms of intelligence, but I will go straight into one thing you talked about, which is different from pre-training, which is post-training ‘cause I hate fracturing intelligence. That is, like, the bad thing to me. And this whole, like, chat-first reasoning mode is because, it forces the intelligence to be fractured. Like, when you’re optimizing for chat, this tends to be, like, pure RLHF, and it’s quite intrinsic in RLHF to do the stuff people, like, naturally complain about, right? Like, oh, I’m gonna
You’re absolutely right. And
Yeah
.
Sycophancy, psychophancy
Yeah
I d- whatever word
Yeah
How- or how to pronounce that. Overconfidence, hallucination. Like, even the kind of style that excels in LM Arena, bold, italicized, emojis? Like, it doesn’t answer the question simply. It gives, like, a long write-up, and then it asks you a follow-up question so it feels more like a human talking to you. All of these things, come because strings are super weird? They are, like, weird-ass things, and you need to be miscalibrated. You need to, like, mode drop. You need to be hyper-confident in order to not go off the rails ‘cause the reward model will punish you so hard when that happens ‘cause it’s obvious. Y- and then this, like, warps the probability space entirely, and it interacts with that of the reasoning models, right? Because, like, it. The models are, like, these simple linear things that tend to cheat a bit. So I think that’s very different than exposing intelligence is my guess. And a lot of the art to intelligence is studying this subtlety that I think that, at least when I was in OpenAI, people were not really studying that because, like, they were just like, “Chat,” just like people are on with Jev right now.
Yeah, you give me an ultimate. You give me an objective, I will just all go optimize for that, right? Like, and it
Yes. But if you try in there. And like, the saying is, like, you could have, like, two objectives and you could just, like, optimize for both, but then that is literally the act of fracturing, right? So yeah.
So in some ways, you ha- you are also fracturing intelligence into System 1, System 2, but you just don’t agree with the other people’s fractur- fracturing, which is fine.
Oh, it
Which is fine.
It’s a little different. No. If I could, if I could add, if I could defend
Yeah
The System 2 tasks, number one, like, we don’t toss out the System 2 tasks, right? Like, you can try to make Jev work on it, and there actually is an intelligent answer for that, which is unknown. Like, my. Like, there. Like, there is better and worse behavior in the System 2 tasks, which should be, like, really low confidence, lots of uncertainty. Maybe some heuristics can, like, move the needle here and there, but we care about them too, just to be clear. I just think that is not what the. What is. The intelligence is native to. So we’re not trying to fracture anything like that. And all fracturing makes the model dumb. Like, if people, like, get the model to say, like, it is OpenAI or Qwen or, d- like, Claude or whatever else, I don’t really know what it says this d- these days. I am not going to put into the models that you are Jev from TypeSafe. That fractures it, right? Like, it. L- like, I don’t want that. Like, represent what do the internet thinks, right? Like, be correct. That is what I want because that’s how you get the smooth, predictable intelligence.
I, identity is a thing, I guess, that is
I- for, it- for
A somewhat of a special
For a first-party product, yes.
Yeah.
But like, for an API, I don’t think so.
Yeah. Okay.
?
Yeah, that’s good.
Like, I don’t. I. Like, people don’t want. If they’re making a chatbot with, ChatGPT, they don’t want it to say it’s ChatGPT. They wanna say it’s, like, Chipout AI or whatever, right?
Identity, APIs, and the Jev Skill
Well, so the way that you also have to make up for it is you have the skill, right? The
Yeah
The Jev skill, which is for coding agents to work with Jev.
Yeah.
Okay, a couple closing questions
Hell yeah
Because I do want to, get you out. One is, like, is just reflecting on your two-year journey. It’s roughly two years? Two point something?
With the company
Yeah
I think that this is, like, more like a four-year journey.
Yeah.
But
Well, yeah. Actually, like, I was thinking, remembering that, like, you had this, like, hero run around Thanksgiving. You were like. You were canceling everything because, you were like, “Guys, like, everyone’s on holiday. I’m gonna take all the open edge GPUs and go do this thing.”
Yeah. That was a good time.
And that was, like, the pre-TypeSafe
Yeah
Moment, right?
I. That might have been. Was that when the coup was happening? I don’t really know.
Yes, actually.
Yeah. That sounds right. Yeah. I remember. Oh my God, I don’t wanna. I’m not. I don’t think I have the time to spill the tea about the coup right now, but That was really annoying.
The coup was annoying or the run was annoying?
The coup was annoying.
The coup. Okay.
Yeah.
Yeah.
It. I will
Safia’s took over the company. Yeah, anyway.
Maybe next time we chat
Okay. All right, all right
I’ll, I’ll dump tea about. A tea about the coup. Yeah. It actually, this problem was one that, like, was in my mind since before ChatGPT even launched. I was like, “Holy shit, the ChatGPT team is cooking. They are doing the right task.” They are doing the thing that AI researchers are bad at, but successful product people are good at, which is giving a lot of fucks about the experience. It’s, it’s, it’s very rare. They. Like, there’s very few people like that at OpenAI. And those guys were cooking on it really well.
From InstructGPT to TypeSafe
And to be clear, this is the whole journey from GPT-3 to 3.5, which included AI Dungeon, which you’ve talked about
Yeah
As like. Yeah. Well, that’s, that’s an example of a use case that we never predicted.
Yes, exactly.
That’s right.
Well, Oh, yeah, that is a. Also, I had fought very hard to deploy InstructGPT.
Like, actually the early versions of it were even trained with, like, an algorithm we didn’t publish that I made myself because it was too slow to clean the PPO data. And I was like, “Fuck it. This is so fucking good. We need to get it in the hands of users.”
And like, basically immediately it took 50% of the market share of LLMs at the time. And but. And we thought it. I made. I went through great effort to make sure everything in our launch video is true. We. I truly was thinking like, “Is this AGI because it’s superhuman at instruction, in instruction out?” You. Obviously, it’s not, but like, everyone I think should have an answer to why that was not AGI, ‘cause it looks very smart. And my answer to that ended up, like, ended up only being used for copywriting. Jasper AI, Copy.ai, like writing, like, what is now called slop on web pages. And we were worried we made the internet a worse place, right? And I went back to the drawing board, and I was like, “What’s missing? We are smart, clearly. Something is missing from it, like, creating value. What is it?” Like, I actually was doing more philosophy at the time of like, “What is going on?” And the answer was, “Oh, machines.” the question I asked myself is like, “Let’s work backwards from an AI-based economic revolution. When that happens, what will c- be. What’ll be calling the AI if AI is an API? Will it be humans or it’ll be code?” And I figured it was many nines of code. And but like, all the optimization was going into the humans part. And then it clicked for me. I’m like, “Holy shit, this is the North Star.” I think, like, I wrote a document. I was, like, talking to Sam about this. Sam was like, “This is so fucking good. You should go work on it.” And we’re like, “Yeah, Sam, I have a job.” like, it. I was working on
Sam just told you to do it. Dude, go do it.
But like, my guess at the time is like, this is super obvious. Like, it’s so unbelievably obvious. Anthropic must be working on this already? And like, we’re already cooked and like, actually OpenAI does better at, like, catching up than it does at, like, actually innovating. So like, ChatGPT was a copy of Claude, right? Like, they had an internal thing. They just didn’t ship it.
Yes. Yeah. Claude and Slack. But reasoning, I would say first-ish.
Yeah.
Yeah.
But debatable how good of a product that is.
Yeah.
Great research though. Super great research. I’m just not sure if people had that product need. And Claude did the coding agent stuff too. So Sam says that, and I just go back to my job for a while. Eventually, like, the instruction following team just says, “We won. We’ve solved instruction following. We don’t need to do stuff anymore.” I’m, like, trying to think about what I do next. I was like, “ maybe I’ll just, like, start playing around with this.” I, do more philosophy and design and thinking. I thought it would end up taking a week, when I started training models. It ended up taking,
Many years. At some point I was like, “Holy shit, there’s signs of life here.” This. It obviously didn’t work, right? Otherwise, we would have deployed it. But like, I wanna explore what it would be like research-wise to go all in on this. Like, I wanna really see, like, what it would be like if you went, like, absolutely insanely all in this direction. And because of what I said, like, if an AI winter happened, would I. How would I feel? I would consider myself personally responsible. I talked to other companies at the time, and I was like, “Hey, I want to start a lab on this direction.” And like, there was interest, and I just talked to them like, “How fast. What would be faster? This or a startup?” And they’re like, “Startup.” And I’m like, “Fuck it, man. We ball.”
Yeah.
“I guess we’re doing some crazy shit.” And
And you called Eric and Sasha and
Yeah. Well, I call Eric first. With Sasha, I actually didn’t try to recruit her. I tried to be good, and I was just like, “Hey, am I crazy? Is something missing here? Isn’t there, like, am I too much in the OpenAI bubble that I didn’t realize there must be a solution to this?” And then Sasha was like, “I’m in.” And I’m like, “Sasha, you’re working at a startup.” And she’s like, “I’m folding it right now.” And I’m like, “Do you wanna think about that?” She’s like, “Oh, yeah. Good point. Let me think about it.” And then she joined.
Yeah.
And then, within two weeks we had funding. We di- we had, like, people move into my apartment. It was the worst ‘cause I’m a neat freak. And we just kept on cooking, and eventually we got the research that,
Starting TypeSafe and Advice for Frontier Researchers
That showed the signs of life?
Yeah.
It was, it was a crazy time.
So the qu- the question is. That was all long context.
Oh, yeah.
And then now the question is, someone like you
Yeah
Is in the Frontier lab right now who is frustrated not getting the funding or the resources, whatever, the attention. What’s your advice to them? Do. Should they do what you did?
Should they do it. Ooh, that’s a fascinating question.
Ooh, man. How do I do this without burning bridges?
I-- My sense is that most n-- unless there’s some level of economics I don’t really understand, I think most neo labs are crap. I don’t want to see myself with that as peers. Like, I don’t really understand what’s going on there. Like, is it becau-- Like, number one, I don’t really value researchers. I value people who. Like, look at my bitterness lesson, right?
The data, the task.
I want. Well, not just that.
Yeah.
I, like, we need researchers, but we need them to give a lot of fucks about the right task, and that’s the important thing, right? So it’s actually, like, the. It’s, it’s kind of backwards when people value pure research pedigree ‘cause that generally doesn’t create value. So it. Like, number one, I believe in North Star tasks and doing cool, really useful stuff. Number two, because I don’t value researchers, I don’t, I don’t recommend going the. Well, it clearly is profitable for someone, or it might be in this environment. So like, from a purely pragmatic perspective, I don’t see creating neo labs as want- something that creates value. It seems to destroy value because, like, they are, like, redoing work from scratch with, like, low probability of actually moving the frontier. And as far as I’ve talked to most neo labs, they don’t really have a direction. They tend to want money to play around with their experiments. If they have a direction, I’m super in favor of it, to be clear. So my advice for someone is it really depends on why you’re doing it? If you are a researcher who wants to play around with research, probably the labs are the best place to do that, TBH. Like, there might be other places. I don’t really keep track of that politics, but I would just recommend not being that way, personally? Like, I think it’s better for the world with people being driven to solve real problems. And those problems may be exploratory. That’s fine. But like, ideally have principles that you stand behind. But if you think that you wanna do the right task, like, abso-fucking-lutely. Like, please do. Like, please break this, like, uni-mind, unimodal, like
Hive mind.
Yeah, exactly. Like, ev- like, again, this pacing the frontier is coming from, like, this one view of AI that looks like, AI super genius that is incredibly jagged, and that is,
Solvable.
It’s solvable, and it’s weird, and it’s, like, not matching reality. And It’s like. It’s tragic, right? Like, I think, like, all of these. Like, the. Like, really unearthing technology I think is, like, just good.
Yeah. For what it’s worth, again, I’m trying to repre- accurately represent the position of the, Anthropic OpenAI folks I was talking to, SpaceX as well, by the way, is that, it is. This is a political thing much more so than a pure Xris thing.
Yep.
So yeah. Political positioning is
And that. And that’s beyond my pay grade.
Exactly, yeah.
That’s well beyond my pay grade.
Once they, once they told me that, I was like, “I get it. This is about the 2028, election.”
Oh, no.
Yeah.
Oh, I wish I didn’t hear that. That’s such a bad vibe.
And so
No. This is not the whole company.
Yeah.
This is just that room’s discussion.
No. That makes sense.
Yeah. Yeah.
That makes me lose faith in humanity a bit, but maybe I’m just a naive technologist.
It’s really starting to matter
Yeah
Who’s, who’s in charge of the governments, that will help to regulate, these things as they emerge. And like, as a lab
I tot
You should probably think that through.
No. No. I totally agree with that, to be clear. Like, I think being opinionated on that matters a lot. I personally am afraid of trying to mislead people because I think that bites people in the ass a lot? Like, I think that, like, people trying to be overconfident, like, I obviously just. I’m not actually gonna talk about politics. I think what happened in COVID is, like, people leaned too much in, like, appeals to authority and being overconfident to try to get people to behave in certain ways. And like, obviously our response was extremely suboptimal, and that had, like, ripples of downstream ramifications that are now, I think, extremely bad for the world. Like, maybe I’m naive. I think that misleading people, even for the greater good or what they think is the greater good, is just, it’s just. I’m not a fan.
Yeah.
I’d r- I’d rather not do it.
For what it’s worth, I. It’s not a. I don’t think it’s misleading. It is just like, this is why now.
Yeah.
Why. Yeah. W- like, w-?
The. I think that the thing
Like, Dario Rodas said in May, like, “Fuck are we doing now?”
I think that is why now that is a little bit, misleading about, like, the risks versus, like, the objective. It. There is, like
Yeah
Some level of, like, sneakiness latent in it
Yeah
That, is worth calling out and I think owning up to. Well, obviously they want to. If they want to manipulate, then they shouldn’t own up to that. That seems like a bad strategy.
No.
But like, that to me is just sad for the world.
Yeah.
Hopefully I’m never. I’ve. Yeah. Hopefully, like, we are never involved in anything
Yeah
Like that. It might be inevitable as we get big, but I want to. I wanna stay, like, pure technologist to my roots as much as I can.
Jev for president. Why not? I can. I. I would trust Jev’s decisions over, my own. Okay, so less shitposting, more about
Less shitposting.
No. For me.
You’re just kind
I’m shit- I’m shitposting.
Oh, you’re just crushing my hopes
No. I’m not gonna be shitposting
About, like, American in the world right now.
Oh my lord.
Yeah. Like, there’s. I kind of. I think I watch too much TV about, like, conspiracies to think about the presidency.
Oh, no.
The, You have chosen your North Star. You have chosen reliability. You’re in a programmable and composable AI.
And cheap.
And cheap.
Games, KV Cache, and Rethinking Coding Agents
Yeah.
What is a second or third one that you wanna throw as a bone to someone else that you’re not. That you want someone else to work on that you’re not gonna work on?
Ooh.
Like, just basically give people tasks.
Give people tasks?
Yeah, like, that your task
Oh, there’s so many I want. Oh, what?
You have picked your tasks, right? What?
What? Wait, I. That’s such a good question. Holy crap. Oh, man, I’m so excited by that.
‘Cause you’re, you’re gonna be, you’ll be for the next, like, 50 years, you’re gonna be busy doing your thing.
Hell yeah. Okay, so let me give, like, a fun one and a not fun. L- and like, maybe a valuable one that’s also fun.
My fun one is I think games could be so freaking cool if they were intelligent. Like, when I see people play around with, like, Ali’s Doom demo, where, like, you can, like, get NPCs to control stuff, like, Like, that was just really, like, the. Like, a proof of concept. I think really cool stuff could be made. It looks really cool. Like, I’m a big Stardew Valley fan? And like, it’s, it’s really static, and it’s still compelling. Like, I feel like there’s a lot of cool story that could happen. You don’t need to call, like, Jev in the game loop. It’s probably too expensive for that. But even, like, simple, like, state machines for NPCs, I think you could make, like, such a compelling world. Oh, man.
And man, a little sad that I can’t work on these types of things.
Yeah.
My life path is a little bit set right now, and I’m,
Yeah, but you can call someone else to work on it
Yeah. That’s cool
And then you can, like, feedback on it.
And the thing that I would really like to explore is, like, coding agents free from the tyranny of the KV cache. Like, it might not be as good as true coding agents are, but I think there’s just so many weird things to think about. Th- that’s why I wrote the article KV cache Rules Everything Around Me.
Believe it or not, I don’t think anyone has used the phrase on the internet “cache rules everything around me,” C-A-C-H-E, when I, when I Googled it.
Okay
So like, I wrote this ‘cause I wanted to tell people about, like, this is how coding agents w- agents work and how the KV cache works and everything. And I think. I don’t know. Yeah.
Like, it explains a lot of stuff, like why routing is really hard, why sub-agents don’t seem to work, like, why compaction is such a hard problem. And I’m going to try to release a document. My team might veto me because, believe it or not, I’m not in charge.
But I wish. But I want to release a document of like, “Here are my thoughts. Please play with it, and please figure out all the ways that we can do things with coding agents, like, once you’re freed from that KV cache tyranny.”
Which is it locks you in and
Well, not. It lo- it locks you in into one model, right? And in order to do it efficiently, you need to, like, keep on appending to it. So now you’re not doing best software practices, like state management, abstraction, decomposition. Why can’t you give an easier task some. Yeah, why can’t you give a sub-agent an easier task? Because of the state that you’re passing around. Oh, I touched this. Because of the state you’re passing around, you nee- would need intelligence that is way cheaper than the intelligence using to read this in order to pass this state around. Why can’t you be smart about it, right? And I think there’s just, like, c- tons of really cool, fun research to be had there on, like, different programming patterns. Kind of like how people are playing around, like, with, like, recursive language models. Like, I feel like there’s, like, just lots of cool stuff in here when you think about, like, “Oh, I want to explicitly label the state of everything.” Or imagine you have, like, a sub-task. Like, coding agents, I think it’s fair to say they work on sub-tasks at a time, as from a decomposition perspective. Why do you need to pass all of that state back into the parent task?
Yeah.
Why couldn’t you do smart things about it? And also, if you had a hierarchy of labeled sub-tasks, why can’t you do a search through that sub-task tree for the relevant context when you need it in, right? And then, another thing that you can do. Oh, man, I forgot to write something about this. I have, like, some cooks in here that are really cool. Hope to publish it. I’m down to jam about it, but like, it’s gonna be a long document. And like, if that becomes the case where context becomes cheap, like, why can’t you do cool patterns, like looking at your historical context very cheaply? Is it kind of weird that you start from scratch every time and you need to solve a problem called continuous learning? That’s a, that’s actually like a memory management problem because you don’t have a smart way of looking up the memory, right? But what if you could? What if you could do that all the time? Or what if when you have parallel sub-agents, they can, like, read each other’s states because you have all of that in, like, your computer memory, and you can be smart about what’s reading and writing at the same time, and your coding agent swarm or whatever has, like, locks around things and can coordinate intelligently, not with, like, basic-ass locks. Like, “What are you doing? What am I doing?” “Jev, who should write first?” Blah. And like, I feel like the future there is
Oh my God
Nuts. Yeah.
Jev to solve locks.
It could be so cool for, like, multiple agents working together. Or, like, if you think about state
Yeah
Like, you have
Agent swarm and stuff.
Yeah.
Yeah.
And some things, for example, are read-only processes. Some people like getting, like, summaries of what the agents are doing.
Yeah.
Why can’t they share state easily? Because, like, a read-only agent needs to, like, read parts of the context and figure out what’s relevant to say, well, like, what’s actually being written ‘cause the exploration is not super important, or here is the tree of sub-tasks. I feel like there’s so many different fun things that could be done if, like, a really smart person, like, dedicated, like, a whole lot of time to rethink, like, the coding agent experience, and that would be super-duper sick.
Yeah.
Man, I. That would be my dream.
I would point you towards PrimeAgent if you haven’t looked at it. So this, works together with the RLM work. We just, talked to Alex, who is a buddy of Ellen’s, in the chair before you.
Oh, cool.
And like, yeah, it is being worked on, but it’s not super popular yet.
Yep.
And if, like, yeah
Well, yeah. But the hope. Yeah, I would want everyone to, like, just play around
Yeah
With, like, weird things. I have no guarantees that it’ll work, but it seems really interesting from, like, a technical perspective. So yeah, that seems cool and cool.
Seems cool.
Like, I. Like, once we figure out how to give credits out, I would love to, like, give credits out to people like this.
Yeah. You will be in a position to fund research, for sure.
Yeah.
No. Anyway, congrats on all your success. You’ve, like, come s- come such a long way since I first met you, like, and the whole team as well.
Agent State, Memory, and Multi-Agent Coordination
I’d like to think I’m the same person as well.
Yeah. Yeah. I think. But I think, like, you are energized in a way that I have never seen you before because you found your mission.
No. That’s true. That’s definitely true.
And
I was
You are articulating your mission, because you, for many years you complained about the problems, but you didn’t have a solution yet, right? And you, like, you had, you had the rough shape and that, then you had to do it, put in the work.
I will say that is partially because I describe myself as 0% entrepreneurial.
I don’t like startups. I never wanted to be a CEO in my life. I can’t imagine anyone doing this twice. It seems horrible. Honestly, doing it once is pretty bad. When we first were fundraising, an investor asked me, like, “Which CEOs do you look up to?” And I was like, “Ew, why would I look up to those people?”
No offense to anyone. I’m trying to be, like, I’m trying to be genuine and good. I’ve met, like, a lot of really good people, but like, the famous ones have, like, a lot of, like, skeletons in their closet it seems. And I think I just really did feel disempowered when I was at OpenAI. Like, I felt, Yeah. Like n- it’s, it’s a little bit easier to be truthful now because, like, I have at least some proof that the direction has legs. Like, I just felt like in the insane house where everyone is just like, “ChatGPT, yeah. Like, where do we put ChatGPT in everything? How do we make ChatGPT good for, like, developers and stuff?” And I’m like, “What are you talking about? Like, the function calling interface is insane. Why would you deploy this?” like, this is, this is so anti-developer.
It’s sort of a hacky way on top of hacks on top of hacks.
Well
Yeah
Not just that. Like, the thing I often said was if there was like a, y- l This is also probably tea I don’t have time for right now, but I always used to say, like, “I want to be removed from any project involving, like, function calling if you did not get a logit bias for each function.” Like, so very Very simple ask in my part. Because
Which is something like a confidence, but not calibrated.
Oh, or a probability for it, right?
Yeah.
Like, we need to give users the ability to control, like, let’s say they have actions
Oh, yeah
Or refuse or allow. Yeah, Disney needs to set a different refusal threshold than AI dungeon. The only way to control that with function calling right now is to say, like, “Pretty please.”? That’s nuts. That’s a nuts interface for developers and like, people have been, like, dealing with this for years now, right? Like, they still have that with skills. Like, the existing coding agents are, like, highly overfit to their existing harness ‘cause they’re jagged. They don’t tend to use, like, external, like, tools and MCPs super well because of overfitting, of course. And like, why can’t, like, big companies allow for, like, these slight nudges to be like, “Call this more. It’s really useful.”
Right? And like, the solution is begging in a system message. That’s nuts.
But no, okay. I think I think I get you. And like, man, it is so exciting to talk about all this stuff.
Thank you.
It’s, it’s really cool to get you on the podcast.
Yay.
You’re gonna go, do amazing things, man. Like, I’m excited for your next, big launches, whatever it is.
Oh, hell yeah.
Yeah.
Just you wait.
Yeah.
Just you wait. It might be sooner than you think.
So hiring data people, infra people, I assume, marketer.
100 feel. Depends on who you ask.
Community person.
If you ask me
Yeah
I feel like I’m a pretty good founding marketer. But if you ask anyone on my team, they say, “Shut the fuck up, Diego. You need to do CEO stuff.” So yes, founding marketer
And it’s not just about spice. Like, I think you’re very spice-oriented, which, like, you, like, that’s Your unique talent. But sometimes you just need to say
I know, I know
Like, yeah.
I would really love
Do team, multi-team things. Yeah.
Yes, I. Nothing teaches you delegation like having a tidal wave of stuff to do. Hiring data people, or we call them model capabilities, like, but they are data people, bo- like, data’s kind of a slur in the industry. And like, I want to make sure they
I don’t think so. We’re very pro-data here.
Yeah, but I want them to be the highest status of, like, the people actually working on the model that actually sounds a little weird. I want everyone to have equal status, but like, I want to even that out And I want to know that’s really valuable.
These are more equal than others.
Well. I don’t like weird hierarchies and I think one of the things I’m most proud about in the company is that they don’t respect me that much or they don’t show that. They troll me and like, joke with me and they treat me poorly sometimes and all of that. And I think that’s a good sign of a culture. We’re hiring, like, platform people, like people to, like, build out Jev everywhere. Like, we are so much more sensitive to location because speed of light is more of a bottleneck.
Right? Like, I’m so sad for the European users that we were only, like, three times as fast instead of, like, 100 times as fast because, like, we don’t have servers there right now. And like, that’s insane, right? But like
It’s okay. Life in Europe goes a bit slower as well. It’s okay.
Wow, I can’t believe you. You said it, not me. Or everywhere.
Closing: Hiring and the AWS of Intelligence
Yeah.
Like, if intelligence per second is a metric that matters, like, we’ll launch this all over the place. Like, we care about. Like, if they’re a developer building on top of us, I care a lot about you. And we are hiring for people to keep building more s- l- like, not just. Like, the goal is not to just be, like, Jev as a company. The goal is to, like, ship more shapes of intelligence beyond that. So we are hiring people to, like, build those things too. Like, we want to not just be, like, yeah, like, the one-trick pony of, like, the simple model. But like, I think that there’s gonna be, like, an AWS of, like, intelligence? And
Which is gonna be you, by the way, right? Yes.
Like, that’s a direction I want to go down.
Yes. Okay.
It’d be arrogant to say it will be me.
Yeah.
Like, we. Like, I’m going to do anything I can to make sure that happens.
Yeah.
Like, I think that’s gonna be so cool. Like, we are playing with, like, System 1 intelligence right now. Imagine the layers? Like, this is like the TCP of it.
Yeah. Several more layers to go.
Yeah.
And who knows what else? I’ve also pitched Temporal, by the way. I don’t know. We need to talk about Temporal as layer eight
Ooh
Out of the seven layers.
Ooh.
But anyway, we can talk forever.
Hell yeah.
You gotta get back to work or sleep.
Yep.
Thank you for coming.
Oh, boy. Yeah. Cool. You’re most welcome. It was a pleasure, man.
Yeah.
So excited.
Yeah.
So excited.
Not the last time.
You came the first time. It
Not the last time.
逐字稿與節目內容來自 Latent Space,版權屬原作者。 閱讀原文 ↗