Latent Space: The AI Engineer Podcast

Join Kyle, Nader, Vibhu, and swyx live at NVIDIA GTC next week!
Now that AIE Europe tix are ~sold out, our attention turns to Miami and World’s Fair!
The definitive AI Accelerator chip company has more than 10xed this AI Summer:
And is now a $4.4 trillion megacorp… that is somehow still moving like a startup. We are blessed to have a unique relationship with our first ever NVIDIA guests: Kyle Kranen who gave a great inference keynote at the first World’s Fair and is one of the leading architects of NVIDIA Dynamo (a Datacenter scale inference framework supporting SGLang, TRT-LLM, vLLM), and Nader Khalil, a friend of swyx from our days in Celo in The Arena, who has been drawing developers at GTC since before they were even a glimmer in the eye of NVIDIA:

Nader discusses how NVIDIA Brev has drastically reduced the barriers to entry for developers to get a top of the line GPU up and running, and Kyle explains NVIDIA Dynamo as a data center scale inference engine that optimizes serving by scaling out, leveraging techniques like prefill/decode disaggregation, scheduling, and Kubernetes-based orchestration, framed around cost, latency, and quality tradeoffs.
We also dive into Jensen’s “SOL” (Speed of Light) first-principles urgency concept, long-context limits and model/hardware co-design, internal model APIs (https://build.nvidia.com), and upcoming Dynamo and agent sessions at GTC.

Full Video pod on YouTube
Timestamps
00:00 Agent Security Basics00:39 Podcast Welcome and Guests07:19 Acquisition and DevEx Shift13:48 SOL Culture and Dynamo Setup27:38 Why Scale Out Wins29:02 Scale Up Limits Explained30:24 From Laptop to Multi Node33:07 Cost Quality Latency Tradeoffs38:42 Disaggregation Prefill vs Decode41:05 Kubernetes Scaling with Grove43:20 Context Length and Co Design57:34 Security Meets Agents58:01 Agent Permissions Model59:10 Build Nvidia Inference Gateway01:01:52 Hackathons And Autonomy Dreams01:10:26 Local GPUs And Scaling Inference01:15:31 Long Running Agents And SF Reflections
Transcript
Agent Security Basics
Nader: Agents can do three things. They can access your files, they can access the internet, and then now they can write custom code and execute it. You literally only let an agent do two of those three things. If you can access your files and you can write custom code, you don’t want internet access because that’s one to see full vulnerability, right?
If you have access to internet and your file system, you should know the full scope of what that agent’s capable of doing. Otherwise, now we can get injected or something that can happen. And so that’s a lot of what we’ve been thinking about is like, you know, how do we both enable this because it’s clearly the future.
But then also, you know, what, what are these enforcement points that we can start to like protect?
swyx: All right.
Podcast Welcome and Guests
swyx: Welcome to the Lean Space podcast in the Chromo studio. Welcome to all the guests here. Uh, we are back with our guest host Viu. Welcome. Good to have you back. And our friends, uh, Netter and Kyle from Nvidia. Welcome.
Kyle: Yeah, thanks for having us.
swyx: Yeah, thank you. Actually, I don’t even know your titles.
Uh, I know you’re like architect something of Dynamo.
Kyle: Yeah. I, I’m one of the engineering leaders [00:01:00] and a architects of Dynamo.
swyx: And you’re director of something and developers, developer tech.
Nader: Yeah.
swyx: You’re the developers, developers, developers guy at nvidia,
Nader: open source agent marketing, brev,
swyx: and like
Nader: Devrel tools and stuff.
swyx: Yeah. Been
Nader: the focus.
swyx: And we’re, we’re kind of recording this ahead of Nvidia, GTC, which is coming to town, uh, again, uh, or taking over town, uh, which, uh, which we’ll all be at. Um, and we’ll talk a little bit about your sessions and stuff. Yeah.
Nader: We’re super excited for it.
GTC Booth Stunt Stories
swyx: One of my favorite memories for Nader, like you always do like marketing stunts and like while you were at Rev, you like had this surfboard that you like, went down to GTC with and like, NA Nvidia apparently, like did so much that they bought you.
Like what, what was that like? What was that?
Nader: Yeah. Yeah, we, we, um. Our logo was a chaka. We, we, uh, we were always just kind of like trying to keep true to who we were. I think, you know, some stuff, startups, you’re like trying to pretend that you’re a bigger, more mature company than you are. And it was actually Evan Conrad from SF Compute who was just like, you guys are like previous
swyx: guest.
Yeah.
Nader: Amazing. Oh, really? Amazing. Yeah. He was just like, guys, you’re two dudes in the room. Why are you [00:02:00] pretending that you’re not? Uh, and so then we were like, okay, let’s make the logo a shaka. We brought surfboards to our booth to GTC and the energy was great. Yeah. Some palm trees too. They,
Kyle: they actually poked out over like the, the walls so you could, you could see the bread booth.
Oh, that’s so funny. And
Nader: no one else,
Kyle: just from very far away.
Nader: Oh, so you remember it back
Kyle: then? Yeah I remember it pre-acquisition. I was like, oh, those guys look cool,
Nader: dude. That makes sense. ‘cause uh, we, so we signed up really last minute, and so we had the last booth. It was all the way in the corner. And so I was, I was worried that no one was gonna come.
So that’s why we had like the palm trees. We really came in with the surfboards. We even had one of our investors bring her dog and then she was just like walking the dog around to try to like, bring energy towards our booth. Yeah.
swyx: Steph.
Kyle: Yeah. Yeah, she’s the best,
swyx: you know, as a conference organizer, I love that.
Right? Like, it’s like everyone who sponsors a conference comes, does their booth. They’re like, we are changing the future of ai or something, some generic b******t and like, no, like actually try to stand out, make it fun, right? And people still remember it after three years.
Nader: Yeah. Yeah. You know what’s so funny?
I’ll, I’ll send, I’ll give you this clip if you wanna, if you wanna add it [00:03:00] in, but, uh, my wife was at the time fiance, she was in medical school and she came to help us. ‘cause it was like a big moment for us. And so we, we bought this cricket, it’s like a vinyl, like a vinyl, uh, printer. ‘cause like, how else are we gonna label the surfboard?
So, we got a surfboard, luckily was able to purchase that on the company card. We got a cricket and it was just like fine tuning for enterprises or something like that, that we put on the. On the surfboard and it’s 1:00 AM the day before we go to GTC. She’s helping me put these like vinyl stickers on.
And she goes, you son of, she’s like, if you pull this off, you son of a b***h. And so, uh, right. Pretty much after the acquisition, I stitched that with the mag music acquisition. I sent it to our family group chat. Oh
swyx: Yeah. No, well, she, she made a good choice there. Was that like basically the origin story for Launchable is that we, it was, and maybe we should explain what Brev is and
Nader: Yeah.
Yeah. Uh, I mean, brev is just, it’s a developer tool that makes it really easy to get a GPU. So we connect a bunch of different GPU sources. So the basics of it is like, how quickly can we SSH you into a G, into a GPU and whenever we would talk to users, they wanted A GPU. They wanted an A 100. And if you go to like any cloud [00:04:00] provisioning page, usually it’s like three pages of forms or in the forms somewhere there’s a dropdown.
And in the dropdown there’s some weird code that you know to translate to an A 100. And I remember just thinking like. Every time someone says they want an A 100, like the piece of text that they’re telling me that they want is like, stuffed away in the corner. Yeah. And so we were like, what if the biggest piece of text was what the user’s asking for?
And so when you go to Brev, it’s just big GPU chips with the type that you want with
swyx: beautiful animations that you worked on pre, like pre you can, like, now you can just prompt it. But back in the day. Yeah. Yeah. Those were handcraft, handcrafted artisanal code.
Nader: Yeah. I was actually really proud of that because, uh, it was an, i I made it in Figma.
Yeah. And then I found, I was like really struggling to figure out how to turn it from like Figma to react. So what it actually is, is just an SVG and I, I have all the styles and so when you change the chip, whether it’s like active or not it changes the SVG code and that somehow like renders like, looks like it’s animating, but it, we just had the transition slow, but it’s just like the, a JavaScript function to change the like underlying SVG.
Yeah. And that was how I ended up like figuring out how to move it from from Figma. But yeah, that’s Art Artisan. [00:05:00]
Kyle: Speaking of marketing stunts though, he actually used those SVGs. Or kind of use those SVGs to make these cards.
Nader: Oh yeah. Like
Kyle: a GPU gift card Yes. That he handed out everywhere. That was actually my first impression of that
Nader: one.
Yeah,
swyx: yeah, yeah.
Nader: Yeah.
swyx: I think I still have one of them.
Nader: They look great.
Kyle: Yeah.
Nader: I have a ton of them still actually in our garage, which just, they don’t have labels. We should honestly like bring, bring them back. But, um, I found this old printing press here, actually just around the corner on Ven ness. And it’s a third generation San Francisco shop.
And so I come in an excited startup founder trying to like, and they just have this crazy old machinery and I’m in awe. ‘cause the the whole building is so physical. Like you’re seeing these machines, they have like pedals to like move these saws and whatever. I don’t know what this machinery is, but I saw all three generations.
Like there’s like the grandpa, the father and the son, and the son was like, around my age. Well,
swyx: it’s like a holy, holy trinity.
Nader: It’s funny because we, so I just took the same SVG and we just like printed it and it’s foil printing, so they make a a, a mold. That’s like an inverse of like the A 100 and then they put the foil on it [00:06:00] and then they press it into the paper.
And I remember once we got them, he was like, Hey, don’t forget about us. You know, I guess like early Apple and Cisco’s first business cards were all made there. And so he was like, yeah, we, we get like the startup businesses but then as they mature, they kind of go somewhere else. And so I actually, I think we were talking with marketing about like using them for some, we should go back and make some cards.
swyx: Yeah, yeah, yeah. You know, I remember, you know, as a very, very small breadth investor, I was like, why are we spending time like, doing these like stunts for GPUs? Like, you know, I think like as a, you know, typical like cloud hard hardware person, you go into an AWS you pick like T five X xl, whatever, and it’s just like from a list and you look at the specs like, why animate this GP?
And, and I, I do think like it just shows the level of care that goes throughout birth and Yeah. And now, and also the, and,
Nader: and Nvidia. I think that’s what the, the thing that struck me most when we first came in was like the amount of passion that everyone has. Like, I think, um, you know, you talk to, you talk to Kyle, you talk to, like, every VP that I’ve met at Nvidia goes so close to the metal.
Like, I remember it was almost a year ago, and like my VP asked me, he’s like, Hey, [00:07:00] what’s cursor? And like, are you using it? And if so, why? Surprised at this, and he downloaded Cursor and he was asking me to help him like, use it. And I thought that was, uh, or like, just show him what he, you know, why we were using it.
And so, the amount of care that I think everyone has and the passion, appreciate, passion and appreciation for the moment. Right. This is a very unique time. So it’s really cool to see everyone really like, uh, appreciate that.
swyx: Yeah.
Acquisition and DevEx Shift
swyx: One thing I wanted to do before we move over to sort of like research topics and, uh, the, the stuff that Kyle’s working on is just tell the story of the acquisition, right?
Like, not many people have been, been through an acquisition with Nvidia. What’s it like? Uh, what, yeah, just anything you’d like to say.
Nader: It’s a crazy experience. I think, uh, you know, we were the thing that was the most exciting for us was. Our goal was just to make it easier for developers.
We wanted to find access to GPUs, make it easier to do that. And then all, oh, actually your question about launchable. So launchable was just make one click exper, like one click deploys for any software on top of the GPU. Mm-hmm. And so what we really liked about Nvidia was that it felt like we just got a lot more resources to do all of that.
I think, uh, you [00:08:00] know, NVIDIA’s goal is to make things as easy for developers as possible. So there was a really nice like synergy there. I think that, you know, when it comes to like an acquisition, I think the amount that the soul of the products align, I think is gonna be. Is going speak to the success of the acquisition.
Yeah. And so it in many ways feels like we’re home. This is a really great outcome for us. Like we you know, I love brev.nvidia.com. Like you should, you should use it’s, it’s the
Kyle: front page for GPUs.
Nader: Yeah. Yeah. If you want GP views,
Kyle: you go there, get
swyx: it there, and it’s like internally is growing very quickly.
I, I don’t remember You said some stats there.
Nader: Yeah, yeah, yeah. It’s, uh, I, I wish I had the exact numbers, but like internally, externally, it’s been growing really quickly. We’ve been working with a bunch of partners with a bunch of different customers and ISVs, if you have a solution that you want someone that runs on the GPU and you want people to use it quickly, we can bundle it up, uh, in a launchable and make it a one click run.
If you’re doing things and you want just like a sandbox or something to run on, right. Like open claw. Huge moment. Super exciting. Our, uh, and we’ll talk into it more, but. You know, internally, people wanna run this, and you, we know we have to be really careful from the security implications. Do we let this run on the corporate network?
Security’s guidance was, Hey, [00:09:00] run this on breath, it’s in, you know, it’s, it’s, it’s a vm, it’s sitting in the cloud, it’s off the corporate network. It’s isolated. And so that’s been our stance internally and externally about how to even run something like open call while we figure out how to run these things securely.
But yeah,
swyx: I think there’s also like, you almost like we’re the right team at the right time when Nvidia is starting to invest a lot more in developer experience or whatever you call it. Yeah. Uh, UX or I don’t know what you call it, like software. Like obviously NVIDIA is always invested in software, but like, there’s like, this is like a different audience.
Yeah. It’s a
Nader: wider
Kyle: developer base.
swyx: Yeah. Right.
Nader: Yeah. Yeah. You know, it’s funny, it’s like, it’s not, uh,
swyx: so like, what, what is it called internally? What, what is this that people should be aware that is going on there?
Nader: Uh, what, like developer experience
swyx: or, yeah, yeah. Is it’s called just developer experience or is there like a broader strategy here
Nader: in Nvidia?
Um, Nvidia always wants to make a good developer experience. The thing is and a lot of the technology is just really complicated. Like, it’s not, it’s uh, you know, I think, um. The thing that’s been really growing or the AI’s growing is having a huge moment, not [00:10:00] because like, let’s say data scientists in 2018, were quiet then and are much louder now.
The pie is com, right? There’s a whole bunch of new audiences. My mom’s wondering what she’s doing. My sister’s learned, like taught herself how to code. Like the, um, you know, I, I actually think just generally AI’s a big equalizer and you’re seeing a more like technologically literate society, I guess.
Like everyone’s, everyone’s learning how to code. Uh, there isn’t really an excuse for that. And so building a good UX means that you really understand who your end user is. And when your end user becomes such a wide, uh, variety of people, then you have to almost like reinvent the practice, right? Yeah. You have
Kyle: to, and actually build more developer ux, right?
Because the, there are tiers of developer base that were added. You know, the, the hackers that are building on top of open claw, right? For example, have never used gpu. They don’t know what kuda is. They, they, they just want to run something.
Nader: Yeah.
Kyle: You need new UX that is not just. Hey, you know, how do you program something in Cuda and run it?
And then, and then we built, you know, like when Deep Learning was getting big, we built, we built Torch and, and, but so recently the amount of like [00:11:00] layers that are added to that developer stack has just exploded because AI has become ubiquitous. Everyone’s using it in different ways. Yeah. It’s
Nader: moving fast in every direction.
Vertical, horizontal.
Vibhu: Yeah. You guys, you even take it down to hardware, like the DGX Spark, you know, it’s, it’s basically the same system as just throwing it up on big GPU cluster.
Nader: Yeah, yeah, yeah. It’s amazing. Blackwell.
swyx: Yeah. Uh, we saw the preview at the last year’s GTC and that was one of the better performing, uh, videos so far, and video coverage so far.
Awesome. This will beat it. Um,
Nader: that was
swyx: actually, we have fingers
Nader: crossed. Yeah.
DGX Spark and Remote Access
Nader: Even when Grace Blackwell or when, um, uh, DGX Spark was first coming out getting to be involved in that from the beginning of the developer experience. And it just comes back to what you
swyx: were involved.
Nader: Yeah. St. St.
swyx: Mars.
Nader: Yeah. Yeah. I mean from, it was just like, I, I got an email, we just got thrown into the loop and suddenly yeah, I, it was actually really funny ‘cause I’m still pretty fresh from the acquisition and I’m, I’m getting an email from a bunch of the engineering VPs about like, the new hardware, GPU chip, like we’re, or not chip, but just GPU system that we’re putting out.
And I’m like, okay, cool. Matters. Now involved with this for the ux, I’m like. What am I gonna do [00:12:00] here? So, I remember the first meeting, I was just like kind of quiet as I was hearing engineering VPs talk about what this box could be, what it could do, how we should use it. And I remember, uh, one of the first ideas that people were idea was like, oh, the first thing that it was like, I think a quote was like, the first thing someone’s gonna wanna do with this is get two of them and run a Kubernetes cluster on top of them.
And I was like, oh, I think I know why I’m here. I was like, the first thing we’re doing is easy. SSH into the machine. And then, and you know, just kind of like scoping it down of like, once you can do that every, you, like the person who wants to run a Kubernetes cluster onto Sparks has a higher propensity for pain, then, then you know someone who buys it and wants to run open Claw right now, right?
If you can make sure that that’s as effortless as possible, then the rest becomes easy. So there’s a tool called Nvidia Sync. It just makes the SSH connection really simple. So, you know, if you think about it like. If you have a Mac, uh, or a PC or whatever, if you have a laptop and you buy this GPU and you want to use it, you should be able to use it like it’s A-A-G-P-U in the cloud, right?
Um, but there’s all this friction of like, how do you actually get into that? That’s part of [00:13:00] Revs value proposition is just, you know, there’s a CLI that wraps SSH and makes it simple. And so our goal is just get you into that machine really easily. And one thing we just launched at CES, it’s in, it’s still in like early access.
We’re ironing out some kinks, but it should be ready by GTC. You can register your spark on Brev. And so now if you
swyx: like remote managed yeah, local hardware. Single pane of glass. Yeah. Yeah. Because Brev can already manage other clouds anyway, right?
Vibhu: Yeah, yeah. And you use the spark on Brev as well, right?
Nader: Yeah. But yeah, exactly. So, so you, you, so you, you set it up at home you can run the command on it, and then it gets it’s essentially it’ll appear in your Brev account, and then you can take your laptop to a Starbucks or to a cafe, and you’ll continue to use your, you can continue use your spark just like any other cloud node on Brev.
Yeah. Yeah. And it’s just like a pre-provisioned center
swyx: in your
Nader: home. Yeah, exactly.
swyx: Yeah. Yeah.
Vibhu: Tiny little data center.
Nader: Tiny little, the size of
Vibhu: your phone.
SOL Culture and Dynamo Setup
swyx: One more thing before we move on to Kyle. Just have so many Jensen stories and I just love, love mining Jensen stories. Uh, my favorite so far is SOL. Uh, what is, yeah, what is S-O-L-S-O-L
Nader: is actually, i, I think [00:14:00] of all the lessons I’ve learned, that one’s definitely my favorite.
Kyle: It’ll always stick with you.
Nader: Yeah. Yeah. I, you know, in your startup, everything’s existential, right? Like we’ve, we’ve run out of money. We were like, on the risk of, of losing payroll, we’ve had to contract our team because we l ran outta money. And so like, um, because of that you’re really always forcing yourself to I to like understand the root cause of everything.
If you get a date, if you get a timeline, you know exactly why that date or timeline is there. You’re, you’re pushing every boundary and like, you’re not just say, you’re not just accepting like a, a no. Just because. And so as you start to introduce more layers, as you start to become a much larger organization, SOL is is essentially like what is the physics, right?
The speed of light moves at a certain speed. So if flight’s moving some slower, then you know something’s in the way. So before trying to like layer reality back in of like, why can’t this be delivered at some date? Let’s just understand the physics. What is the theoretical limit to like, uh, how fast this can go?
And then start to tell me why. ‘cause otherwise people will start telling you why something can’t be done. But actually I think any great leader’s goal is just to create urgency. Yeah. [00:15:00] There’s an infinite
Kyle: create compelling events, right?
Nader: Yeah.
Kyle: Yeah. So l is a term video is used to instigate a compelling event.
You say this is done. How do we get there? What is the minimum? As much as necessary, as little as possible thing that it takes for us to get exactly here and. It helps you just break through a bunch of noise.
swyx: Yeah.
Kyle: Instantly.
swyx: One thing I’m unclear about is, can only Jensen use the SOL card? Like, oh, no, no, no.
Not everyone get the b******t out because obviously it’s Jensen, but like, can someone else be like, no, like
Kyle: frontline engineers use it.
Nader: Yeah. Every, I think it’s not so much about like, get the b******t out. It’s like, it’s like, give me the root understanding, right? Like, if you tell me something takes three weeks, it like, well, what’s the first principles?
Yeah, the first principles. It’s like, what’s the, what? Like why is it three weeks? What is the actual yeah. What’s the actual limit of why this is gonna take three weeks? If you’re gonna, if you, if let’s say you wanted to buy a new computer and someone told you it’s gonna be here in five days, what’s the SOL?
Well, like the SOL is like, I could walk into a Best Buy and pick it up for you. Right? So then anything that’s like beyond that is, and is that practical? Is that how we’re gonna, you know, let’s say give everyone in the [00:16:00] company a laptop, like obviously not. So then like that’s the SOL and then it’s like, okay, well if we have to get more than 10, suddenly there might be some, right?
And so now we can kind of piece the reality back.
swyx: So, so this is the. Paul Graham do things that don’t scale. Yeah. And this is also the, what people would now call behi agency. Yeah.
Kyle: It’s actually really interesting because there’s a, there’s a second hardware angle to SOL that like doesn’t come up for all the org sol is used like culturally at a
swyx: media for everything.
I’m also mining for like, I think that can be annoying sometimes. And like someone keeps going IOO you and you’re like, guys, like we have to be stable. We have to, we to f*****g plan. Yeah.
Kyle: It’s an interesting balance.
Nader: Yeah. I encounter that with like, actually just with, with Alec, right? ‘cause we, we have a new conference so we need to launch, we have, we have goals of what we wanna launch by, uh, by the conference and like, yeah.
At the end of the day, where is
swyx: this GTC?
Nader: Um, well this is like, so we, I mean we did it for CES, we did for GT CDC before that we’re doing it for GTC San Jose. So I mean, like every, you know, we have a new moment. Um, and we want to launch something. Yeah. And we want to do so at SOL and that does mean that some, there’s some level of prioritization that needs [00:17:00] to happen.
And so it, it is difficult, right? I think, um, you have to be careful with what you’re pushing. You know, stability is important and that should be factored into S-O-L-S-O-L isn’t just like, build everything and let it break, you know, that, that’s part of the conversation. So as you’re laying, layering in all the details, one of them might be, Hey, we could build this, but then it’s not gonna be stable for X, y, z reasons.
And so that was like, one of our conversations for CES was, you know, hey, like we, we can get this into early access registering your spark with brev. But there are a lot of things that we need to do in order to feel really comfortable from a security perspective, right? There’s a lot of networking involved before we deliver that to users.
So it’s like, okay. Let’s get this to a point where we can at least let people experiment with it. We had it in a booth, we had it in Jensen’s keynote, and then let’s go iron out all the networking kinks. And that’s not easy. And so, uh, that can come later. And so that was the way that we layered that back in.
Yeah. But
Kyle: It’s not really about saying like, you don’t have to do the, the maintenance or operational work. It’s more about saying, you know, it’s kind of like [00:18:00] highlights how progress is incremental, right? Like, what is the minimum thing that we can get to. And then there’s SOL for like every component after that.
But there’s the SOL to get you, get you to the, the starting line. And that, that’s usually how it’s asked. Yeah. On the other side, you know, like SOL came out of like hardware at Nvidia. Right. So SOL is like literally if we ran the accelerator or the GPU with like at basically full speed with like no other constraints, like how FAST would be able to make a program go.
swyx: Yeah. Yeah. Right.
Kyle: So
swyx: in, in training that like, you know, then you work back to like some percentage of like MFU for example.
Kyle: Yeah, that’s a, that’s a great example. So like, there’s an, there’s an S-O-L-M-F-U, and then there’s like, you know, what’s practically achievable.
swyx: Cool. Should we move on to sort of, uh, Kyle’s side?
Uh, Kyle, you’re coming more from the data science world. And, uh, I, I mean I always, whenever, whenever I meet someone who’s done working in tabular stuff, graph neural networks, time series, these are basically when I go to new reps, I go to ICML, I walk the back halls. There’s always like a small group of graph people.
Yes. Absolute small group of tabular people. [00:19:00] And like, there’s no one there. And like, it’s very like, you know what I mean? Like, yeah, no, like it’s, it’s important interesting work if you care about solving the problems that they solve.
Kyle: Yeah.
swyx: But everyone else is just LMS all the time.
Kyle: Yeah. I mean it’s like, it’s like the black hole, right?
Has the event horizon reached this yet in nerves? Um,
swyx: but like, you know, those are, those are transformers too. Yeah. And, and those are also like interesting things. Anyway, uh, I just wanted to spend a little bit of time on, on those, that background before we go into Dynamo, uh, proper.
Kyle: Yeah, sure. I took a different path to Nvidia than that, or I joined six years ago, seven, if you count, when I was an intern.
So I joined Nvidia, like right outta college. And the first thing I jumped into was not what I’d done in, during internship, which was like, you know, like some stuff for autonomous vehicles, like heavyweight object detection. I jumped into like, you know, something, I’m like, recommenders, this is popular. And
swyx: yeah, he did Rexi
Kyle: as well.
Yeah, Rexi. Yeah. I mean that, that was the taboo data at the time, right? You have tables of like, audience qualities and item qualities, and you’re trying to figure out like which member of [00:20:00] the audience matches which item or, or more practically which item matches which member of the audience. And at the time, really it was like we were trying to enable.
Uh, recommender, which had historically been like a little bit of a CP based workflow into something that like, ran really well in GPUs. And it’s since been done. Like there are a bunch of libraries for Axis that run on GPUs. Uh, the common models like Deeplearning recommendation model, which came outta meta and the wide and deep model, which was used or was released by Google were very accelerated by GPUs using, you know, the fast HBM on the chips, especially to do, you know, vector lookups.
But it was very interesting at the time and super, super relevant because like we were starting to get like. This explosion of feeds and things that required rec recommenders to just actively be on all the time. And sort of transitioned that a little bit towards graph neural networks when I discovered them because I was like, okay, you can actually use graphical neural networks to represent like, relationships between people, items, concepts, and that, that interested me.
So I jumped into that at [00:21:00] Nvidia and, and got really involved for like two-ish years.
swyx: Yeah. Uh, and something I learned from Brian Zaro Yeah. Is that you can just kind of choose your own path in Nvidia.
Kyle: Oh my God. Yeah.
swyx: Which is not a normal big Corp thing. Yeah. Like you, you have a lane, you stay in your lane.
Nader: I think probably the reason why I enjoy being in a, a big company, the mission is the boss probably from a startup guy. Yeah. The mission
swyx: is the boss.
Nader: Yeah. Uh, it feels like a big game of pickup basketball. Like, you know, if you play one, if you wanna play basketball, you just go up to the court and you’re like, Hey look, we’re gonna play this game and we need three.
Yeah. And you just like find your three. That’s honestly for every new initiative that’s what it feels like. Yeah.
Vibhu: It also like shows, right? Like Nvidia. Just releasing state-of-the-art stuff in every domain. Yeah. Like, okay, you expect foundation models with Nemo tron voice just randomly parakeet.
Call parakeet just comes out another one, uh, voice. The
Kyle: video voice team has always been producing.
Vibhu: Yeah. There’s always just every other domain of paper that comes out, dataset that comes out. It’s like, I mean, it also stems back to what Nvidia has to do, right? You have to make chips years before they’re actually produced.
Right? So you need to know, you need to really [00:22:00] focus. The
Kyle: design process starts like
Vibhu: exactly
Kyle: three to five years before the chip gets to the market.
Vibhu: Yeah. I, I’m curious more about what that’s like, right? So like, you have specialist teams. Is it just like, you know, people find an interest, you go in, you go deep on whatever, and that kind of feeds back into, you know, okay, we, we expect predictions.
Like the internals at Nvidia must be crazy. Right? You know? Yeah. Yeah. You know, you, you must. Not even without selling to people, you have your own predictions of where things are going. Yeah. And they’re very based, very grounded. Right?
Kyle: Yeah. It, it, it’s really interesting. So there’s like two things that I think that Amed does, which are quite interesting.
Uh, one is like, we really index into passion. There’s a big. Sort of organizational top sound push to like ensure that people are working on the things that they’re passionate about. So if someone proposes something that’s interesting, many times they can just email someone like way up the chain that they would find this relevant and say like, Hey, can I go work on this?
Nader: It’s actually like I worked at a, a big company for a couple years before, uh, starting on my startup journey and like, it felt very weird if you were to like email out of chain, if that makes [00:23:00] sense. Yeah. The emails at Nvidia are like mosh pits
swyx: shoot,
Nader: and it’s just like 60 people, just whatever. And like they’re, there’s this,
swyx: they got messy like, reply all you,
Nader: oh, it’s in, it’s insane.
It’s insane. They just
Kyle: help. You know, Maxim,
Nader: the context. But, but that’s actually like, I’ve actually, so this is a weird thing where I used to be like, why would we send emails? We have Slack. I am the entire, I’m the exact opposite. I feel so bad for anyone who’s like messaging me on Slack ‘cause I’m so unresponsive.
swyx: Your email
Nader: Maxi, email Maxim. I’m email maxing Now email is a different, email is perfect because man, we can’t work together. I’m email is great, right? Because important threads get bumped back up, right? Yeah, yeah. Um, and so Slack doesn’t do that. So I just have like this casino going off on the right or on the left and like, I don’t know which thread was from where or what, but like the threads get And then also just like the subject, so you can have like working threads.
I think what’s difficult is like when you’re small, if you’re just not 40,000 people I think Slack will work fine, but there’s, I don’t know what the inflection point is. There is gonna be a point where that becomes really messy and you’ll actually prefer having email. ‘cause you can have working threads.
You can cc more than nine people in a thread.
Kyle: You can fork stuff.
Nader: You can [00:24:00] fork stuff, which is super nice and just like y Yeah. And so, but that is part of where you can propose a plan. You can also just. Start, honestly, momentum’s the only authority, right? So like, if you can just start, start to make a little bit of progress and show someone something, and then they can try it.
That’s, I think what’s been, you know, I think the most effective way to push anything for forward. And that’s both at Nvidia and I think just generally.
Kyle: Yeah, there’s, there’s the other concept that like is explored a lot at Nvidia, which is this idea of a zero billion dollar business. Like market creation is a big thing at Nvidia.
Like,
swyx: oh, you want to go and start a zero billion dollar business?
Kyle: Jensen says, we are completely happy investing in zero billion dollar markets. We don’t care if this creates revenue. It’s important for us to know about this market. We think it will be important in the future. It can be zero billion dollars for a while.
I’m probably minging as words here for, but like, you know, like, I’ll give an example. NVIDIA’s been working on autonomous driving for a a long time,
swyx: like an Nvidia car.
Kyle: No, they, they’ve
Vibhu: used the Mercedes, right? They’re around the HQ and I think it finally just got licensed out. Now they’re starting to be used quite a [00:25:00] bit.
For 10 years you’ve been seeing Mercedes with Nvidia logos driving.
Kyle: If you’re in like the South San Santa Clara, it’s, it’s actually from South. Yeah. So, um. Zero billion dollar markets are, are a thing like, you know, Jensen,
swyx: I mean, okay, look, cars are not a zero billion dollar market. But yeah, that’s a bad example.
Nader: I think, I think he’s, he’s messaging, uh, zero today, but, or even like internally, right? Like, like it’s like, uh, an org doesn’t have to ruthlessly find revenue very quickly to justify their existence. Right. Like a lot of the important research, a lot of the important technology being developed that, that’s kind of
Kyle: where research, research is very ide ideologically free at Nvidia.
Yeah. Like they can pursue things that they were
swyx: Were you research officially?
Kyle: I was never in research. Officially. I was always in engineering. Yeah. We in, I’m in an org called Deep Warning Algorithms, which is basically just how do we make things that are relevant to deep warning go fast.
swyx: That sounds freaking cool.
Vibhu: And I think a lot of that is underappreciated, right? Like time series. This week Google put out time. FF paper. Yeah. A new time series, paper res. Uh, Symantec, ID [00:26:00] started applying Transformers LMS to Yes. Rec system. Yes. And when you think the scale of companies deploying these right. Amazon recommendations, Google web search, it’s like, it’s huge scale and
Kyle: Yeah.
Vibhu: You want fast?
Kyle: Yeah. Yeah. Yeah. Actually it’s, it, I, there’s a fun moment that brought me like full circle. Like, uh, Amazon Ads recently gave a talk where they talked about using Dynamo for generative recommendation, which was like super, like weirdly cathartic for me. I’m like, oh my God. I’ve, I’ve supplanted what I was working on.
Like, I, you’re using LMS now to do what I was doing five years ago.
swyx: Yeah. Amazing. And let’s go right into Dynamo. Uh, maybe introduce Yeah, sure. To the top down and Yeah.
Kyle: I think at this point a lot of people are familiar with the term of inference. Like funnily enough, like I went from, you know, inference being like a really niche topic to being something that’s like discussed on like normal people’s Twitter feeds.
It’s,
Nader: it’s on billboards
Kyle: here now. Yeah. Very, very strange. Driving, driving, seeing just an inference ad on 1 0 1 inference at scale is becoming a lot more important. Uh, we have these moments like, you know, open claw where you have these [00:27:00] agents that take lots and lots of tokens, but produce, incredible results.
There are many different aspects of test time scaling so that, you know, you can use more inference to generate a better result than if you were to use like a short amount of inference. There’s reasoning, there’s quiring, there’s, adding agency to the model, allowing it to call tools and use skills.
Dyno sort came about at Nvidia. Because myself and a couple others were, were sort of talking about the, these concepts that like, you know, you have inference engines like VLMS, shelan, tenor, TLM and they have like one single copy. They, they, they sort of think about like things as like one single copy, like one replica, right?
Why Scale Out Wins
Kyle: Like one version of the model. But when you’re actually serving things at scale, you can’t just scale up that replica because you end up with like performance problems. There’s a scaling limit to scaling up replicas. So you actually have to scale out to use a, maybe some Kubernetes type terminology.
We kind of realized that there was like. A lot of potential optimization that we could do in scaling out and building systems for data [00:28:00] center scale inference. So Dynamo is this data center scale inference engine that sits on top of the frameworks like VLM Shilling and 10 T lm and just makes things go faster because you can leverage the economy of scale.
The fact that you have KV cash, which we can define a little bit later, uh, in all these machines that is like unique and you wanna figure out like the ways to maximize your cash hits or you want to employ new techniques in inference like disaggregation, which Dynamo had introduced to the world in, in, in March, not introduced, it was a academic talk, but beforehand.
But we are, you know, one of the first frameworks to start, supporting it. And we wanna like, sort of combine all these techniques into sort of a modular framework that allows you to. Accelerate your inference at scale.
Nader: By the way, Kyle and I became friends on my first date, Nvidia, and I always loved, ‘cause like he always teaches me
swyx: new things.
Yeah. By the way, this is why I wanted to put two of you together. I was like, yeah, this is, this is gonna be
Kyle: good. It’s very, it’s very different, you know, like we’ve, we, we’ve, we’ve talked to each other a bunch [00:29:00] actually, you asked like, why, why can’t we scale up?
Nader: Yeah.
Scale Up Limits Explained
Nader: model, you said model replicas.
Kyle: Yeah. So you, so scale up means assigning more
swyx: heavier?
Kyle: Yeah, heavier. Like making things heavier. Yeah, adding more GPUs. Adding more CPUs. Scale out is just like having a barrier saying, I’m gonna duplicate my representation of the model or a representation of this microservice or something, and I’m gonna like, replicate it Many times.
Handle, load. And the reason that you can’t scale, scale up, uh, past some points is like, you know, there, there, there are sort of hardware bounds and algorithmic bounds on, on that type of scaling. So I’ll give you a good example that’s like very trivial. Let’s say you’re on an H 100. The Maxim ENV link domain for H 100, for most Ds H one hundreds is heus, right?
So if you scaled up past that, you’re gonna have to figure out ways to handle the fact that now for the GPUs to communicate, you have to do it over Infin band, which is still very fast, but is not as fast as ENV link.
swyx: Is it like one order of magnitude, like hundreds or,
Kyle: it’s about an order of magnitude?
Yeah. Okay. Um, so
swyx: not terrible.
Kyle: [00:30:00] Yeah. I, I need to, I need to remember the, the data sheet here, like, I think it’s like about 500 gigabytes. Uh, a second unidirectional for ENV link, and about 50 gigabytes a second unidirectional for Infin Band. I, it, it depends on the, the generation.
swyx: I just wanna set this up for people who are not familiar with these kinds of like layers and the trash speed
Vibhu: and all that.
Of course.
From Laptop to Multi Node
Vibhu: Also, maybe even just going like a few steps back before that, like most people are very familiar with. You see a, you know, you can use on your laptop, whatever these steel viol, lm you can just run inference there. All, there’s all, you can, you
can run it on that
Vibhu: laptop. You can run on laptop.
Then you get to, okay, uh, models got pretty big, right? JLM five, they doubled the size, so mm-hmm. Uh, what do you do when you have to go from, okay, I can get 128 gigs of memory. I can run it on a spark. Then you have to go multi GPU. Yeah. Okay. Multi GPU, there’s some support there. Now, if I’m a company and I don’t have like.
I’m not hiring the best researchers for this. Right. But I need to go [00:31:00] multi-node, right? I have a lot of servers. Okay, now there’s efficiency problems, right? You can have multiple eight H 100 nodes, but, you know, is that as a, like, how do you do that efficiently?
Kyle: Yeah. How do you like represent them? How do you choose how to represent the model?
Yeah, exactly right. That’s a, that’s like a hard question. Everyone asks, how do you size oh, I wanna run GLM five, which just came out new model. There have been like four of them in the past week, by the way, like a bunch of new models.
swyx: You know why? Right? Deep seek.
Kyle: No comment. Oh. Yeah, but Ggl, LM five, right?
We, we have this, new model. It’s, it’s like a large size, and you have to figure out how to both scale up and scale out, right? Because you have to find the right representation that you care about. Everyone does this differently. Let’s be very clear. Everyone figures this out in their own path.
Nader: I feel like a lot of AI or ML even is like, is like this. I think people think, you know, I, I was, there was some tweet a few months ago that was like, why hasn’t fine tuning as a service taken off? You know, that might be me. It might have been you. Yeah. But people want it to be such an easy recipe to follow.
But even like if you look at an ML model and specific
Kyle: to you Yeah,
Nader: yeah.
Kyle: And the [00:32:00] model,
Nader: the situation, and there’s just so much tinkering, right? Like when you see a model that has however many experts in the ME model, it’s like, why that many experts? I don’t, they, you know, they tried a bunch of things and that one seemed to do better.
I think when it comes to how you’re serving inference, you know, you have a bunch of decisions to make and there you can always argue that you can take something and make it more optimal. But I think it’s this internal calibration and appetite for continued calibration.
Vibhu: Yeah. And that doesn’t mean like, you know, people aren’t taking a shot at this, like tinker from thinking machines, you know?
Yeah. RL as a service. Yeah, totally. It’s, it also gets even harder when you try to do big model training, right? We’re not the best at training Moes, uh, when they’re pre-trained. Like we saw this with LAMA three, right? They’re trained in such a sparse way that meta knows there’s gonna be a bunch of inference done on these, right?
They’ll open source it, but it’s very trained for what meta infrastructure wants, right? They wanna, they wanna inference it a lot. Now the question to basically think about is, okay, say you wanna serve a chat application, a coding copilot, right? You’re doing a layer of rl, you’re serving a model for X amount of people.
Is it a chat model, a coding model? Dynamo, you know, back to that,
Kyle: it’s [00:33:00] like, yeah, sorry. So you we, we sort of like jumped off of, you know, jumped, uh, on that topic. Everyone has like, their own, own journey.
Cost Quality Latency Tradeoffs
Kyle: And I, I like to think of it as defined by like, what is the model you need? What is the accuracy you need?
Actually I talked to NA about this earlier. There’s three axes you care about. What is the quality that you’re able to produce? So like, are you accurate enough or can you complete the task with enough, performance, high enough performance. Yeah, yeah. Uh, there’s cost. Can you serve the model or serve your workflow?
Because it’s not just the model anymore, it’s the workflow. It’s the multi turn with an agent cheaply enough. And then can you serve it fast enough? And we’re seeing all three of these, like, play out, like we saw, we saw new models from OpenAI that you know, are faster. You have like these new fast versions of models.
You can change the amount of thinking to change the amount of quality, right? Produce more tokens, but at a higher cost in a, in a higher latency. And really like when you start this journey of like trying to figure out how you wanna host a model, you, you, you think about three things. What is the model I need to serve?
How many times do I need to call it? What is the input sequence link was [00:34:00] the, what does the workflow look like on top of it? What is the SLA, what is the latency SLA that I need to achieve? Because there’s usually some, this is usually like a constant, you, you know, the SLA that you need to hit and then like you try and find the lowest cost version that hits all of these constraints.
Usually, you know, you, you start with those things and you say you, you kind of do like a bit of experimentation across some common configurations. You change the tensor parallel size, which is a form of parallelism
Vibhu: I take, it goes even deeper first. Gotta think what model.
Kyle: Yes, course,
of
Kyle: course. It’s like, it’s like a multi-step design process because as you said, you can, you can choose a smaller model and then do more test time scaling and it’ll equate the quality of a larger model because you’re doing the test time scaling or you’re adding a harness or something.
So yes, it, it goes way deeper than that. But from the performance perspective, like once you get to the model you need, you need to host, you look at that and you say, Hey. I have this model, I need to serve it at the speed. What is the right configuration for that?
Nader: You guys see the recent, uh, there was a paper I just saw like a few days ago that, uh, if you run [00:35:00] the same prompt twice, you’re getting like double Just try it
again.
Nader: Yeah, exactly.
Vibhu: And you get a lot. Yeah. But the, the key thing there is you give the context of the failed try, right? Yeah. So it takes a shot. And this has been like, you know, basic guidance for quite a while. Just try again. ‘cause you know, trying, just try again. Did you try again? All advice
Nader: in life.
Vibhu: Just, it’s a paper from Google, if I’m not mistaken, right?
Yeah,
Vibhu: yeah. I think it, it’s like a seven bas little short paper. Yeah. Yeah. The title’s very cute. And it’s just like, yeah, just try again. Give it ask context,
Kyle: multi-shot. You just like, say like, hey, like, you know, like take, take a little bit more, take a little bit more information, try and fail. Fail.
Vibhu: And that basic concept has gone pretty deep.
There’s like, um, self distillation, rl where you, you do self distillation, you do rl and you have past failure and you know, that gives some signal so people take, try it again. Not strong enough.
swyx: Uh, for, for listeners, uh, who listen to here, uh, vivo actually, and I, and we run a second YouTube channel for our paper club where, oh, that’s awesome.
Vivo just covered this. Yeah. Awesome. Self desolation and all that’s, that’s why he, to speed [00:36:00] on it.
Nader: I’ll to check it out.
swyx: Yeah. It, it’s just a good practice, like everyone needs, like a paper club where like you just read papers together and the social pressure just kind of forces you to just,
Nader: we, we,
there’s
Nader: like a big inference.
Kyle: Reading
Nader: group at a video. I feel so bad every time. I I, he put it on like, on our, he shared it.
swyx: One, one of
Nader: your guys,
swyx: uh, is, is big in that, I forget es han Yeah, yeah,
Kyle: es Han’s on my team. Actually. Funny. There’s a, there’s a, there’s a employee transfer between us. Han worked for Nater at Brev, and now he, he’s on my team.
He was
Nader: our head of ai. And then, yeah, once we got in, and
swyx: because I’m always looking for like, okay, can, can I start at another podcast that only does that thing? Yeah. And, uh, Esan was like, I was trying to like nudge Esan into like, is there something here? I mean, I don’t think there’s, there’s new infant techniques every day.
So it’s like, it’s like
Kyle: you would, you would actually be surprised, um, the amount of blog posts you see. And if
swyx: there’s a period where it was like, Medusa hydra, what Eagle, like, you
Kyle: know, now we have new forms of decode, uh, we have new forms of specula, of decoding or new,
swyx: what,
Kyle: what are you
Vibhu: excited? And it’s exciting when you guys put out something like Tron.
‘cause I remember the paper on this Tron three, [00:37:00] uh, the amount of like post train, the on tokens that the GPU rich can just train on. And it, it was a hybrid state space model, right? Yeah.
Kyle: It’s co-designed for the hardware.
Vibhu: Yeah, go design for the hardware. And one of the things was always, you know, the state space models don’t scale as well when you do a conversion or whatever the performance.
And you guys are like, no, just keep draining. And Nitron shows a lot of that. Yeah.
Nader: Also, something cool about Nitron it was released in layers, if you will, very similar to Dynamo. It’s, it’s, it’s essentially it was released as you can, the pre-training, post-training data sets are released. Yeah. The recipes on how to do it are released.
The model itself is released. It’s full model. You just benefit from us turning on the GPUs. But there are companies like, uh, ServiceNow took the dataset and they trained their own model and we were super excited and like, you know, celebrated that work.
Zoom
Vibhu: different. Zoom is, zoom is CGI, I think, uh, you know, also just to add like a lot of models don’t put out based models and if there’s that, why is fine tuning not taken off?
You know, you can do your own training. Yeah,
Kyle: sure.
Vibhu: You guys put out based model, I think you put out everything.
Nader: I believe I know [00:38:00]
swyx: about base. Basically
Vibhu: without base
swyx: basic can be cancelable.
Vibhu: Yeah. Base can be cancelable.
swyx: Yeah.
Vibhu: Safety training.
swyx: Did we get a full picture of dymo? I, I don’t know if we, what,
Nader: what I’d love is you, you mentioned the three axes like break it down of like, you know, what’s prefilled decode and like what are the optimizations that we can get with Dynamo?
Kyle: Yeah. That, that’s, that’s, that’s a great point. So to summarize on that three axis problem, right, there are three things that determine whether or not something can be done with inference, cost, quality, latency, right? Dynamo is supposed to be there to provide you like the runtime that allows you to pull levers to, you know, mix it up and move around the parade of frontier or the preto surface that determines is this actually possible with inference And AI today
Nader: gives you the knobs.
Kyle: Yeah, exactly. It gives you the knobs.
Disaggregation Prefill vs Decode
Kyle: Uh, and one thing that like we, we use a lot in contemporary inference and is, you know, starting to like pick up from, you know, in, in general knowledge is this co concept of disaggregation. So historically. Models would be hosted with a single inference engine. And that inference engine [00:39:00] would ping pong between two phases.
There’s prefill where you’re reading the sequence generating KV cache, which is basically just a set of vectors that represent the sequence. And then using that KV cache to generate new tokens, which is called Decode. And some brilliant researchers across multiple different papers essentially made the realization that if you separate these two phases, you actually gain some benefits.
Those benefits are basically a you don’t have to worry about step synchronous scheduling. So the way that an inference engine works is you do one step and then you finish it, and then you schedule, you start scheduling the next step there. It’s not like fully asynchronous. And the problem with that is you would have, uh, essentially pre-fill and decode are, are actually very different in terms of both their resource requirements and their sometimes their runtime.
So you would have like prefill that would like block decode steps because you, you’d still be pre-filing and you couldn’t schedule because you know the step has to end. So you remove that scheduling issue and then you also allow you, or you yourself, to like [00:40:00] split the work into two different ki types of pools.
So pre-fill typically, and, and this changes as, as model architecture changes. Pre-fill is, right now, compute bound most of the time with the sequence is sufficiently long. It’s compute bound. On the decode side because you’re doing a full Passover, all the weights and the entire sequence, every time you do a decode step and you’re, you don’t have the quadratic computation of KV cache, it’s usually memory bound because you’re retrieving a linear amount of memory and you’re doing a linear amount of compute as opposed to prefill where you retrieve a linear amount of memory and then use a quadratic.
You know,
Nader: it’s funny, someone exo Labs did a really cool demo where for the DGX Spark, which has a lot more compute, you can do the pre the compute hungry prefill on a DG X spark and then do the decode on a, on a Mac. Yeah. And so
Vibhu: that’s faster.
Nader: Yeah. Yeah.
Kyle: So you could, you can do that. You can do machine strat stratification.
Nader: Yeah.
Kyle: And like with our future generation generations of hardware, we actually announced, like with Reuben, this [00:41:00] new accelerator that is prefilled specific. It’s called Reuben, CPX. So
Kubernetes Scaling with Grove
Nader: I have a question when you do the scale out. Yeah. Is scaling out easier with Dynamo? Because when you need a new node, you can dedicate it to either the Prefill or, uh, decode.
Kyle: Yeah. So Dynamo actually has like a, a Kubernetes component in it called Grove that allows you to, to do this like crazy scaling specialization. It has like this hot, it’s a representation that, I don’t wanna go too deep into Kubernetes here, but there was a previous way that you would like launch multi-node work.
Uh, it’s called Leader Worker Set. It’s in the Kubernetes standard, and Leader worker set is great. It served a lot of people super well for a long period of time. But one of the things that it’s struggles with is representing a set of cases where you have a multi-node replica that has a pair, right?
You know, prefill and decode, or it’s not paired, but it has like a second stage that has a ratio that changes over time. And prefill and decode are like two different things as your workload changes, right? The amount of prefill you’ll need to do may change. [00:42:00] The amount of decode that you, you’ll need to do might change, right?
Like, let’s say you start getting like insanely long queries, right? That probably means that your prefill scales like harder because you’re hitting these, this quadratic scaling growth.
swyx: Yeah.
And then for listeners, like prefill will be long input. Decode would be long output, for example, right?
Kyle: Yeah. So like decode, decode scale. I mean, decode is funny because the amount of tokens that you produce scales with the output length, but the amount of work that you do per step scales with the amount of tokens in the context.
swyx: Yes.
Kyle: So both scales with the input and the output.
swyx: That’s true.
Kyle: But on the pre-fold view code side, like if.
Suddenly, like the amount of work you’re doing on the decode side stays about the same or like scales a little bit, and then the prefilled side like jumps up a lot. You actually don’t want that ratio to be the same. You want it to change over time. So Dynamo has a set of components that A, tell you how to scale.
It tells you how many prefilled workers and decoded workers you, it thinks you should have, and also provides a scheduling API for Kubernetes that allows you to actually represent and affect this scheduling on, on, on your actual [00:43:00] hardware, on your compute infrastructure.
Nader: Not gonna lie. I feel a little embarrassed for being proud of my SVG function earlier.
swyx: No, it
Nader: was
really
Kyle: cute. I, I
swyx: like
Nader: it’s all,
swyx: it’s all engineering. It’s all engineering. Um, that’s where I’m
Kyle: technical.
swyx: One thing I’m, I’m kind of just curious about with all with you see at a systems level, everything going on here. Mm-hmm. And we, you know, we’re scaling it up in, in multi, in distributed systems.
Context Length and Co Design
swyx: Um, I think one thing that’s like kind of, of the moment right now is people are asking, is there any SOL sort of upper bounds. In terms of like, let’s call, just call it context length for one for of a better word, but you can break it down however you like.
Nader: Yeah.
swyx: I just think like, well, yeah, I mean, like clearly you can engage in hybrid architectures and throw in some state space models in there.
All, all you want, but it looks, still looks very attention heavy.
Kyle: Yes. Uh, yeah. Long context is attention heavy. I mean, we have these hybrid models, um,
swyx: to take and most, most models like cap out at a million contexts and that’s it. Yeah. Like for the last two years has been it.
Kyle: Yeah. The model hardware context co-design thing that we’re seeing these days is actually super [00:44:00] interesting.
It’s like my, my passion, like my secret side passion. We see models like Kimmy or G-P-T-O-S-S. I’m use these because I, I know specific things about these models. So Kimmy two comes out, right? And it’s an interesting model. It’s like, like a deep seek style architecture is MLA. It’s basically deep seek, scaled like a little bit differently, um, and obviously trained differently as well.
But they, they talked about, why they made the design choices for context. Kimmy has more experts, but fewer attention heads, and I believe a slightly smaller attention, uh, like dimension. But I need to remember, I need to check that. Uh, it doesn’t matter. But they discussed this actually at length in a blog post on ji, which is like our pu which is like credit pu
swyx: Yeah.
Kyle: Um, in, in China. Chinese red.
swyx: Yeah.
Kyle: It’s, yeah. So it, it’s, it’s actually an incredible blog post. Uh, like all the mls people in, in, in that, I’ve seen that on GPU are like very brilliant, but they, they talk about like the creators of Kimi K two [00:45:00] actually like, talked about it on, on, on there in the blog post.
And they say, we, we actually did an experiment, right? Attention scales with the number of heads, obviously. Like if you have 64 heads versus 32 heads, you do half the work of attention. You still scale quadratic, but you do half the work. And they made a, a very specific like. Sort of barter in their system, in their architecture, they basically said, Hey, what if we gave it more experts, so we’re gonna use more memory capacity.
But we keep the amount of activated experts the same. We increase the expert sparsity, so we have fewer experts act. The ratio to of experts activated to number of experts is smaller, and we decrease the number of attention heads.
Vibhu: And kind of for context, what the, what we had been seeing was you make models sparser instead.
So no one was really touching heads. You’re just having, uh,
Kyle: well, they, they did, they implicitly made it sparser.
Vibhu: Yeah, yeah. For, for Kimmy. They did,
Kyle: yes.
Vibhu: They also made it sparser. But basically what we were seeing was people were at the level of, okay, there’s a sparsity ratio. You want more total parameters, less active, and that’s sparsity.[00:46:00]
But what you see from papers, like, the labs like moonshot deep seek, they go to the level of, okay, outside of just number of experts, you can also change how many attention heads and less attention layers. More attention. Layers. Layers, yeah. Yes, yes. So, and that’s all basically coming back to, just tied together is like hardware model, co-design, which is
Kyle: hardware model, co model, context, co-design.
Vibhu: Yeah.
Kyle: Right. Like if you were training a, a model that was like. Really, really short context, uh, or like really is good at super short context tasks. You may like design it in a way such that like you don’t care about attention scaling because it hasn’t hit that, like the turning point where like the quadratic curve takes over.
Nader: How do you consider attention or context as a separate part of the co-design? Like I would imagine hardware or just how I would’ve thought of it is like hardware model. Co-design would be hardware model context co-design
Kyle: because the harness and the context that is produced by the harness is a part of the model.
Once it’s trained in,
Vibhu: like even though towards the end you’ll do long context, you’re not changing architecture through I see. Training. Yeah.
Kyle: I mean you can try.
swyx: You’re saying [00:47:00] everyone’s training the harness into the model.
Kyle: I would say to some degree, or
swyx: there’s co-design for harness. I know there’s a small amount, but I feel like not everyone has like gone full send on this.
Kyle: I think, I think I think it’s important to internalize the harness that you think the model will be running. Running into the model.
swyx: Yeah. Interesting. Okay. Bash is like the universal harness,
Kyle: right? Like I’ll, I’ll give. An example here, right? I mean, or just like a, like a, it’s easy proof, right? If you can train against a harness and you’re using that harness for everything, wouldn’t you just train with the harness to ensure that you get the best possible quality out of,
swyx: Well, the, uh, I, I can provide a counter argument.
Yeah, sure. Which is what you wanna provide a generally useful model for other people to plug into their harnesses, right? So if you
Kyle: Yeah. Harnesses can be open, open source, right?
swyx: Yeah. So I mean, that’s, that’s effectively what’s happening with Codex.
Kyle: Yeah.
swyx: And, but like you may want like a different search tool and then you may have to name it differently or,
Nader: I don’t know how much people have pushed on this, but can you.
Train a model, would it be, have you have people compared training a model for the for the harness versus [00:48:00] like post training for
swyx: I think it’s the same thing. It’s the same thing. It’s okay. Just extra post training. I
Nader: see.
swyx: And so, I mean, cognition does this course, it does this where you, you just have to like, if your tool is slightly different, um, either force your tool to be like the tool that they train for.
Hmm. Or undo their training for their tool and then Oh, that’s re retrain. Yeah. It’s, it’s really annoying and like,
Kyle: I would hope that eventually we hit like a certain level of generality with respect to training new
swyx: tools. This is not a GI like, it’s, this is a really stupid like. Learn my tool b***h.
Like, I don’t know if, I don’t know if I can say that, but like, you know, um, I think what my point kind of is, is that there’s, like, I look at slopes of the scaling laws and like, this slope is not working, man. We, we are at a million token context, okay, maybe next year, 2 million, we’re not going to a hundred trillion, you know, like this, this, oh, there’s so many interesting ways to get this Doesn’t work.
Just doesn’t work.
Nader: What’s kind of funny is whenever there, I, I feel like we always want to see a trend that we can predict, but every time something’s come, it’s been like a leapfrog. So I, I imagine I, I don’t know how we go from one to two, but I imagine what, what’s likely to happen is [00:49:00] we break through that from some new
Kyle: Yeah.
There’s actually, there’s an interesting formalization of this. There, there’s an essay. It’s a pretty interesting essay by Leopold Ashton Brener called Situational Awareness.
swyx: Okay? Yes.
Kyle: He introduces a concept awareness called an un hobbler, right? So he, you know, Leopold in this essay details, Hey, I want to get.
You know, like, I wanna get to this point in intelligence and I think that it is four orders of magnitude worth of like compute and data and training away. And you know, he says, oh yeah, I think data centers can scale up by about this much. I think that you can do, scale up the data and some other things by this much.
But one of the things that like makes the rest of that order of magnitude growth, PO possibilities is un hobbler, like these scientific discoveries that are discovered during. You know, model architecture, search or training that really, really, really impact how, how you are able to scale. Like a, a good example of this might be that like we see like a mo a lot of models that are, [00:50:00] and this is probably a very tiny on hobbler.
But is important for the performance perspective. We see a lot of models that are like trained with multi token prediction natively in during pre-training.
And per deep seek in their paper they say, Hey, decided this actually helped us in ensure sta more stable convergence. But they’re like, un Hobbs that are like that.
And then they’re like, rather large on hobbler. Right. Like architecturally, a lot of our models, like we had different types of attention. And one of the problems with attention is like, you have a lot of kv, but people found like different forms of attention, like group query attention and, uh, like MLA in deep seek multi-head latent attention that like decrease the burden that KV has on the model, which allows you to grow like longer in context.
swyx: Yeah. And that, that was very drastic for deeps seek.
Kyle: Yeah. This was like, yeah, it for context like the, the total, I think the total context length of deeps seek is 128,000 tokens or might be 256,000 with rope extension. That entire context, I think it’s 128,000 fits into eight gigabytes. Previously context, like I think the, the llama four or five B context [00:51:00] of a similar size was like 40 or 80 gigabytes in the same precision.
swyx: Yeah.
Kyle: Um, so like those in Hobbler like really decrease the stuff of that size. And I wouldn’t be surprised if we do see the ability to like, break through to like 10 million, 20 million, a hundred million context through the an un hobbler showing up. I
swyx: see.
Kyle: And it’s just science.
swyx: So more deep learning algorithms is what
Kyle: I’m hearing.
Yeah. More deep learning algorithms. Um,
swyx: yeah,
Kyle: I, I could, I could actually playing pickup
swyx: and he has
Kyle: room to, I I could actually give you an, an example like of like a, a theory, not a theory theory, but something theoretical and a hobar
Nader: that you’re excited about or,
Kyle: well, and, and a hobar that, I mean, I haven’t seen, so it could be a tar pit and it could not, just, not work.
But, uh, I, I would be really excited to see a model that does prefill and decode differently. So a model that does, uh, prefill like locally, like document wise, prefill, like it doesn’t in chunks, and then you do decode globally across like the entire sequence because it, logically to me it doesn’t seem like you would necessarily need to [00:52:00] have KV b associative between documents that have like, no, no mutual association.
But that like places a lot of burden on prefilled to like, or sorry, on, on decode and pure attention within the decode phase to like make those connections since the KV is like static at that point. And you see other techniques that are interesting like this too. But if, if you’re able to do that, like.
If Prefill becomes local and decode is, is still global, you solve that prefilled quadratic scaling problem because you have a bunch of like small chunks that you prefill independently.
swyx: Okay. All right. Well, let’s, uh, wait and see, but I, I think it’ll be pretty exciting.
Kyle: Fingers crossed.
swyx: Yeah, fingers crossed.
Yeah. Yeah.
Vibhu: I’m excited for prefilled decode on separate hardware. So like yeah. CR acquisition, right. Can we decode on the gr Can we get super fast?
Kyle: I don’t think I’m allowed to comment on this.
swyx: Mark is gonna shoot arrows at us.
Nader: Uh, he’s got a blow dark, he’s in the room, just
Kyle: like,
Nader: like go to sleep.
Yeah. Yeah.
swyx: But
Nader: I’m, I’m super excited to see the team come in and like, you know, I’ve gotten the, the pleasure of working with some of the, the GR people coming in. So, you know, yeah, I,
swyx: I know Sonny, [00:53:00] we’ve had him, uh, at the same
Kyle: conference that
swyx: you are at.
Nader: Yeah.
swyx: Um, and, uh, I, I think you’re, you guys are gonna be doing some sessions at G tc.
I don’t know if you wanna, this is a good place to plug them.
Kyle: Yeah, yeah, yeah. So, I can’t speak to any LPU related sessions at G tc. I have no idea about that. Oh, no, that was,
swyx: no. Yours
Kyle: on the, on the GR side. Yeah. I use the associative NVIDIA U Yeah. Um, on the, on the Nvidia Dynamo side, we’re, we’re giving, there are a large number of sessions.
For those that aren’t aware, you can actually search. All of these sessions for GTC online, just go to the GTC website. I don’t know what the URL is, but go there. Google it. Yeah. Uh, and you can just look up Dynamo and you’ll get all the sessions. There’re about 20. There are a couple that are hosted by the Dynamo team.
There are a couple that are hosted by people that use Dynamo that wanna show off the results they’ve been able to get. But there are two that I’m really excited about. Uh, one is just the General Dynamo tutorial, and this is the, I’m going out with Harry, who’s our lead product manager for Dynamo.
And we’re sort of talking about like how to use Dynamo to get better performance and also like where we see Dynamo going in the future. And [00:54:00] then there’s another session that I’m doing with one of our agents teams at Nvidia to talk about sort of the future of agents in production inference. Yeah. So we’re talking about, there’s like this new horizon with respect to agents because we have these harnesses that actually impart structure on upon calls.
Like if you, if you compare like, the past and the, and the present with respect to like how LM calls work. Like in the early days when they were chatbots, like every call was like very different. There was basically no structure. You could assume that like people, you, if it was conversational, there might be like some implicit structure because you have, you know, a multi-term conversation.
But agency have this, this harness that, like abides by rules, right? So it imparts direct structure onto the context. And you see this, there was an interesting Twitter post about how Claude code like structures, its context so that you get as many cts as possible.
And I think it was by one of the, the PMs for Claude code.
And he, he wrote about it. And that type of structure that the harness can impart actually like goes hand in [00:55:00] hand with the. Inference co-design. So I’m doing a talk, I, I don’t know the session name or the session number, but I’m, I’m doing a talk, uh, you can look at me up by name on, on the GTC website, on how we accelerate agents and where we see specific optimizations for agents going in Dynamo and in inference in general.
swyx: Yeah. I think there’s only 1:00 PM for cloud code and it’s wo the rest. There’s, there’s Devrel, there’s Boris. Maybe it was maybe Devrel. Yeah, exactly. I mean, let’s go into agents. I think this was like the last part of the, the, the discussion we planned. Yeah. How have we not talked about agents also with you guys?
Well, we scheduled, it was like, I was like, okay, you know, like, let’s have like cohesive sections or,
Vibhu: I mean, there’s the big news, right? The NVIDIA’s a huge. Like deployment of Codex. Yeah, video
swyx: uses everything. I mean, we use this cursor and we uses code,
Vibhu: but that’s, that’s a pretty big deployment, right?
Like, that’s tens of thousands of people.
Nader: Totally. Yeah.
Vibhu: We’re super What? That’s,
Nader: yeah. I, it goes back to the mosh pit of emails we kind of mentioned earlier, or just the like, um, how fluid the org feels. So when there’s new technology, people will just email it out and everyone will try it.
[00:56:00] And if it, if it’s making people’s lives easier, it’ll spread like wildfire.
Kyle: A lot of times Jensen will get it and it’ll be like, let’s make this work. Yeah. Across the company. Let’s make this work right now,
Nader: honestly, uh, if I was a startup, I feel like a cool hack. If you have something that’s going to save an Nvidia time they’ll spread it to a couple and the same thing.
Right? It’ll just spread like wildfire. Okay.
Vibhu: Careful before your email blows up from startups. Well,
Nader: You gotta know the person. Right? But no, I, um, I, yeah, so I mean, we, I love using Codex. It’s been a ton of fun. Yeah. Uh, I’ve been using it personally. I’ve been using it at work. It’s been, um.
Yeah, I dunno. It’s been great to see the rollout, something really funny. Uh, on the data we got, uh, codex and cloud code access. I found this person, uh, his name’s Carlos at the company. He wrote an Outlook, CLI.
Kyle: Oh yeah.
Nader: And, uh, just the CLI for email. And this was, I’ve
Kyle: been using that,
Nader: yeah, maybe like four or five weeks ago.
And, uh, the site, so once I got like Codex access I. Installed the CLI, it had a skill and I just asked it to go through all of my emails, which it’s very messy. So if I don’t respond to your email, I’m really sorry. But I asked it to gimme a summary, highlight any [00:57:00] escalations that I should look at, put any thread that it thinks I should respond to in a folder, and then archive everything.
And it did. So if I missed your email, it’s because it didn’t get,
swyx: so I should put a prompt injection in my V to Yeah, yeah. What you should do is just FaceTime. Yeah. Um, my, yeah, my SLA is highest on FaceTime,
Nader: but that was, it was magic. And so I, I sent it in a big email thread to like 500 people. A bunch of folks tried it out.
I started like FaceTiming whoever I could at the company to get them set up with this.
swyx: Yeah. Um, that specific example mm-hmm. You guys deal with like some pretty. Sensitive emails.
Nader: Yeah.
swyx: Is there a security review with this?
Security Meets Agents
swyx: ‘cause like one guy made, made it for himself, but like it’s not meant for all the
Nader: security team and Nvidia is incredible.
Like, shout out to them. They’re, they’re, they’re trying to, we have a, we have an amazing security team ‘cause they’re progressive and they know that this is
Kyle: really important technology and you have to bring it in. If you think about like, if you work at a big company, your laptop’s usually very locked down if
Nader: you can only access certain things.
Nvidia engineers have those restrictions aren’t there. So you’re expected to understand the risks when you try things out. And so. Very quickly, you know, made sure to [00:58:00] chime in security on what we were doing.
Agent Permissions Model
Nader: There’s actually a lot that we’ve been thinking about, especially with open claw, right? Like there’s, you know, agents can do three things.
Yeah. A agents can do three things. They can access your files, they can access the internet, and then now they can write custom code, uh, and execute it. And you literally only let an agent do two of those three things. If you can access your files and you can write custom code, you don’t want internet access because that’s one to see full vulnerability, right?
If you have access to internet and your file system, you should know the full scope of what that agent’s capable of doing. Otherwise, malware can get injected or something that can happen. And so that’s a lot of what we’ve been thinking about is like, you know, how do we both enable this because it’s clearly the future.
But then also, you know, what, what are these enforcement points that we can start to like protect?
swyx: And is there any directive of like, Hey, we have a company account or a company agreement with open ai, we use open AI models here, or like choose whatever.
Nader: No, no. So, so I would never put any company data in a model that’s not either, that we don’t even, it has to most security.
Yeah. Yeah. I like how,
swyx: how that goes. Uh, you know, obviously you could run your own [00:59:00] models. You Nemo and, and we, right, we, we as an, we have an internal cluster, so, you know, of course in random,
Kyle: uh, yeah.
swyx: Yeah.
Nader: I think we’re dynamo’s first customers. Let’s go
Build Nvidia Inference Gateway
Kyle: actually, uh, there’s a funny story about like how I got the experience that informed what we needed for Dynamo at one point.
There’s a website called build done n video.com and also for us infra dun n video com. That is allows people to try models. It gives an a p service. You can call the model with like a rest, API, and you know, you get a response. I ran the model side for that and it was at one point the largest inference deployment and still may actually be the largest inference deployment in video.
I’ve, I’ve since like, handed it off to some people and they’re doing a wonderful by way. This is a extremely
Nader: underknown or less known resource. Vil diamond v.com. You can get any of these open source models. And it’s rate limited, but it’s free. So it’s perfect for hackers to,
Kyle: and, and the SLA on getting models day zero models up is like a day.
Yeah.
Kyle: Like they’re, they’re incredibly good at like figuring out the right way to host the model to [01:00:00] get it up there as soon as it comes out.
swyx: You ran this?
Kyle: Yeah, I ran, I ran it a long time ago. It was originally called Nvidia AI Playground, then it was called AI Foundational insert. Yeah. And then it was called Build Nvidia call.
And I, I ran the model side of it. So there were, there was a large multi-organizational team. I ran how, which models should we host? How should we host them and like what’s the proportion of them? And then of course there was like an SRE team that like made sure that things ran well and scaled the models as well.
But I ran like, you know, model, how do we get the model to silicon? And then, which model also worked with our product team Determine like which models were important a very long time ago.
Yeah. Yeah. There’s also like a middle ground in between there, right? This is like for the hacker. Try anything.
There’s the Brev console, then there’s Dynamo, there was also nims, right?
Kyle: Yes.
I remember it had its little moment, like a year or two ago. Is it still?
Nader: Yeah. NIM is, uh, you know, inference, uh, oil. I, I think it like for something is it is a log or acronym. Yeah. It [01:01:00] just, just a name. But, um, yeah, NIM is, uh, how enterprises can take our uh, any of the, any of this technology and run it with support and all of that.
And so that includes Daniel Mo. That includes, I don’t know all of our other optimizations that are packers up for Enterprise. Yep.
swyx: Anyway, so, so you, you got a bunch of experience start running the sort of internal inference gateway playgrounds.
Kyle: Yeah, I got And Bill also built how build NVIDIA’s first internal like vs.
Code thing. We call it MB code.
swyx: That’s what I, uh, extension.
Kyle: Yeah, it was, it was a V first,
like the fork vs code.
swyx: We jokes absolutely not. It just a while back they like, we should have a fourth vs. Code hackathon where you, that’s four. It’s the best four V vs code. We,
we were, we were doing a hack how make a billion dollars, someone from VS code was there and he was like somewhat down to get involved and I was like,
swyx: oh, you should do that.
That’s all. Then the cool thing became four chrome hackathon
Chrome,
swyx: And no, no, no IDs or not cooling.
Nader: I saw, what’s it called?
Hackathons And Autonomy Dreams
Nader: I was talking to Joseph, uh, from Robo Flow and uh, they’re partnering crime. We were talking about how with the new Alpha Mayo model, so Nvidia just [01:02:00] released an open source. Uh, the, the Mercedes cars that you saw drag, she on Frazey?
swyx: Yeah.
Nader: Released. Will you open source, a autonomous driving model? Uh, I already, yeah, so we were thinking like, could we hackathon a driverless car? Like I have my old car. Let’s just try it.
swyx: We’ll take it,
Nader: take it to like, click train with a treasure eye, like in the middle of the day. Just like, just see, let everyone, like how many, how many cameras do we need?
Right? Like, 1, 2,
swyx: 3, 4. They don’t. Five, six.
Nader: I don’t know. I, yeah. But, um, I think we’re gonna try, you just do it with us.
swyx: We can see, we could even
Nader: have a race. It’s like the first person to automate their
swyx: driving. Let me over a weekend. We do have an autonomy track at Will’s fair. Uh, WiMo was there like Yeah.
Nvidia did send people that for Goot. Not because he didn’t have the driving thing yet.
Nader: Yeah.
swyx: Yeah. It’s, that’s cool.
Yeah. I think comma, comma also has a version of this comma have open source driving. They’ve, they’ve done a fun hackathon on
swyx: music and he and I also, ‘cause I, I really, what I really want is a Tesla with Tesla level self-driving.
Yeah.
swyx: But as a smart car, like a two seater. That’s the basic CPA wheelchair with a [01:03:00] roof
and only thing they make them, but the demand has d they, no, they realize this probably five years. Yeah. Really?
swyx: Yeah.
They were d manufacturer.
Kyle: I thought it is one of those things, we’ll, where we’ll see someone buy the brand and it’ll be revived.
swyx: I, I would buy it like I
Kyle: probably. Someone hears this go by
swyx: your car. Yeah. Yeah. That’s crazy. Nobody Mercedes, because they, they’re like, I think 10 Mercedes, Mercedes, uh, I in Mercedes used
to make them, I don’t know. I feel like they own the brand and you out
swyx: that’s your dream might come true enough. Okay.
We we’re time notify and, and I was like, every time I, I try to park in San Francisco, I I have to buy a smart car because like 20% of the parking lots in San Francisco only fit smart cars.
Nader: Yeah. So, Hey, really?
swyx: That’s where, I mean, it’s mall
Nader: even it was late here trying to, this comes from someone that like, basically does
Kyle: not drive.
Nader: That’s where the, the Vepa was a life hack. Yeah, exactly. Yeah. You know what happened to the Vespa? Um, I used to have [01:04:00] this yellow Vespa, uh, I left it outside the hacker house when we moved out. It trend. Um, it’s just, it was always there. And then like a month ago. It’s not there anymore. I’ve been meeting today.
I don’t dunno. You could, it’s actually tv. You forgot about it.
swyx: Yeah.
Nader: And left.
swyx: Yeah. Yeah. No, this, it’s probably hazard. And speaking of hackathons, I also wanted say, give a big shout out to the world. Shortest hackathon. Let’s go. Uh, you did twice. You gonna watch a
Nader: handful of times? Yeah. There’s gonna be one at G tc.
Oh, we’re doing pretty much we have a bunch of challenges that No, we haven’t released. And you get to bring your agent to come and attempt to, uh, go through those
Kyle: challeng again. It’s like a zero, the zero minute hackathon idea, which you just, you just bring your, I I approached eight, nine along a long time ago.
You just bring your agent and then you press the go button. You’re not allowed to code. It’s just the Asian doing bond.
It’s a good hidden email, right?
Kyle: Yeah.
Do you make a jar? You make
Kyle: I there something I would love to see from cognition or someone else be like, come bring your agent. Drop it in
because you don’t, you don’t know you like supervisor.
Well let be [01:05:00] a, you know, operate a browser, order a pizza. We’ll just see like that snake it, you know,
swyx: and
Kyle: you don’t know what the
swyx: task
Kyle: is. Yeah. You dunno what the task is like, or just like, you don’t even know what the judging categories are and then you give it the judging categories. Like, try as much as possible.
It’s great though. It turns into like, yeah, so let’s build something on dining party. It’s a great business. See,
Kyle: anyway, funny story.
Agent UX And CLI Everywhere
Kyle: Actually, we have a couple of people at Nvidia, we’ve been working with security to like bring agents really close to compute. So we now have like stuff where we can like tell Dynamo, like go run some experience with Dynamo, like on, X cluster and just like try it right now, like queue up once you get queued, like, send this request load and we’ve actually been able to like, just like, you know, like one shot problems like.
We used to have this problem where you know, with Dynamo you have to like find the right configurations and we, sort of do it automatically for some parts of it, but you have to like a good initial configuration that you want to use. And we’ve just had like an agent just completely one shot that it goes, it gets the compute, it like runs a couple experiments.
It’s like [01:06:00] this is the best, this is this, these are part of the ER frontier. Go run this. And then we just like give that to people and it’s like faster than anything that they have.
Nader: Agent UX and agent marketing are super important. There’s stuff that we’ve been thinking a lot about. Um, Alec is like redoing the entire Brev CLI, um, so that you can fetch all the different compute types that are available.
I don’t know, it’s gonna be really soon, but then you can, you can just browse what GPUs are available and then provision one say to it right there. And you can pipe all the commands. But I think it goes back to like the Alex CLI, like if you, coding agents. It’s kind of funny. I feel like coding agents have been so much more effective than general purpose agents.
And I think a large part of that is it just has access to the terminal, like you said, and that means it has access to everything that you’ve installed into your terminal. It can run. So, you know, it would write code and, and it can compile the code and if there are errors, it can fix it, it can run your suite of tests because that’s all just in your terminal.
And so that, you know, then for the idea, what come me really excited about the CLI, we’re now just turning through building CLI for the entire, like for the entire business. We Slack, building Slack, also. Workday, C-L-I-S-A Go. I, I’ve also done that for myself first. Really? Yeah. Yeah. Um, we’re gonna, we’re gonna [01:07:00] open source all of this.
And like yeah, all the, the I they’re just they’re the C yeah. CLI for the business applications. We would love for someone to run with this and like build like, I don’t know, like open CLI foundation in or something. Yeah. We, I Nvidia would love to support, uh, anyone that’s doing this.
Like e every Devrel tool should really have good CLI support at this point.
Yeah. Like at one point it was, you want your docs to be. Like accessible by an LM, right? You want LM Good dog. No, every, everything needs some CLI.
Nader: Yeah. It’s kind of funny, right? Like we, like computing began with a terminal with a shell, but we said that it’s not empathetic to, uh, humans. So we built these nice user interfaces and then now we have LMS navigating our user interfaces.
And ironically, we’re not empathetic to the machine anymore.
swyx: Yeah.
Nader: Yeah. Just give the, the LLM access to the show.
swyx: One thing that slightly makes me uncomfortable is like, why do we have to build cli? Why can’t we just expose APIs? Like,
Kyle: I, I have, I have an interesting answer to this. So there are a couple reasons.
Like there’s, there’s like, you know, portability is like one issue. Like, you know, like sometimes APIs are not like discoverable or like reachable by, by some, you know, types of [01:08:00] things. There’s some element of locality, right? Like, uh, like the CLI is like literally you interfacing with your like local system, which is a little bit different.
You could still do it by API, but like there’s this highlighting of like, what is the difference between like a CLI and an MCP, right? Like they kind of occupy the same purposes and you call them, it does something on the system and, and that’s done. I think that in pre-training there’s just an enormous amount.
Oh, okay. Command line data. Yeah.
Yeah. Like e even let’s ignore our, let’s let’s ignore our l Like you’re doing no harness, you’re doing no harness push training. Just the amount of like CLI versus API documentation for just like navigating this world of the CLI in your file system through that is just enormous.
Nader: Yeah. Yeah.
Kyle: Right. I
Nader: think there’s a, there’s a couple of things too. Like if, let’s say we wanna, so one I think your intuition’s, right? The CLI is just wrapping the API,
swyx: right? So functional
Nader: functionally, right? Yeah. And I think it’s nice because one, you’re, you’re being very, uh, specific and pedantic even, um, of what and that’s really good ‘cause you’re describing the problem space.
So you know what the, I don’t [01:09:00] know. I don’t wanna call it like what the, the space for vulnerability. You know what network calls you’re making, it’s not arbitrary and that’s not decided on the fly. That’s like pre-decided, which is important from a security perspective. But then if you were to write a bunch of API requests, you would probably do that.
I don’t know. Would the model like use Python to do so? I kind of like that. Everything like a CLI is just dash because it’s ubiquitous. Like it’s just there. And you don’t have to make sure that there’s certain environment variables that are set up. Like if your Python versions, if the My Python version we’re using the same model to go do the same thing, is it gonna write like different code?
It probably would. And so it’s kind of like an nice deal work, right? Yeah. Human. Yeah. No, I think just like making those decisions happen ahead of time versus yeah.
swyx: One last thing on this sort of agent, I guess maybe co-location or whatever you call it, uh, one pattern on tracking for this year, I always try to think about what’s the theme of this year gonna be last year?
Definitely coding agents this year is definitely coding agents, breaking out of containment into broadening third world. I go Definitely has. So
Vibhu: you rent a human?
swyx: Yeah. Yeah.
I’m on here.
swyx: Are you really? [01:10:00]
I’m like $5,000. I’ll do anything. Really? I think so. I need, uh,
swyx: my, uh, my borrow from Costco.
Uh, but I think the best part is only the agent can book me, you know?
Yeah.
swyx: It’s very
Kyle: usually like,
swyx: it’s just like another labor marketplace at Mechanical Turk was this.
So definitely I have a weird story with why I did it. So back to your example of just giving agent access to compute, right? Yeah. You guys are GPU Rich at Nvidia. Yeah, I hooked up.
Nader: He’s not shy about it.
Local GPUs And Scaling Inference
I have, I have a 24 7 agent running, I hooked up to run pot.
It doesn’t shut down instances. And I’m like, I’ve tried prompting you, I’ve given the instruction. Shut down when you’re done. It’s like I to keep it warm, I’ll need it soon. And it’s horrible on time estimates too, ‘cause like they realize it’s like. Yeah, I’ll need it in 45 minutes. 45 minutes, I’ll shut it down.
45 minutes of human time is actually three minute of agent time, so it’s like I’m booting it up, I’m waiting, I’ll just leave it on all night. And mo moo’s good at shutting down after something activity. I had it on my local server, like a little dual GPU thing. It just stays on. I have a little space heater at home now, but careful.
[01:11:00] So basically, you know, they don’t care about the concept of money just burn it. I need it. It’s useful.
Nader: And another DGX spark will be really nice. Like, I, I think I’m looking at it as super useful for agents because Yeah, you buy it once you plug it in and they it can rip. I’m gonna make a, I’m gonna make an Nvidia ad here.
Kyle: Okay. The Blackwell, like RTX 6,000 cards. Pro Pro only, like, I think it’s $8,000. Slightly cheaper. Yeah. Well, it’s much, it’s much cheaper than the data center cards.
Vibhu: Yeah.
Kyle: And it’s got 96 gigabytes of u gram. So if you and your, your crew want to go, like, run a local agent for you, you know, you, you in the home.
I feel like, hmm. It’s got a significant amount of vra m I’ve thought about purchasing this and running in my basement, except my neighbors would hate me.
It’s just a single, like two, three slot. GPU. It’s mostly,
Kyle: yeah, it’s A-V-C-I-E.
Yeah, it’s
Kyle: UCI u. So GPU, you can go by that. I mean, the big difference against like the RTX, like gaming, GPUs, it, I mean, obviously it’s like blackball Pro, like it’s a pro GPU and it has a [01:12:00] lot of E round, which means you can run pretty large models on it.
You can stack four of them for the Maxim Q in a system that’s a beast.
Kyle: It’s beefy. You can run, uh, what is that, 96 ger or anything? 96, uh, you’re on a loge.
Uh, but also they, they are slow. They’re not, I mean, performance of speed will be somewhat slower compared to API like,
Kyle: oh yeah, that, that’s true. So again, the big learning economy of scale allows you to do things that allow you to get both speed and throughput.
Like you can run. I’ll give you an example. There’s an optimization called Wide ep. I’m not gonna go into it fully, but like it featured heavily in, in inference Maxim for Deep seek. And there’s a, there’s a great set of stories from Nvidia and from semi analysis about like why y EP is important, but for like MOE models, it’s like basically essential and you run it like the A Level app parallelism, the level scale up parallelism used for it is like 32.
So it goes beyond that eight barrier. And it like really, really, really is important to have that M mbl, L [01:13:00] 72, GB 200 MD link to serve at scale. And like, it’s like, I don’t remember the, the, you know, cost improvement I think against Hopper, right? Against Hopper. With this MBL L 72 system, you’re getting like 35 times cheaper per token for like a lot of the curve.
Yeah. Which is crazy.
swyx: Yeah.
Kyle: And Normalize per GPU obviously because the part of the GP is cost or the code, the GST part of the cost.
swyx: One thing I’m exploring is the sort of, this year is also the year at the subagent, um, where you have the main agent, but then that also kicks off tools, which are in themselves, agents that have limiteds.
Yeah. And sort of context locally, whatever, right? Yeah. Different prompts. So for example, one thing that Ian does is before you kick off a search, they do like a fast context model where you kick off April or you just to search, uh, across the code base plus all that. That is better than indexing. A a lot of the times, not, not all the times, and, uh, you should sell index for some picks, but like the idea that agents should be able to command subagent and probably run [01:14:00] them like maybe close to inference as well.
I don’t know if that’s like architecturally possible or even
Kyle: Yeah, we’re, we’re thinking about that for dmo. That’s like our big theme for the year,
swyx: because like you, like if you can design that into your stuff, then a lot of people, a lot more people will use it. Right now it’s like just kind of theoretical because.
You do pay a lot of like back and forth, uh, coordination costs. Yes.
Vibhu: I think it’ll net speed up though, right? Like even at a basic level, speculative decoding, you’re running a small model, you’re running two instances, but it’s not,
swyx: that is one example. Yes.
Kyle: Yeah. But this is like a little bit like different with like agents.
Agents, yeah. This is not spec. I think, I think there’s like a summarization of that trend that I like to do or I like to say to my team, it’s like, this is the year. So there are two things. This is the year system as model, right? Where like instead of having like a single model be a thing, you have a system of models and components that are working together to like emulate the black box model.
So when you, when you make an API call to something that’s like, like a multi-agent in the background, it still looks like an API called a model. You’re still getting back to
swyx: grants, but under the hood.
Kyle: Yeah, under the hood. It’s like a [01:15:00] billion different models. And that’s a lot of complexity, with Dynamo and with other libraries and media we’re, we’re looking to help manage
Nader: that complaint.
Yeah. It’s funny because we actually, for CES, we just released the model router. Uh, for DGX Spark where you can have a local model that’s running on the spark and then also a foundational model and then the model router decides when to send queries to which one. So it’s no longer this like either or.
It’s used the best stuff for everything that’s available to you. You have a good post-training bottle that’s running on
swyx: these. There are leads that are also the bread functionality of being able to manage the spark.
Kyle: Oh, that’d be cool. Oh yeah,
swyx: I did be able feature request. There we go.
Long Running Agents And SF Reflections
Kyle: I actually like a question, like I, I like to like extend and flip over.
How much longer do you guys think like agents are gonna be running? Because that’s one thing I’ve been throwing around, like, what happens when, I
mean always are
Kyle: it
even affects the, like back to the prefilled d the decode, right? Like, yeah. Codex is, I’d say, compared to cloud code, it’s much longer at tasks like, yeah, that thing, we’ll, like to run 6, 7, 8 hours.
I’ll run it overnight.
Kyle: Yeah.
And I’ll, I’ll go back and I have like a little crappy logging software I use and there’s just times where it wants to, like, I’m gonna go deep on [01:16:00] research and it’ll, I eat up 80,000 tokens go on another go on another, yeah. Just eat through tokens and you know, that’s part of it.
Like, at the end it does, it does hit a long task. And I think you only see that, that expense. Yeah.
Nader: I, yeah, there’s insatiable demand for tokens and every improvement that comes kind of just makes our demand even higher. It’s kind of funny, right? Like if you have like a teammate and you ask me to do a task and they’re like, should I save some effort and not think too hard about this task?
I’m like, f**k no.
I mean, my favorite was like, you can, you can have four shots, right? Yeah. Like the original codex before the app. You, why do one call, like, give it four attempts? Just, just use all the token to out, right? Try Moreal try, try again. Try more. It’s
Kyle: like, it’s like the, the meta index right?
Is the thing that tracks like how long models are able to run. I expect that we’ll just see like log linear, if not log super linear growth. We will see before the end of the year an agent that is capable of running for longer than 24 hours with like self consistency the entire time.
I, I would also poke at different domains, having different [01:17:00] desires, right?
Like at a consumer level. I’m getting slightly frustrated at 20 minutes per basic query. Sure. You can optimize, you know, six, eight hour. I don’t see myself shooting off many one week agents. Right. Someone doing like, okay, GPU kernel research or medical or biological, like, you know, in, in those domains Sure.
Shoot off a lot. That take a, so like I think it will be somewhat domain specific ‘cause you also really need to turn that in. Right.
Kyle: It’s funny one, those was doing your taxes. Right. Like, that’s tax. Yeah, that’s, yeah. Okay. Yeah.
Nader: Get it right. I wonder if like this major school say sort of like, uh, speculative decoding is like your agent figuring out what you might be prompting it the next day at night and like pre fetching.
swyx: Yeah, you can do
that.
Nader: Yeah. Really? Branch, branch prediction.
swyx: Oh, well no, that, well, that’s, that’s too, that’s too low level, but yes. Sorry. Yeah, yeah, yeah. One question I gotta get, so like, uh, we actually did record a part with the, the beat folks. Uh, with Sarah right here, their chart is the human equivalent work, uh, hours of work rather than how long it has themselves are, are being [01:18:00] autonomous.
And that, that’s a huge difference, right? Like human work, five hours agent work, 30 minutes, like it’s actually 30 minutes not, uh, yeah. Firearms, right? Like, so like that, that, that chart that you see is them estimating what the human equivalent replacement is. Um, I think the, I think actually Enro release a more recent chart.
That showed cloud code autonomy from their production traffic numbers, and that was 20 to 45 minutes. That’s roughly where we are. So yeah. Yeah, that’s the sort of realistic thing. I mean, I, I do think like there’s experimental setups we can just like, Ralph with and like just prompt it to keep going, uh, when it stops.
And obviously you can, that can go arbitrarily long,
Nader: I feel like
from my
Nader: experience. Yeah. I guess 20 to 40 minutes seems right for when I’m using like Codex or cloud code. But then like what, I always try to just, like, if I wanna spin up like a new, there’s a net new project, I’ll, I’ll often start to rep it and like it’ll end for I believe, yeah, yeah.
Like spin up like the, their new, like from the V three agent. Like it’ll spin up a web browser and like click around and discover new bugs and just keep churning. Um, so I, I think like my longest was like over an hour that, hey, I’ve been churning
I think before [01:19:00] we see super long running. I think there’s gonna be a bit of an efficiency hit.
So. Sure you can take an hour and go down paths, but you also want you wanna be more efficient, you wanna be smarter in your reasoning, right? So I think that’ll actually go down before we go back up. Like, you don’t wanna scale non-optimized systems just for the heck of it. As much as I love saying, use all the tokens, um, you know, they are expensive.
Like going from dance to reasoning models, that’s an added cost, right? You’re paying for a lot of tokens and it doesn’t make sense to just scale stuff that’s not optimized. So there’s, there’s always that little balance.
Nader: Yeah.
But you know. I think you’ll see both sides of it.
Nader: Yeah. So 2023 was super exciting.
I think if you were in SF you were like, okay, uh, I know this is gonna be a huge world changing moment, but it seemed like, you know, no one had known yet. And maybe even before, was it 2022 maybe?
swyx: Yeah, yeah. I would say, yeah, like RU had this tweet where like everyone was in SF from like 2021 to 2023. Yeah.
Understood what it was like to be late, early.
Nader: Totally. Um, yeah, 2021, that’s when I made my first open AI account. Yeah, it went, um, it was crazy. [01:20:00] And I remember it was so funny ‘cause at the time SF had not been doing well. So pretty much what it felt like was the concentration of founders in the city had ro had risen because, um, where my neighbors were used to doing a bunch of stuff, those people had all left.
So the only people that were still in the city were people that really wanted to build It was cheap tech. It was, yeah. It was also way cheaper. I feel really bad anyone, uh, who is trying to get rent now, but there was, uh, cell was they had a huge office.
swyx: So blockchain in Yeah, like took over the, the old Casper building.
Nader: Yeah. They had the showroom and they had the, like the, what would, I think it was like the back warehouse. It was, and it was a huge office. And
swyx: it’s right across an opening Eyes in New Link.
Nader: Yeah. It was in
the original arena.
swyx: I named the Arena because of it.
Nader: Yeah. Yeah. And so it was really exciting because like vo flow I think uh, I forgot the Minify.
Yeah. Minify, uh, brev was there. You guys were there. I remember. That was actually, it was there that you bought the AI engineer domain.
swyx: Yeah. I didn’t know what I was gonna do in ai. I, I wanna do something,
Nader: but it was kind of this, it was a really fun moment where we were kind of all in this solo space and it, um, I don’t know.
It was, [01:21:00] it was a really cool community, especially being so
swyx: early. Yeah. And so it, then you got me early cruise access. Oh yeah. So there was a going period of time. They both cruises and Waymo’s were just free. Yeah, always.
If you had, I mean, they’re, they’re so Back Cell is opened again.
swyx: Yeah. So Nature Zoo.
Zoo is Nature Zoo. Zoo Robot Taxi. Yeah. So Totally. Yeah.
Nader: Oh. But yeah. And so it’s actually really cool that you guys have this studio so close to, uh, cell. Yeah. This rock climbing gin right around the corner. It was like, um, 2000. Oh yeah. Yeah. It’s, it’s an awesome block.
swyx: Cool. Yeah. Just, and you bit services partnership.
Uh, I do think one, one thing I try to do with the podcast is like bring, like what is, I get to be a San Francisco to the rest of the world and also just like. Maybe give, uh, yeah.
Nader: Yeah. My favorite talk was in the city, uh, and
swyx: yeah, stick and stream. I know. It’s very good.
Nader: Yeah. And I guess what it’s like to be in San Francisco I think is just everyone seems to be super supportive.
Uh, sometimes I feel like the city believes in you more than you do. And even, uh, I don’t know if you remember, but I remember [01:22:00] posting my first blog post and I had met you on Twitter and you gave me like an hour of your time super randomly, and you kind of coached me through, uh, writing content for developers.
And I was trying really hard not to come off salesy or plug myself. And so I kind of stripped all personality out of the blog post. Yeah. And you, you brought that out. You’re like, people don’t, it’s, it’s okay to talk about what you’re doing. Like you don’t have to be weird about it. And I remember just that, I think that really helped me kind of figure out what our voice is and not shy away from it.
And so always really grateful for you. Hey, you inject your voice into like, everything. Now it’s actually a huge advantage to be like very
Kyle: genuine about what you care about.
swyx: Yeah. Yeah. You imagine like summer, some infra in DMU and like, it’s like, can you gimme feedback on this blog post? And it’s pretty boring and you’re like.
Find like, you know, he looks interesting. I’ll just do a zoom call and then you meet this guy. Yeah, right. He’s so energetic, so just be right. There’s, but like, I think people are trained to write a certain way in school and Yeah. They never totally see there’s like a broader well,
and
Nader: lots un unlearn
Kyle: writing.
Writing is thinking and like everyone thinks differently. So [01:23:00] like, might as well as just like,
swyx: yeah. Yeah.
Kyle: Write your way.
swyx: Cool. Well, thank you for, uh, in indulging with us, uh, really broad breaking discussion, but I love, like, you guys are like, sort of like the sort of young faces on video with so much energy and, but like also lot of technic death and I think, uh, people learn about for this session.
So thank you.
Nader: This was awesome. Thank you guys. So thank you for everything that you’ve done in the talk. Yeah, NG the podcast, all the above. And uh, C-O-T-C-I really forward to it. Yeah. Cool. Thanks. That’s awesome. Thank you. Thank you.


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.latent.space/subscribe

All speakers are announced at AIE EU, schedule coming soon. Join us there or in Miami with the renowned organizers of React Miami! Singapore CFP also open!
We’ve called this out a few times over in AINews, but the overwhelming consensus in the Valley is that “the IDE is Dead”. In November it was just a gut feeling, but now we actually have data: even at the canonical “VSCode Fork” company, people are officially using more agents than tab autocomplete (the first wave of AI coding):
Cursor has launched cloud agents for a few months now, and this specific launch is around Computer Use, which has come a long way since we first talked with Anthropic about it in 2024, and which Jonas productized as Autotab:

We also take the opportunity to do a live demo, talk about slash commands and subagents, and the future of continual learning and personalized coding models, something that Sam previously worked on at New Computer. (The fact that both of these folks are top tier CEOs of their own startups that have now joined the insane talent density gathering at Cursor should also not be overlooked).

Full Episode on YouTube!
please like and subscribe!

Timestamps
00:00 Agentic Code Experiments00:53 Why Cloud Agents Matter02:08 Testing First Pillar03:36 Video Reviews Second Pillar04:29 Remote Control Third Pillar06:17 Meta Demos and Bug Repro13:36 Slash Commands and MCPs18:19 From Tab to Team Workflow31:41 Minimal Web UI Philosophy32:40 Why No File Editor34:38 Full Stack Cursor Debate36:34 Model Choice and Auto Routing38:34 Parallel Agents and Best Of N41:41 Subagents and Context Management44:48 Grind Mode and Throughput Future01:00:24 Cloud Agent Onboarding and Memory

Transcript
EP 77 - CURSOR - Audio version
[00:00:00]
Agentic Code Experiments
Samantha: This is another experiment that we ran last year and didn’t decide to ship at that time, but may come back to LM Judge, but one that was also agentic and could write code. So it wasn’t just picking but also taking the learnings from two models or and models that it was looking at and writing a new diff.
And what we found was that there were strengths to using models from different model providers as the base level of this process. Basically you could get almost like a synergistic output that was better than having a very unified like bottom model tier.
Jonas: We think that over the coming months, the big unlock is not going to be one person with a model getting more done, like the water flowing faster and we’ll be making the pipe much wider and so paralyzing more, whether that’s swarms of agents or parallel agents, both of those are things that contribute to getting much more done in the same amount of time.
Why Cloud Agents Matter
swyx: This week, one of the biggest launches that Cursor’s ever done is cloud agents. I think you, you had [00:01:00] cloud agents before, but this was like, you give cursor a computer, right? Yeah. So it’s just basically they bought auto tab and then they repackaged it. Is that what’s going on, or,
Jonas: that’s a big part of it.
Yeah. Cloud agents already ran in their own computers, but they were sort of site reading code. Yeah. And those computers were not, they were like blank VMs typically that were not set up for the Devrel X for whatever repo the agents working on. One of the things that we talk about is if you put yourself in the model shoes and you were seeing tokens stream by and all you could do was cite read code and spit out tokens and hope that you had done the right thing,
swyx: no chance
Jonas: I’d be so bad.
Like you obviously you need to run the code. And so that I think also is probably not that contrarian of a take, but no one has done that yet. And so giving the model the tools to onboard itself and then use full computer use end-to-end pixels in coordinates out and have the cloud computer with different apps in it is the big unlock that we’ve seen internally in terms of use usage of this going from, oh, we use it for little copy changes [00:02:00] to no.
We’re really like driving new features with this kind of new type of entech workflow. Alright, let’s see it. Cool.
Live Demo Tour
Jonas: So this is what it looks like in cursor.com/agents. So this is one I kicked off a while ago. So on the left hand side is the chat. Very classic sort of agentic thing. The big new thing here is that the agent will test its changes.
So you can see here it worked for half an hour. That is because it not only took time to write the tokens of code, it also took time to test them end to end. So it started Devrel servers iterate when needed. And so that’s one part of it is like model works for longer and doesn’t come back with a, I tried some things pr, but a I tested at pr that’s ready for your review.
One of the other intuition pumps we use there is if a human gave you a PR asked you to review it and you hadn’t, they hadn’t tested it, you’d also be annoyed because you’d be like, only ask me for a review once it’s actually ready. So that’s what we’ve done with
Testing Defaults and Controls
swyx: simple question I wanted to gather out front.
Some prs are way smaller, [00:03:00] like just copy change. Does it always do the video or is it sometimes,
Jonas: Sometimes.
swyx: Okay. So what’s the judgment?
Jonas: The model does it? So we we do some default prompting with sort. What types of changes to test? There’s a slash command that people can do called slash no test, where if you do that, the model will not test,
swyx: but the default is test.
Jonas: The default is to be calibrated. So we tell it don’t test, very simple copy changes, but test like more complex things. And then users can also write their agents.md and specify like this type of, if you’re editing this subpart of my mono repo, never tested ‘cause that won’t work or whatever.
Videos and Remote Control
Jonas: So pillar one is the model actually testing Pillar two is the model coming back with a video of what it did.
We have found that in this new world where agents can end-to-end, write much more code, reviewing the code is one of these new bottlenecks that crop up. And so reviewing a video is not a substitute for reviewing code, but it is an entry point that is much, much easier to start with than glancing at [00:04:00] some giant diff.
And so typically you kick one off you, it’s done you come back and the first thing that you would do is watch this video. So this is a, video of it. In this case I wanted a tool tip over this button. And so it went and showed me what that looks like in, in this video that I think here, it actually used a gallery.
So sometimes it will build storybook type galleries where you can see like that component in action. And so that’s pillar two is like these demo videos of what it built. And then pillar number three is I have full remote control access to this vm. So I can go heat in here. I can hover things, I can type, I have full control.
And same thing for the terminal. I have full access. And so that is also really useful because sometimes the video is like all you need to see. And oftentimes by the way, the video’s not perfect, the video will show you, is this worth either merging immediately or oftentimes is this worth iterating with to get it to that final stage where I am ready to merge in.
So I can go through some other examples where the first video [00:05:00] wasn’t perfect, but it gave me confidence that we were on the right track and two or three follow-ups later, it was good to go. And then I also have full access here where some things you just wanna play around with. You wanna get a feel for what is this and there’s no substitute to a live preview.
And the VNC kind of VM remote access gives you that.
swyx: Amazing What, sorry? What is VN. And
Jonas: just the remote desktop. Remote desktop. Yeah.
swyx: Sam, any other details that you always wanna call out?
Samantha: Yeah, for me the videos have been super helpful. I would say, especially in cases where a common problem for me with agents and cloud agents beforehand was almost like under specification in my requests where our plan mode and going really back and forth and getting detailed implementation spec is a way to reduce the risk of under specification, but then similar to how human communication breaks down over time, I feel like you have this risk where it’s okay, when I pull down, go to the triple of pulling down and like running this branch locally, I’m gonna see that, like I said, this should be a toggle and you have a checkbox and like, why didn’t you get that detail?
And having the video up front just [00:06:00] has that makes that alignment like you’re talking about a shared artifact with the agent. Very clear, which has been just super helpful for me.
Jonas: I can quickly run through some other Yes. Examples.
Meta Agents and More Demos
Jonas: So this is a very front end heavy one. So one question I was
swyx: gonna say, is this only for front
Jonas: end?
Exactly. One question you might have is this only for front end? So this is another example where the thing I wanted it to implement was a better error message for saving secrets. So the cloud agents support adding secrets, that’s part of what it needs to access certain systems. Part of onboarding that is giving access.
This is cloud is working on
swyx: cloud agents. Yes.
Jonas: So this is a fun thing is
Samantha: it can get super meta. It
Jonas: can get super meta, it can start its own cloud agents, it can talk to its own cloud agents. Sometimes it’s hard to wrap your mind around that. We have disabled, it’s cloud agents starting more cloud agents. So we currently disallow that.
Someday you might. Someday we might. Someday we might. So this actually was mostly a backend change in terms of the error handling here, where if the [00:07:00] secret is far too large, it would oh, this is actually really cool. Wow. That’s the Devrel tools. That’s the Devrel tools. So if the secret is far too large, we.
Allow secrets above a certain size. We have a size limit on them. And the error message there was really bad. It was just some generic failed to save message. So I was like, Hey, we wanted an error message. So first cool thing it did here, zero prompting on how to test this. Instead of typing out the, like a character 5,000 times to hit the limit, it opens Devrel tools, writes js, or to paste into the input 5,000 characters of the letter A and then hit save, closes the Devrel tools, hit save and gets this new gets the new error message.
So that looks like the video actually cut off, but here you can see the, here you can see the screenshot of the of the error message. What, so that is like frontend backend end-to-end feature to, to get that,
swyx: yeah.
Jonas: And
swyx: And you just need a full vm, full computer run everything.
Okay. Yeah.
Jonas: Yeah. So we’ve had versions of this. This is one of the auto tab lessons where we started that in 2022. [00:08:00] No, in 2023. And at the time it was like browser use, DOM, like all these different things. And I think we ended up very sort of a GI pilled in the sense that just give the model pixels, give it a box, a brain in a box is what you want and you want to remove limitations around context and capabilities such that the bottleneck should be the intelligence.
And given how smart models are today, that’s a very far out bottleneck. And so giving it its full VM and having it be onboarded with Devrel X set up like a human would is just been for us internally a really big step change in capability.
swyx: Yeah I would say, let’s call it a year ago the models weren’t even good enough to do any of this stuff.
So
Samantha: even six months ago. Yeah.
swyx: So yeah what people have told me is like round about Sonder four fire is when this started being good enough to just automate fully by pixel.
Jonas: Yeah, I think it’s always a question of when is good enough. I think we found in particular with Opus 4 5, 4, 6, and Codex five three, that those were additional step [00:09:00] changes in the autonomy grade capabilities of the model to just.
Go off and figure out the details and come back when it’s done.
swyx: I wanna appreciate a couple details. One 10 Stack Router. I see it. Yeah. I’m a big fan. Do you know any, I have to name the 10 Stack.
Jonas: No.
swyx: This just a random lore. Some buddy Sue Tanner. My and then the other thing if you switch back to the video.
Jonas: Yeah.
swyx: I wanna shout out this thing. Probably Sam did it. I don’t know
Jonas: the chapters.
swyx: What is this called? Yeah, this is called Chapters. Yeah. It’s like a Vimeo thing. I don’t know. But it’s so nice the design details, like the, and obviously a company called Cursor has to have a beautiful cursor
Samantha: and it is
swyx: the cursor.
Samantha: Cursor.
swyx: You see it branded? It’s the cursor. Cursor, yeah. Okay, cool. And then I was like, I complained to Evan. I was like, okay, but you guys branded everything but the wallpaper. And he was like, no, that’s a cursor wallpaper. I was like, what?
Samantha: Yeah. Rio picked the wallpaper, I think. Yeah. The video.
That’s probably Alexi and yeah, a few others on the team with the chapters on the video. Matthew Frederico. There’s been a lot of teamwork on this. It’s a huge effort.
swyx: I just, I like design details.
Samantha: Yeah.
swyx: And and then when you download it adds like a little cursor. Kind of TikTok clip. [00:10:00] Yes. Yes.
So it’s to make it really obvious is from Cursor,
Jonas: we did the TikTok branding at the end. This was actually in our launch video. Alexi demoed the cloud agent that built that feature. Which was funny because that was an instance where one of the things that’s been a consequence of having these videos is we use best of event where you run head to head different models on the same prompt.
We use that a lot more because one of the complications with doing that before was you’d run four models and they would come back with some giant diff, like 700 lines of code times four. It’s what are you gonna do? You’re gonna review all that’s horrible. But if you come back with four 22nd videos, yeah, I’ll watch four 22nd videos.
And then even if none of them is perfect, you can figure out like, which one of those do you want to iterate with, to get it over the line. Yeah. And so that’s really been really fun.
Bug Repro Workflow
Jonas: Here’s another example. That’s we found really cool, which is we’ve actually turned since into a slash command as well slash [00:11:00] repro, where for bugs in particular, the model of having full access to the to its own vm, it can first reproduce the bug, make a video of the bug reproducing, fix the bug, make a video of the bug being fixed, like doing the same pattern workflow with obviously the bug not reproducing.
And that has been the single category that has gone from like these types of bugs, really hard to reproduce and pick two tons of time locally, even if you try a cloud agent on it. Are you confident it actually fixed it to when this happens? You’ll merge it in 90 seconds or something like that.
So this is an example where, let me see if this is the broken one or the, okay, this is the fixed one. Okay. So we had a bug on cursor.com/agents where if you would attach images where remove them. Then still submit your prompt. They would actually still get attached to the prompt. Okay. And so here you can see Cursor is using, its full desktop by the way.
This is one of the cases where if you just do, browse [00:12:00] use type stuff, you’ll have a bad time. ‘cause now it needs to upload files. Like it just uses its native file viewer to do that. And so you can see here it’s uploading files. It’s going to submit a prompt and then it will go and open up. So this is the meta, this is cursor agent, prompting cursor agent inside its own environment.
And so you can see here bug, there’s five images attached, whereas when it’s submitted, it only had one image.
swyx: I see. Yeah. But you gotta enable that if you’re gonna use cur agent inside cur.
Jonas: Exactly. And so here, this is then the after video where it went, it does the same thing. It attaches images, removes, some of them hit send.
And you can see here, once this agent is up, only one of the images is left in the attachments. Yeah.
swyx: Beautiful.
Jonas: Okay. So easy merge.
swyx: So yeah. When does it choose to do this? Because this is an extra step.
Jonas: Yes. I think I’ve not done a great job yet of calibrating the model on when to reproduce these things.
Yeah. Sometimes it will do it of its own accord. Yeah. We’ve been conservative where we try to have it only do it when it’s [00:13:00] quite sure because it does add some amount of time to how long it takes it to work on it. But we also have added things like the slash repro command where you can just do, fix this bug slash repro and then it will know that it should first make you a video of it actually finding and making sure it can reproduce the bug.
swyx: Yeah. Yeah. One sort of ML topic this ties into is reward hacking, where while you write test that you update only pass. So first write test, it shows me it fails, then make you test pass, which is a classic like red green.
Jonas: Yep.
swyx: Like
Jonas: A-T-D-D-T-D-D
swyx: thing.
No, very cool. Was that the last demo? Is there
Jonas: Yeah.
Anything I missed on the demos or points that you think? I think that
Samantha: covers it well. Yeah.
swyx: Cool. Before we stop the screen share, can you gimme like a, just a tour of the slash commands ‘cause I so God ready. Huh, what? What are the good ones?
Samantha: Yeah, we wanna increase discoverability around this too.
I think that’ll be like a future thing we work on. Yeah. But there’s definitely a lot of good stuff now
Jonas: we have a lot of internal ones that I think will not be that interesting. Here’s an internal one that I’ve made. I don’t know if anyone else at Cursor uses this one. Fix bb.
Samantha: I’ve never heard of it.
Jonas: Yeah.[00:14:00]
Fix Bug Bot. So this is a thing that we want to integrate more tightly on. So you made it for
swyx: yourself.
Jonas: I made this for myself. It’s actually available to everyone in the team, but yeah, no one knows about it. But yeah, there will be Bug bot comments and so Bug Bot has a lot of cool things. We actually just launched Bug Bot Auto Fix, where you can click a button and or change a setting and it will automatically fix its own things, and that works great in a bunch of cases.
There are some cases where having the context of the original agent that created the PR is really helpful for fixing the bugs, because it might be like, oh, the bug here is that this, is a regression and actually you meant to do something more like that. And so having the original prompt and all of the context of the agent that worked on it, and so here I could just do, fix or we used to be able to do fixed PB and it would do that.
No test is another one that we’ve had. Slash repro is in here. We mentioned that one.
Samantha: One of my favorites is cloud agent diagnosis. This is one that makes heavy use of the Datadog MCP. Okay. And I [00:15:00] think Nick and David on our team wrote, and basically if there is a problem with a cloud agent we’ll spin up a bunch of subs.
Like a single
swyx: instance.
Samantha: Yeah. We’ll take the ideas and argument and spin up a bunch of subagents using the Datadog MCP to explore the logs and find like all of the problems that could have happened with that. It takes the debugging time, like from potentially you can do quick stuff quickly with the Datadog ui, but it takes it down to, again, like a single agent call as opposed to trolling through logs yourself.
Jonas: You should also talk about the stuff we’ve done with transcripts.
Samantha: Yes. Also so basically we’ve also done some things internally. There’ll be some versions of this as we ship publicly soon, where you can spit up an agent and give it access to another agent’s transcript to either basically debug something that happened.
So act as an external debugger. I see. Or continue the conversation. Almost like forking it.
swyx: A transcript includes all the chain of thought for the 11 minutes here. 45 minutes there.
Samantha: Yeah. That way. Exactly. So basically acting as a like secondary agent that debugs the first, so we’ve started to push more and
swyx: they’re all the same [00:16:00] code.
It is just the different prompts, but the sa the same.
Samantha: Yeah. So basically same cloud agent infrastructure and then same harness. And then like when we do things like include, there’s some extra infrastructure that goes into piping in like an external transcript if we include it as an attachment.
But for things like the cloud agent diagnosis, that’s mostly just using the Datadog MCP. ‘Cause we also launched CPS along with along with this cloud agent launch, launch support for cloud agent cps.
swyx: Oh, that was drawn out.
Jonas: We won’t, we’ll be doing a bigger marketing moment for it next week, but, and you can now use CPS and
swyx: People will listen to it as well.
Yeah,
Jonas: they’ll
Samantha: be ahead of the third. They’ll be ahead. And I would I actually don’t know if the Datadog CP is like publicly available yet. I realize this not sure beta testing it, but it’s been one of my favorites to use. So
swyx: I think that one’s interesting for Datadog. ‘cause Datadog wants to own that site.
Interesting with Bits. I don’t know if you’ve tried bits.
Samantha: I haven’t tried bits.
swyx: Yeah.
Jonas: That’s their cloud agent
swyx: product. Yeah. Yeah. They want to be like we own your logs and give us our, some part of the, [00:17:00] self-healing software that everyone wants. Yeah. But obviously Cursor has a strong opinion on coding agents and you, you like taking away from the which like obviously you’re going to do, and not every company’s like Cursor, but it’s interesting if you’re a Datadog, like what do you do here?
Do you expose your logs to FDP and let other people do it? Or do you try to own that it because it’s extra business for you? Yeah. It’s like an interesting one.
Samantha: It’s a good question. All I know is that I love the Datadog MCP,
Jonas: And yeah, it is gonna be no, no surprise that people like will demand it, right?
Samantha: Yeah.
swyx: It’s, it’s like any
system
swyx: of record company like this, it’s like how much do you give away? Cool. I think that’s that for the sort of cloud agents tour. Cool. And we just talk about like cloud agents have been when did Kirsten loves cloud agents? Do you know, in June
Jonas: last year.
swyx: June last year. So it’s been slowly develop the thing you did, like a bunch of, like Michael did a post where himself, where he like showed this chart of like ages overtaking tap. And I’m like, wow, this is like the biggest transition in code.
Jonas: Yeah.
swyx: Like in, in [00:18:00] like the last,
Jonas: yeah. I think that kind of got turned out.
Yeah. I think it’s a very interest,
swyx: not at all. I think it’s been highlighted by our friend Andre Kati today.
Jonas: Okay.
swyx: Talk more about it. What does it mean? Yeah. Is I just got given like the cursor tab key.
Jonas: Yes. Yes.
swyx: That’s that’s
Samantha: cool.
swyx: I know, but it’s gonna be like put in a museum.
Jonas: It is.
Samantha: I have to say I haven’t used tab a little bit myself.
Jonas: Yeah. I think that what it looks like to code with AI code generally creates software, even if you want to go higher level. Is changing very rapidly. No, not a hot take, but I think from our vendor’s point at Cursor, I think one of the things that is probably underappreciated from the outside is that we are extremely self-aware about that fact and Kerscher, got its start in phase one, era one of like tab and auto complete.
And that was really useful in its time. But a lot of people start looking at text files and editing code, like we call it hand coding. Now when you like type out the actual letters, it’s
swyx: oh that’s cute.
Jonas: Yeah.
swyx: Oh that’s cute.
Jonas: You’re so boomer. So boomer. [00:19:00] And so that I think has been a slowly accelerating and now in the last few months, rapidly accelerating shift.
And we think that’s going to happen again with the next thing where the, I think some of the pains around tab of it’s great, but I actually just want to give more to the agent and I don’t want to do one tab at a time. I want to just give it a task and it goes off and does a larger unit of work and I can.
Lean back a little bit more and operate at that higher level of abstraction that’s going to happen again, where it goes from agents handing you back diffs and you’re like in the weeds and giving it, 32nd to three minute tasks, to, you’re giving it, three minute to 30 minute to three hour tasks and you’re getting back videos and trying out previews rather than immediately looking at diffs every single time.
swyx: Yeah. Anything to add?
Samantha: One other shift that I’ve noticed as our cloud agents have really taken off internally has been a shift from primarily individually driven development to almost this collaborative nature of development for us, slack is actually almost like a development on [00:20:00] Id basically.
So I
swyx: like maybe don’t even build a custom ui, like maybe that’s like a debugging thing, but actually it’s that.
Samantha: I feel like, yeah, there’s still so much to left to explore there, but basically for us, like Slack is where a lot of development happens. Like we will have these issue channels or just like this product discussion channels where people are always at cursing and that kicks off a cloud agent.
And for us at least, we have team follow-ups enabled. So if Jonas kicks off at Cursor in a thread, I can follow up with it and add more context. And so it turns into almost like a discussion service where people can like collaborate on ui. Oftentimes I will kick off an investigation and then sometimes I even ask it to get blame and then tag people who should be brought in. ‘cause it can tag people in Slack and then other people will come
swyx: in, can tag other people who are not involved in conversation. Yes. Can just do at Jonas if say, was talking to,
Samantha: yeah.
swyx: That’s cool. You should, you guys should make a big good deal outta that.
Samantha: I know. It’s a lot to, I feel like there’s a lot more to do with our slack surface area to show people externally. But yeah, basically like it [00:21:00] can bring other people in and then other people can also contribute to that thread and you can end up with a PR again, with the artifacts visible and then people can be like, okay, cool, we can merge this.
So for us it’s like the ID is almost like moving into Slack in some ways as well.
swyx: I have the same experience with, but it’s not developers, it’s me. Designer salespeople.
Samantha: Yeah.
swyx: So me on like technical marketing, vision, designer on design and then salespeople on here’s the legal source of what we agreed on.
And then they all just collaborate and correct. The agents,
Jonas: I think that we found when these threads is. The work that is left, that the humans are discussing in these threads is the nugget of what is actually interesting and relevant. It’s not the boring details of where does this if statement go?
It’s do we wanna ship this? Is this the right ux? Is this the right form factor? Yeah. How do we make this more obvious to the user? It’s like those really interesting kind of higher order questions that are so easy to collaborate with and leave the implementation to the cloud agent.
Samantha: Totally. And no more discussion of am I gonna do this? Are you [00:22:00] gonna do this cursor’s doing it? You just have to decide. You like it.
swyx: Sometimes the, I don’t know if there’s a, this probably, you guys probably figured this out already, but since I, you need like a mute button. So like cursor, like we’re going to take this offline, but still online.
But like we need to talk among the humans first. Before you like could stop responding to everything.
Jonas: Yeah. This is a design decision where currently cursor won’t chime in unless you explicitly add Mention it. Yeah. Yeah.
Samantha: So it’s not always listening.
Yeah.
Jonas: I can see all the intermediate messages.
swyx: Have you done the recursive, can cursor add another cursor or spawn another cursor?
Samantha: Oh,
Jonas: we’ve done some versions of this.
swyx: Because, ‘cause it can add humans.
Jonas: Yes. One of the other things we’ve been working on that’s like an implication of generating the code is so easy is getting it to production is still harder than it should be.
And broadly, you solve one bottleneck and three new ones pop up. Yeah. And so one of the new bottlenecks is getting into production and we have a like joke internally where you’ll be talking about some feature and someone says, I have a PR for that. Which is it’s so easy [00:23:00] to get to, I a PR for that, but it’s hard still relatively to get from I a PR for that to, I’m confident and ready to merge this.
And so I think that over the coming weeks and months, that’s a thing that we think a lot about is how do we scale up compute to that pipeline of getting things from a first draft An agent did.
swyx: Isn’t that what Merge isn’t know what graphite’s for, like
Jonas: graphite is a big part of that. The cloud agent testing
swyx: Is it fully integrated or still different companies
Jonas: working on I think we’ll have more to share there in the future, but the goal is to have great end-to-end experience where Cursor doesn’t just help you generate code tokens, it helps you create software end-to-end.
And so review is a big part of that, that I think especially as models have gotten much better at writing code, generating code, we’ve felt that relatively crop up more,
swyx: sorry this is completely unplanned, but like there I have people arguing one to you need ai. To review ai and then there is another approach, thought school of thought where it’s no, [00:24:00] reviews are dead.
Like just show me the video. It’s it like,
Samantha: yeah. I feel again, for me, the video is often like alignment and then I often still wanna go through a code review process.
swyx: Like still look at the files and
Samantha: everything. Yeah. There’s a spectrum of course. Like the video, if it’s really well done and it does like fully like test everything, you can feel pretty competent, but it’s still helpful to, to look at the code.
I make hep pay a lot of attention to bug bot. I feel like Bug Bot has been a great really highly adopted internally. We often like, won’t we tell people like, don’t leave bug bot comments unaddressed. ‘cause we have such high confidence in it. So people always address their bug bot comments.
Jonas: Once you’ve had two cases where you merged something and then you went back later, there was a bug in it, you merged, you went back later and you were like, ah, bug Bot had found that I should have listened to Bug Bot.
Once that happens two or three times, you learn to wait for bug bot.
Samantha: Yeah. So I think for us there’s like that code level review where like it’s looking at the actual code and then there’s like the like feature level review where you’re looking at the features. There’s like a whole number of different like areas.
There’ll probably eventually be things like performance level review, security [00:25:00] review, things like that where it’s like more more different aspects of how this feature might affect your code base that you want to potentially leverage an agent to help with.
Jonas: And some of those like bug bot will be synchronous and you’ll typically want to wait on before you merge.
But I think another thing that we’re starting to see is. As with cloud agents, you scale up this parallelism and how much code you generate. 10 person startups become, need the Devrel X and pipelines that a 10,000 person company used to need. And that looks like a lot of the things I think that 10,000 person companies invented in order to get that volume of software to production safely.
So that’s things like, release frequently or release slowly, have different stages where you release, have checkpoints, automated ways of detecting regressions. And so I think we’re gonna need stacks merg stack diffs merge queues. Exactly. A lot of those things are going to be important
swyx: forward with.
I think the majority of people still don’t know what stack stacks are. And I like, I have many friends in Facebook and like I, I’m pretty friendly with graphite. I’ve just, [00:26:00] I’ve never needed it ‘cause I don’t work on that larger team and it’s just like democratization of no, only here’s what we’ve already worked out at very large scale and here’s how you can, it benefits you too.
Like I think to me, one of the beautiful things about GitHub is that. It’s actually useful to me as an individual solo developer, even though it’s like actually collaboration software.
Jonas: Yep.
swyx: And I don’t think a lot of Devrel tools have figured that out yet. That transition from like large down to small.
Jonas: Yeah. Kers is probably an inverse story.
swyx: This is small down to
Jonas: Yeah. Where historically Kers share, part of why we grew so quickly was anyone on the team could pick it up and in fact people would pick it up, on the weekend for their side project and then bring it into work. ‘cause they loved using it so much.
swyx: Yeah.
Jonas: And I think a thing that we’ve started working on a lot more, not us specifically, but as a company and other folks at Cursor, is making it really great for teams and making it the, the 10th person that starts using Cursor in a team. Is immediately set up with things like, we launched Marketplace recently so other people can [00:27:00] configure what CPS and skills like plugins.
So skills and cps, other people can configure that. So that my cursor is ready to go and set up. Sam loves the Datadog, MCP and Slack, MCP you’ve also been using a lot but
Samantha: also pre-launch, but I feel like it’s so good.
Jonas: Yeah, my cursor should be configured if Sam feels strongly that’s just amazing and required.
swyx: Is it automatically shared or you have to go and.
Jonas: It depends on the MCP. So some are obviously off per user. Yeah. And so Sam can’t off my cursor with my Slack MCP, but some are team off and those can be set up by admins.
swyx: Yeah. Yeah. That’s cool. Yeah, I think, we had a man on the pod when cursor was five people, and like everyone was like, okay, what’s the thing?
And then it’s usually something teams and org and enterprise, but it’s actually working. But like usually at that stage when you’re five, when you’re just a vs. Code fork it’s like how do you get there? Yeah. Will people pay for this? People do pay for it.
Jonas: Yeah. And I think for cloud agents, we expect.[00:28:00]
To have similar kind of PLG things where I think off the bat we’ve seen a lot of adoption with kind of smaller teams where the code bases are not quite as complex to set up. Yes. If you need some insane docker layer caching thing for builds not to take two hours, that’s going to take a little bit longer for us to be able to support that kind of infrastructure.
Whereas if you have front end backend, like one click agents can install everything that they need themselves.
swyx: This is a good chance for me to just ask some technical sort of check the box questions. Can I choose the size of the vm?
Jonas: Not yet. We are planning on adding that. We
swyx: have, this is obviously you want like LXXL, whatever, right?
Like it’s like the Amazon like sort menu.
Jonas: Yes, exactly. We’ll add that.
swyx: Yeah. In some ways you have to basically become like a EC2, almost like you rent a box.
Jonas: You rent a box. Yes. We talk a lot about brain in a box. Yeah. So cursor, we want to be a brain in a box,
swyx: but is the mental model different? Is it more serverless?
Is it more persistent? Is. Something else.
Samantha: We want it to be a bit persistent. The desktop should be [00:29:00] something you can return to af even after some days. Like maybe you go back, they’re like still thinking about a feature for some period of time. So the
swyx: full like sus like suspend the memory and bring it back and then keep going.
Samantha: Exactly.
swyx: That’s an interesting one because what I actually do want, like from a manna and open crawl, whatever, is like I want to be able to log in with my credentials to the thing, but not actually store it in any like secret store, whatever. ‘cause it’s like this is the, my most sensitive stuff.
Yeah. This is like my email, whatever. And just have it like, persist to the image. I don’t know how it was hood, but like to rehydrate and then just keep going from there. But I don’t think a lot of infra works that way. A lot of it’s stateless where like you save it to a docker image and then it’s only whatever you can describe in a Docker file and that’s it.
That’s the only thing you can cl multiple times in parallel.
Jonas: Yeah. We have a bunch of different ways of setting them up. So there’s a dockerfile based approach. The main default way is actually snapshotting
swyx: like a Linux vm
Jonas: like vm, right? You run a bunch of install commands and then you snapshot more or less the file system.
And so that gets you set up for everything [00:30:00] that you would want to bring a new VM up from that template basically.
swyx: Yeah.
Jonas: And that’s a bit distinct from what Sam was talking about with the hibernating and re rehydrating where that is a full memory snapshot as well. So there, if I had like the browser open to a specific page and we bring that back, that page will still be there.
swyx: Was there any discussion internally and just building this stuff about every time you shoot a video it’s actually you show a little bit of the desktop and the browser and it’s not necessary if you just show the browser. If, if you know you’re just demoing a front end application.
Why not just show the browser, right? Like it Yeah,
Samantha: we do have some panning and zooming. Yeah. Like it can decide that when it’s actually recording and cutting the video to highlight different things. I think we’ve played around with different ways of segmenting it and yeah. There’s been some different revs on it for sure.
Jonas: Yeah. I think one of the interesting things is the version that you see now in cursor.com actually is like half of what we had at peak where we decided to unshift or unshipped quite a few things. So two of the interesting things to talk about, one is directly an answer to your [00:31:00] question where we had native browser that you would have locally, it was basically an iframe that via port forwarding could load the URL could talk to local host in the vm.
So that gets you basically, so in
swyx: your machine’s browser,
like
Jonas: in your local browser? Yeah. You would go to local host 4,000 and that would get forwarded to local host 4,000 in the VM via port forward. We unshift that like at
swyx: Eng Rock.
Jonas: Like an Eng Rock. Exactly. We unshift that because we felt that the remote desktop was sufficiently low latency and more general purpose.
So we build Cursor web, but we also build Cursor desktop. And so it’s really useful to be able to have the full spectrum of things. And even for Cursor Web, as you saw in one of the examples, the agent was uploading files and like I couldn’t upload files and open the file viewer if I only had access to the browser.
And we’ve thought a lot about, this might seem funny coming from Cursor where we started as this, vs. Code Fork and I think inherited a lot of amazing things, but also a lot [00:32:00] of legacy UI from VS Code.
Minimal Web UI Surfaces
Jonas: And so with the web UI we wanted to be very intentional about keeping that very minimal and exposing the right sum of set of primitive sort of app surfaces we call them, that are shared features of that cloud.
Environment that you and the agent both use. So agent uses desktop and controls it. I can use desktop and controlled agent runs terminal commands. I can run terminal commands. So that’s how our philosophy around it. The other thing that is maybe interesting to talk about that we unshipped is and we may, both of these things we may reship and decide at some point in the future that we’ve changed our minds on the trade offs or gotten it to a point where, put
swyx: it out there.
Let users tell you they want it. Exactly. Alright, fine.
Why No File Editor
Jonas: So one of the other things is actually a files app. And so we used to have the ability at one point during the process of testing this internally to see next to, I had GID desktop and terminal on the right hand side of the tab there earlier to also have a files app where you could see and edit files.
And we actually felt that in some [00:33:00] ways, by restricting and limiting what you could do there, people would naturally leave more to the agent and fall into this new pattern of delegating, which we thought was really valuable. And there’s currently no way in Cursor web to edit these files.
swyx: Yeah. Except you like open up the PR and go into GitHub and do the thing.
Jonas: Yeah.
swyx: Which is annoying.
Jonas: Just tell the agent,
swyx: I have criticized open AI for this. Because Open AI is Codex app doesn’t have a file editor, like it has file viewer, but isn’t a file editor.
Jonas: Do you use the file viewer a lot?
swyx: No. I understand, but like sometimes I want it, the one way to do it is like freaking going to no, they have a open in cursor button or open an antigravity or, opening whatever and people pointed that.
So I was, I was part of the early testers group people pointed that and they were like, this is like a design smell. It’s like you actually want a VS. Code fork that has all these things, but also a file editor. And they were like, no, just trust us.
Jonas: Yeah. I think we as Cursor will want to, as a product, offer the [00:34:00] whole spectrum and so you want to be able to.
Work at really high levels of abstraction and double click and see the lowest level. That’s important. But I also think that like you won’t be doing that in Slack. And so there are surfaces and ways of interacting where in some cases limiting the UX capabilities makes for a cleaner experience that’s more simple and drives people into these new patterns where even locally we kicked off joking about this.
People like don’t really edit files, hand code anymore. And so we want to build for where that’s going and not where it’s been
swyx: a lot of cool stuff. And Okay. I have a couple more.
Full Stack Hosting Debate
swyx: So observations about the design elements about these things. One of the things that I’m always thinking about is cursor and other peers of cursor start from like the Devrel tools and work their way towards cloud agents.
Other people, like the lovable and bolts of the world start with here’s like the vibe code. Full cloud thing. They were already cloud edges before anyone else cloud edges and we will give you the full deploy platform. So we own the whole loop. We own all the infrastructure, we own, we, we have the logs, we have the the live site, [00:35:00] whatever.
And you can do that cycle cursor doesn’t own that cycle even today. You don’t have the versal, you don’t have the, you whatever deploy infrastructure that, that you’re gonna have, which gives you powers because anyone can use it. And any enterprise who, whatever you infra, I don’t care. But then also gives you limitations as to how much you can actually fully debug end to end.
I guess I’m just putting out there that like is there a future where there’s like full stack cursor where like cursor apps.com where like I host my cursor site this, which is basically a verse clone, right? I don’t know.
Jonas: I think that’s a interesting question to be asking, and I think like the logic that you laid out for how you would get there is logic that I largely agree with.
swyx: Yeah. Yeah.
Jonas: I think right now we’re really focused on what we see as the next big bottleneck and because things like the Datadog MCP exist, yeah. I don’t think that the best way we can help our customers ship more software. Is by building a hosting solution right now,
swyx: by the way, these are things I’ve actually discussed with some of the companies I just named.
Jonas: Yeah, for sure. Right now, just this big bottleneck is getting the code out there and also [00:36:00] unlike a lovable in the bolt, we focus much more on existing software. And the zero to one greenfield is just a very different problem. Imagine going to a Shopify and convincing them to deploy on your deployment solution.
That’s very different and I think will take much longer to see how that works. May never happen relative to, oh, it’s like a zero to one app.
swyx: I’ll say. It’s tempting because look like 50% of your apps are versal, superb base tailwind react it’s the stack. It’s what everyone does.
So I it’s kinda interesting.
Jonas: Yeah.
Model Choice and Auto Routing
swyx: The other thing is the model select dying. Right now in cloud agents, it’s stuck down, bottom left. Sure it’s Codex High today, but do I care if it’s suddenly switched to Opus? Probably not.
Samantha: We definitely wanna give people a choice across models because I feel like it, the meta change is very frequently.
I was a big like Opus 4.5 Maximalist, and when codex 5.3 came out, I hard, hard switch. So that’s all I use now.
swyx: Yeah. Agreed. I don’t know if, but basically like when I use it in Slack, [00:37:00] right? Cursor does a very good job of exposing yeah. Cursors. If people go use it, here’s the model we’re using.
Yeah. Here’s how you switch if you want. But otherwise it’s like extracted away, which is like beautiful because then you actually, you should decide.
Jonas: Yeah, I think we want to be doing more with defaults.
swyx: Yeah.
Jonas: Where we can suggest things to people. A thing that we have in the editor, the desktop app is auto, which will route your request and do things there.
So I think we will want to do something like that for cloud agents as well. We haven’t done it yet. And so I think. We have both people like Sam, who are very savvy and want know exactly what model they want, and we also have people that want us to pick the best model for them because we have amazing people like Sam and we, we are the experts.
Yeah. We have both the traffic and the internal taste and experience to know what we think is best.
swyx: Yeah. I have this ongoing pieces of agent lab versus model lab. And to me, cursor and other companies are example of an agent lab that is, building a new playbook that is different from a model lab where it’s like very GP heavy Olo.
So obviously has a research [00:38:00] team. And my thesis is like you just, every agent lab is going to have a router because you’re going to be asked like, what’s what. I don’t keep up to every day. I’m not a Sam, I don’t keep up every day for using you as sample the arm arbitrator of taste. Put me on CRI Auto.
Is it free? It’s not free.
Jonas: Auto’s not free, but there’s different pricing tiers. Yeah.
swyx: Put me on Chris. You decide from me based on all the other people you know better than me. And I think every agent lab should basically end up doing this because that actually gives you extra power because you like people stop carrying or having loyalty with one lab.
Jonas: Yeah.
Best Of N and Model Councils
Jonas: Two other maybe interesting things that I don’t know how much they’re on your radar are one the best event thing we mentioned where running different models head to head is actually quite interesting because
swyx: which exists in cursor.
Jonas: That exists in cur ID and web. So the problem is where do you run them?
swyx: Okay.
Jonas: And so I, I can share my screen if that’s interesting. Yeahinteresting.
swyx: Yeah. Yeah. Obviously parallel agents, very popal.
Jonas: Yes, exactly. Parallel agents
swyx: in you mind. Are they the same thing? Best event and parallel agents? I don’t want to [00:39:00] put words in your mouth.
Jonas: Best event is a subset of parallel agents where they’re running on the same prompt.
That would be my answer. So this is what that looks like. And so here in this dropdown picker, I can just select multiple models.
swyx: Yeah.
Jonas: And now if I do a prompt, I’m going to do something silly. I am running these five models.
swyx: Okay. This is this fake clone, of course. The 2.0 yeah.
Jonas: Yes, exactly. But they’re running so the cursor 2.0, you can do desktop or cloud.
So this is cloud specifically where the benefit over work trees is that they have their own VMs and can run commands and won’t try to kill ports that the other one is running. Which are some of the pains. These are all
swyx: called work trees?
Jonas: No, these are all cloud agents with their own VMs.
swyx: Okay. But
Jonas: When you do it locally, sometimes people do work trees and that’s been the main way that people have set out parallel so far.
I’ve gotta say.
swyx: That’s so confusing for folks.
Jonas: Yeah.
swyx: No one knows what work trees are.
Jonas: Exactly. I think we’re phasing out work trees.
swyx: Really.
Jonas: Yeah.
swyx: Okay.
Samantha: But yeah. And one other thing I would say though on the multimodel choice, [00:40:00] so this is another experiment that we ran last year and the decide to ship at that time but may come back to, and there was an interesting learning that’s relevant for, these different model providers. It was something that would run a bunch of best of ends but then synthesize and basically run like a synthesizer layer of models. And that was other agents that would take LM Judge, but one that was also agentic and could write code. So it wasn’t just picking but also taking the learnings from two models or, and models that it was looking at and writing a new diff.
And what we found was that at the time at least, there were strengths to using models from different model providers as the base level of this process. Like basically you could get almost like a synergistic output that was better than having a very unified, like bottom model tier. So it was really interesting ‘cause it’s like potentially, even though even in the future when you have like maybe one model as ahead of the other for a little bit, there could be some benefit from having like multiple top tier models involved in like a [00:41:00] model swarm or whatever agent Swarm that you’re doing, that they each have strengths and weaknesses.
Yeah.
Jonas: Andre called this the council, right?
Samantha: Yeah, exactly. We actually, oh, that’s another internal command we have that Ian wrote slash council. Oh, and they some, yeah.
swyx: Yes. This idea is in various forms everywhere. And I think for me, like for me, the productization of it, you guys have done yeah, like this is very flexible, but.
If I were to add another Yeah, what your thing is on here it would be too much. I what, let’s say,
Samantha: Ideally it’s all, it’s something that the user can just choose and it all happens under the hood in a way where like you just get the benefit of that process at the end and better output basically, but don’t have to get too lost in the complexity of judging along the way.
Jonas: Okay.
Subagents for Context
Jonas: Another thing on the many agents, on different parallel agents that’s interesting is an idea that’s been around for a while as well that has started working recently is subagents. And so this is one other way to get agents of the different prompts and different goals and different models, [00:42:00] different vintages to work together.
Collaborate and delegate.
swyx: Yeah. I’m very like I like one of my, I always looking for this is the year of the blah, right? Yeah. I think one of the things on the blahs is subs. I think this is of but I haven’t used them in cursor. Are they fully formed or how do I honestly like an intro because do I form them from new every time?
Do I have fixed subagents? How are they different for slash commands? There’s all these like really basic questions that no one stops to answer for people because everyone’s just like too busy launching. We have to
Samantha: honestly, you could, you can see them in cursor now if you just say spin up like 50 subagents to, so cursor defines
swyx: what Subagents.
Yeah.
Samantha: Yeah. So basically I think I shouldn’t speak for the whole subagents team. This is like a different team that’s been working on this, but our thesis or thing that we saw internally is that like they’re great for context management for kind of long running threads, or if you’re trying to just throw more compute at something.
We have strongly used, almost like a generic task interface where then the main agent can define [00:43:00] like what goes into the subagent. So if I say explore my code base, it might decide to spin up an explore subagent and or might decide to spin up five explore subagent.
swyx: But I don’t get to set what those subagent are, right?
It’s all defined by a model.
Samantha: I think. I actually would have to refresh myself on the sub agent interface.
Jonas: There are some built-in ones like the explore subagent is free pre-built. But you can also instruct the model to use other subagents and then it will. And one other example of a built-in subagent is I actually just kicked one off in cursor and I can show you what that looks like.
swyx: Yes. Because I tried to do this in pure prompt space.
Jonas: So this is the desktop app? Yeah. Yeah. And that’s
swyx: all you need to do, right? Yeah.
Jonas: That’s all you need to do. So I said use a sub agent to explore and I think, yeah, so I can even click in and see what the subagent is working on here. It ran some fine command and this is a composer under the hood.
Even though my main model is Opus, it does smart routing to take, like in this instance the explorer sort of requires reading a ton of things. And so a faster model is really useful to get an [00:44:00] answer quickly, but that this is what subagent look like. And I think we wanted to do a lot more to expose hooks and ways for people to configure these.
Another example of a cus sort of builtin subagent is the computer use subagent in the cloud agents, where we found that those trajectories can be long and involve a lot of images obviously, and execution of some testing verification task. We wanted to use that models that are particularly good at that.
So that’s one reason to use subagents. And then the other reason to use subagents is we want contexts to be summarized reduced down at a subagent level. That’s a really neat boundary at which to compress that rollout and testing into a final message that agent writes that then gets passed into the parent rather than having to do some global compaction or something like that.
swyx: Awesome. Cool. While we’re in the subagents conversation, I can’t do a cursor conversation and not talk about listen stuff. What is that? What is what? He built a browser. He built an os. Yes. And he [00:45:00] experimented with a lot of different architectures and basically ended up reinventing the software engineer org chart.
This is all cool, but what’s your take? What’s, is there any hole behind the side? The scenes stories about that kind of, that whole adventure.
Samantha: Some of those experiments have found their way into a feature that’s available in cloud agents now, the long running agent mode internally, we call it grind mode.
And I think there’s like some hint of grind mode accessible in the picker today. ‘cause you can do choose grind until done. And so that was really the result of experiments that Wilson started in this vein where he I think the Ralph Wigga loop was like floating around at the time, but it was something he also independently found and he was experimenting with.
And that was what led to this product surface.
swyx: And it is just simple idea of have criteria for completion and do not. Until you complete,
Samantha: there’s a bit more complexity as well in, in our implementation. Like there’s a specific, you have to start out by aligning and there’s like a planning stage where it will work with you and it will not get like start grind execution mode until it’s decided that the [00:46:00] plan is amenable to both of you.
Basically,
swyx: I refuse to work until you make me happy.
Jonas: We found that it’s really important where people would give like very underspecified prompt and then expect it to come back with magic. And if it’s gonna go off and work for three minutes, that’s one thing. When it’s gonna go off and work for three days, probably should spend like a few hours upfront making sure that you have communicated what you actually want.
swyx: Yeah. And just to like really drive from the point. We really mean three days that No, no
Jonas: human. Oh yeah. We’ve had three day months innovation whatsoever.
Samantha: I don’t know what the record is, but there’s been a long time with the grants
Jonas: and so the thing that is available in cursor. The long running agent is if you wanna think about it, very abstractly that is like one worker node.
Whereas what built the browser is a society of workers and planners and different agents collaborating. Because we started building the browser with one worker node at the time, that was just the agent. And it became one worker node when we realized that the throughput of the system was not where it needed to be [00:47:00] to get something as large of a scale as the browser done.
swyx: Yeah.
Jonas: And so this has also become a really big mental model for us with cloud, cloud agents is there’s the classic engineering latency throughput trade-offs. And so you know, the code is water flowing through a pipe. The, we think that over the coming months, the big unlock is not going to be one person with a model getting more done, like the water flowing faster and we’ll be making the pipe much wider and so ing more, whether that’s swarms of agents or parallel agents, both of those are things that contribute to getting.
Much more done in the same amount of time, but any one of those tasks doesn’t necessarily need to get done that quickly. And throughput is this really big thing where if you see the system of a hundred concurrent agents outputting thousands of tokens a second, you can’t go back like that.
Just you see a glimpse of the future where obviously there are many caveats. Like no one is using this browser. IRL. There’s like a bunch of things not quite right yet, but we are going to get to systems that produce real production [00:48:00] code at the scale much sooner than people think. And it forces you to think what even happens to production systems. Like we’ve broken our GitHub actions recently because we have so many agents like producing and pushing code that like CICD is just overloaded. ‘cause suddenly it’s like effectively weg grew, cursor’s growing very quickly anyway, but you grow head count, 10 x when people run 10 x as many agents.
And so a lot of these systems, exactly, a lot of these systems will need to adapt.
swyx: It also reminds me, we, we all, the three of us live in the app layer, but if you talk to the researchers who are doing RL infrastructure, it’s the same thing. It’s like all these parallel rollouts and scheduling them and making sure as much throughput as possible goes through them.
Yeah, it’s the same thing.
Jonas: We were talking briefly before we started recording. You were mentioning memory chips and some of the shortages there. The other thing that I think is just like hard to wrap your head around the scale of the system that was building the browser, the concurrency there.
If Sam and I both have a system like that running for us, [00:49:00] shipping our software. The amount of inference that we’re going to need per developer is just really mind-boggling. And that makes, sometimes when I think about that, I think that even with, the most optimistic projections for what we’re going to need in terms of buildout, our underestimating, the extent to which these swarm systems can like churn at scale to produce code that is valuable to the economy.
And,
swyx: yeah, you can cut this if it’s sensitive, but I was just Do you have estimates of how much your token consumption is?
Jonas: Like per developer?
swyx: Yeah. Or yourself. I don’t need like comfy average. I just curious. I
Samantha: feel like I, for a while I wasn’t an admin on the usage dashboard, so I like wasn’t able to actually see, but it was a,
swyx: mine has gone up.
Samantha: Oh yeah.
swyx: But I think
Samantha: it’s in terms of how much work I’m doing, it’s more like I have no worries about developers losing their jobs, at least in the near term. ‘cause I feel like that’s a more broad discussion.
swyx: Yeah. Yeah. You went there. I didn’t go, I wasn’t going there.
I was just like how much more are you using?
Samantha: There’s so much stuff to be built. And so I feel like I’m basically just [00:50:00] trying to constantly I have more ambitions than I did before. Yes. Personally. Yes. So can’t speak to the broader thing. But for me it’s like I’m busier than ever before.
I’m using more tokens and I am also doing more things.
Jonas: Yeah. Yeah. I don’t have the stats for myself, but I think broadly a thing that we’ve seen, that we expect to continue is J’S paradox. Where
swyx: you can’t do it in our podcast without seeing
Jonas: it. Exactly. We’ve done it. Now we can wrap. We’ve done, we said the words.
Phase one tab auto complete people paid like 20 bucks a month. And that was great. Phase two where you were iterating with these local models. Today people pay like hundreds of dollars a month. I think as we think about these highly parallel kind of agents running off for a long times in their own VM system, we are already at that point where people will be spending thousands of dollars a month per human, and I think potentially tens of thousands and beyond, where it’s not like we are greedy for like capturing more money, but what happens is just individuals get that much more leverage.
And if one person can do as much as 10 people, yeah. That tool that allows ‘em to do that is going to be tremendously valuable [00:51:00] and worth investing in and taking the best thing that exists.
swyx: One more question on just the cursor in general and then open-ended for you guys to plug whatever you wanna put.
How is Cursor hiring these days?
Samantha: What do you mean by how?
swyx: So obviously lead code is dead. Oh,
Samantha: okay.
swyx: Everyone says work trial. Different people have different levels of adoption of agents. Some people can really adopt can be much more productive. But other people, you just need to give them a little bit of time.
And sometimes they’ve never lived in a token rich place like cursor.
And once you live in a token rich place, you’re you just work differently. But you need to have done that. And a lot of people anyway, it was just open-ended. Like how has agentic engineering, agentic coding changed your opinions on hiring?
Is there any like broad like insights? Yeah.
Jonas: Basically I’m asking this for other people, right? Yeah, totally. Totally. To hear Sam’s opinion, we haven’t talked about this the two of us. I think that we don’t see necessarily being great at the latest thing with AI coding as a prerequisite.
I do think that’s a sign that people are keeping up and [00:52:00] curious and willing to upscale themselves in what’s happening because. As we were talking about the last three months, the game has completely changed. It’s like what I do all day is very different.
swyx: Like it’s my job and I can’t,
Jonas: Yeah, totally.
I do think that still as Sam was saying, the fundamentals remain important in the current age and being able to go and double click down. And models today do still have weaknesses where if you let them run for too long without cleaning up and refactoring, the coke will get sloppy and there’ll be bad abstractions.
And so you still do need humans that like have built systems before, no good patterns when they see them and know where to steer things.
Samantha: I would agree with that. I would say again, cursor also operates very quickly and leveraging ag agentic engineering is probably one reason why that’s possible in this current moment.
I think in the past it was just like people coding quickly and now there’s like people who use agents to move faster as well. So it’s part of our process will always look for we’ll select for kind of that ability to make good decisions quickly and move well in this environment.
And so I think being able to [00:53:00] figure out how to use agents to help you do that is an important part of it too.
swyx: Yeah. Okay. The fork in the road, either predictions for the end of the year, if you have any, or PUDs.
Jonas: Evictions are not going to go well.
Samantha: I know it’s hard.
swyx: They’re so hard. Get it wrong.
It’s okay. Just, yeah.
Jonas: One other plug that may be interesting that I feel like we touched on but haven’t talked a ton about is a thing that the kind of these new interfaces and this parallelism enables is the ability to hop back and forth between threads really quickly. And so a thing that we have,
swyx: you wanna show something or,
Jonas: yeah, I can show something.
A thing that we have felt with local agents is this pain around contact switching. And you have one agent that went off and did some work and another agent that, that did something else. And so here by having, I just have three tabs open, let’s say, but I can very quickly, hop in here.
This is an example I showed earlier, but the actual workflow here I think is really different in a way that may not be obvious, where, I start the morning, I kick off 10 agents or something, the first one of them [00:54:00] finishes, come in, watch the video either as close. And so I might send a follow up.
I might say, Hey, make it red, or I might hop into the desktop and try it out. And within, 90, 120 seconds, I’ve kicked this one back off. And either started the merge process like CI is running now and I’ll come back to it later or it’s off with some additional follow up information. And then I can hop into the next one.
And then the next one I hop in and I’m like, okay, this looks interesting. Actually try it out for real in the app. I want to see it in action, not just in the gallery. So I can kick that off and the agent will go and work on that because maybe I wanted to try it out, like what the button looks like in the actual thing.
And then here I might hop in as well and, check the video here or do something. And so you’re really parallelizing much more and follow up here, check in there. It’s much more this higher level of abstraction and having the different desktops where you can hop back and forth and you’re [00:55:00] not like, oh, I checked out this branch.
Oh, where was that work tree again? Yeah. It’s really like solving for that which we’ve ourselves have struggled with in cursor and these local agents to be like, where was that diff again? It’s lost in some work tree. Never gonna find it. Oh, my local thing is rebuilding. Oh, just make another one.
That, that’s what you end up with and then you wait for five more minutes for it to run. And so this is really like a new way of just paralleling that we found to be really fun, honestly. Yeah. Where you’re just hopping in and injecting taste and you’re like that doesn’t quite feel right.
Oh, actually this is not architected quite right, but you’re just focusing on those like taste interesting questions.
Samantha: For me, the cloud ecosystem too also enabled this to be like, something that is like adding productivity to my dead time, like commuting or like overnight or something like that.
The fact that I don’t have to leave my computer open,
swyx: there’s no cursor, there is a cursor mobile app.
Samantha: If there is, I’m not sure. It’s like the current thing. We, I use it on my phone all the time, just on the web. So pretty good experience there for checking [00:56:00] in. Yeah. And un unlocking. I think, yeah. You can see the videos and stuff in the web app, which is awesome.
Yeah.
Jonas: Yeah.
swyx: I think this is one that the a DD one inherited the earth, like the, if you’re like, your attention span is cooked, but you still can manage, like actually this is good for you. Yeah. But also I think this is where the coding tools start coming into conflict with the productivity tools where like the linear the canman boards, because what you have there is cool, but you know what, you actually need a cabin board. Which people have vibe, vibe, cam, van is out there. Open source. I’m sure you guys have talked about it, but we’ll start to conflict because actually the code doesn’t matter anymore.
It’s the process of the human interacting and checking in. And seeing, like getting the world of warcrafts sound package to go like work or whatever. It’s like job done or, I don’t know. It’s like an interesting like future productivity thing.
Samantha: Yeah.
swyx: I also think like another big theme like last year li is called like the, your coding agents.
This year another like coding agents spill over to the real world into cloud cowork and all the other stuff. Yeah. I’m sure cursor’s gonna focus on software, but let’s call it like open claw is like extremely [00:57:00] mind expanding in terms of I did not know that could happen.
Jonas: Yeah.
swyx: And it’s all based on a coding agent based totally.
Jonas: And I think one of the things that like talking to, friends and family that are not in the software world that’s interesting is I do. Speeding up predictions. I do think that we are going to start seeing other industries go through what software development has started going through.
I think by virtue of how good models are at writing software and how early adopter the people building the new technology are and trying it out and applying it to themselves, that’s certain kinds of shifts will happen too to other industries. And there’s a lot to be learned from how that’s gone down and is continuing to go down in software.
In terms of, all the interesting questions about to what point do people get more leverage, when do you start changing the role to become much more generalist? Like, all of these questions that we’ve seen some data on, but we’ll see a lot more in the coming months. That will happen everywhere.
swyx: Sammy party thoughts? Any flus of your own?
Samantha: Not really. [00:58:00] It’s fine. I feel we covered so much good draft. We covered it. We covered a lot. Coming up with a prediction. I just think agents are gonna keep getting better. Gonna stop doing as much manual coding, probably zero lines of code written in the whole month of December this year by myself.
A hundred percent agents as a personal prediction, but
swyx: oh, you’re not as zero today.
What in what cases?
Samantha: I think honestly, it’s 1% if I like, just am like, get frustrated and I’m like, I don’t wanna go have it tell an agent to change this one thing. But
Jonas: prompting sometimes I feel like working on prompts sometimes.
Yeah. I still go in and manually edit because it’s so like bare intent transfer that like telling the agent what I want. It’s like writing an essay where I don’t use agents to write essays yet because the process of writing it is the thinking.
Samantha: I still can’t stand AI generated writing. So yeah, I can also can’t have the agent write prompts.
swyx: So no D Spy, no jpa, nothing like that here.
Jonas: We have some internal tooling around some of the prompt optimization things, but there’s a fair amount of just what concepts do I need to communicate to the agent or the model.
swyx: I also noticed another thing I’m also [00:59:00] looking for is voice.
I noticed that you didn’t use your voice to code even open ai. When we do podcasts with them, they don’t use their voice. Yeah. And I’m like at some point this gets good. You can stop typing.
Samantha: We have some people who like that a lot internally, and I think we’ll be experimenting in that space too, for sure.
Jonas: Do you use voice log?
swyx: Not a lot. Sometimes that’s bound to my caps log, so I can press it. I just,
Jonas: and when you use it, do you want it to talk back or you just want
swyx: Yeah,
Jonas: just dump in. Yeah. Yeah.
swyx: But like the brain dump is good. Yeah. Because you can interrupt yourself. You can go on a tangent, whatever.
It just captures everything. Yeah. And lop it into all m, it’s fine.
Jonas: Yeah. The way that we did this with Auto Tab was people would record full screen recordings with audio to teach the model, like how to do a task. And one of the funny things that we learned was people would use their Siri voice, where they would start talking in like short, stilted sentences and enunciate really clearly because they were used to, they last used AI two years ago where you had to
swyx: apple has damaged like an entire generation of people’s expectations.
Jonas: Exactly. And we had to be like, no you’re very native, so [01:00:00] you do this, but just dump everything in. You can say you can repeat yourself. You can contradict yourself. The models are smart enough to figure it out,
swyx: but it’s still very bad. So voice coding was always, I considered like the hardest part because you have to say like technical things that pel like spelling matters, capitalization matters and like it’s all not in voice.
So we’ll see. So far it’s been more sort of emotional companionship, that kind of stuff, but at some point it’s gonna hit voice coding.
Jonas: Yeah. I have a prediction for you. I predict that by the end of the year, the volume on, I think it will take longer than people think and longer than we think for cloud and agents working in their own boxes to surpass local agents.
But I think that crossover will happen before the end of the year and probably by the end of the year, agents running in the cloud will be a multi, like more than two x the volume of local agents.
swyx: Okay. You’re leaving me an opening. What’s not good today?
Jonas: Yeah, there’s a bunch of hard things. So one of them is just getting those [01:01:00] sandboxes to be really good and a thing that was part of this launch that we spend in inordinate amount of time on is cursor.com/onboard where you pick a repo, add secrets, give it access to things, and the agent just goes off and installs things.
swyx: Yes, I think all the whole thing. That was my favorite.
Jonas: Yeah, we worked a lot on that. Sam and I in particular spent a lot of late nights making that good, but there’s still a lot to do there, right? Set up 1, 2, 2 things. Maybe it’s too slow. It’s too slow. Working on it set up is not like a unitary thing where everything is set up or not, right?
Like things will break over time. You have new dependencies, you need access to new systems, like you change where your database lives. So that’s one part of it. And then the other part of it is, having these agents run in the cloud and be more autonomous. We’ve really started to see the lack of memory.
And Sam, as someone who’s thought a lot about this once you start getting the model kind of doing, operating the code base, there’s more particularities that are not it’s not just a read file tool. It needs to know how do I start up the backend, how do I check the status [01:02:00] of the backend?
That’s very particular to your code base. And even if it’s great at NPM Run watch or whatever the default things are, there’s always quirks. Everyone has quirks. And getting the model good at those things will require more work. And we’re working on that. But we think that will be one of the big unlocks, is having them be onboarded not only in terms of their environment, but also in terms of their understanding of design trade-offs, how the code base works, how to be a good developer in any one code base.
swyx: It’s lot crier rules. It’s gonna be something else. Is it gonna be a file? Is it. We just call in either markdown file a different name, and
Samantha: I don’t know. One thing that we learned at, could we be in cursor of the company this year? There, there’s a really great blog post that the Judi and the other people in the agent quality team put out about dynamic file context.
swyx: Is that your team is the different team?
Samantha: Different team, yeah. And they were working on basically doing a lot everything, file system, everything is file system. And so a lot of my thinking personally on memory this past year has changed to be more aligned with that, where it’s like giving the agent pointers to things, annotations [01:03:00] to things.
The second thing I think that I’ve started to think differently about memory is a subset of agent self-audit ability and self-awareness. Basically like the agent might wanna propose annotations or links or memory like files to itself when it finds that there’s like some gap in its functionality in its own harness that might need to be filled by like some piece of information on a semi-permanent basis.
But there’s a whole bunch of other things that are a side effect of self auditability that are really interesting, like potentially finding like conflicting instructions or like skills and rules that like might be like, eh, these are bugging each other. And also things like fixing like Devrel X problems that it runs into.
I think that basically the dynamic file system stuff is probably very promising from memory. And there’s also this notion of needing to have the agent be a little bit more self-aware in terms of being able to identify gaps in its own functionality and decide how to fill them.
Jonas: That’s such a good point.
Like self-awareness broadly has been a really big thing that I think Sam has pushed us to [01:04:00] do more and more of where the agent should understand how its environment works, it should understand how secrets work. Like it needs to be self-aware about its own harness and its environment. And then, and you
swyx: think this is not inherent in the model you have to do.
Jonas: It’s specifics, right? If it’s running in cursor versus some other sandbox that’s a bit different. And then the other part of it that starts to get really interesting is when the model starts editing its own system. Prompt.
swyx: Yeah.
Jonas: What does that even mean? How do you do that safely and then way over
swyx: do that?
This is just research, right? This isn’t, this is
Jonas: I think it will do that. Yeah. It will manage its own context. And so system prompt is part of the context, and you can argue about
Samantha: Yeah, like other things that it might decide to turn off or on depending, and all those, self-awareness to us in this context is not like the model itself, having a notion of consciousness, but more like knowing like what system it’s operating in and the constraints of that system and potentially being able to have agency in optimizing itself to operate best in the, in that system.
This was like one of the [01:05:00] first things I learned at DOT when we launched was that I we had made the model or made the agent or. Whatever we would call it. At that time, it was far less, agentic made the product work very well at a certain number of things, but didn’t have complete self-awareness of like its own boundaries.
So people would be like, Hey, can you do this thing? And the thing was there and could be done and the and the product would be like, oh no. And I’d be like, but you can. And so like basically like that was one of the earliest things I found is
swyx: believe in yourself.
Samantha: I know as a product developer, like it needs to both be able to do the thing and it needs to have complete knowledge of its ability to do the thing.
Those are not always obviously the same like part of the prompt at all.
Yeah.
swyx: Yeah.
Samantha: It’s something that I think has continued to be a theme in the ecosystem that users will often attribute increased intelligence to a system that is more highly self-aware and is more able to like, manipulate itself to do well in a system.
If that makes sense.
swyx: Yeah. This is more abstract than I ever thought would get at Thisor discussion. Cool. That isn’t the kind of [01:06:00] conversation that you have
Samantha: in, we talk about this stuff all the time to
swyx: improving
Samantha: Yeah.
swyx: Agents in general.
Jonas: Yeah. I think to your point right about the agent layer and thinking a lot about models and the harness and the product and the affordances like that.
Yeah. Falls from the
swyx: No, I mean you guys are like my sort of needing example what an agent lab looks like and can be successful and I think people always hungry for insights into how you guys operate, so thank you for taking the time to share.
Samantha: Yeah. Thanks for coming.
Yeah. Thank you.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.latent.space/subscribe

The reception to our recent post on Code Reviews has been strong. Catch up!
Amid a maelstrom of discussion on whether or not AI is killing SaaS, one of the top publicly listed SaaS companies in the world has just reported record revenues, clearing well over $1.1B in ARR for the first time with a 28% margin. As we comment on the pod, Aaron Levie is the rare public company CEO equally at home in both worlds of Silicon Valley and Wall Street/Main Street, by day helping 70% of the Fortune 500 with their Enterprise Advanced Suite, and yet by night is often found in the basements of early startups and tweeting viral insights about the future of agents.
Now that both Cursor, Cloudflare, Perplexity, Anthropic and more have made Filesystems and Sandboxes and various forms of “Just Give the Agent a Box” cool (not just cool; it is now one of the single hottest areas in AI infrastructure growing 100% MoM), we find it a delightfully appropriate time to do the episode with the OG CEO who has been giving humans and computers Boxes since he was a college dropout pitching VCs at a Michael Arrington house party.
Enjoy our special pod, with fan favorite returning guest/guest cohost Jeff Huber!
Note: We didn’t directly discuss the AI vs SaaS debate - Aaron has done many, many, many other podcasts on that, and you should read his definitive essay on it. Most commentators do not understand SaaS businesses because they have never scaled one themselves, and deeply reflected on what the true value proposition of SaaS is.
We also discuss Your Company is a Filesystem:

We also shoutout CTO Ben Kus’ and the AI team, who talked about the technical architecture and will return for AIE WF 2026.

Full Video Episode

Timestamps
* 00:00 Adapting Work for Agents
* 01:29 Why Every Agent Needs a Box
* 04:38 Agent Governance and Identity
* 11:28 Why Coding Agents Took Off First
* 21:42 Context Engineering and Search Limits
* 31:29 Inside Agent Evals
* 33:23 Industries and Datasets
* 35:22 Building the Agent Team
* 38:50 Read Write Agent Workflows
* 41:54 Docs Graphs and Founder Mode
* 55:38 Token FOMO Culture
* 56:31 Production Function Secrets
* 01:01:08 Film Roots to Box
* 01:03:38 AI Future of Movies
* 01:06:47 Media DevRel and Engineering

Transcript
Adapting Work for Agents
Aaron Levie: Like you don’t write code, you talk to an agent and it goes and does it for you, and you may be at best review it. That’s even probably like, like largely not even what you’re doing. What’s happening is we are changing our work to make the agents effective. In that model, the agent didn’t really adapt to how we work.
We basically adapted to how the agent works. All of the economy has to go through that exact same evolution. Right now, it’s a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this ‘cause you’ll see compounding returns. But that’s just gonna take a while for most companies to actually go and get this deployed.
swyx: Welcome to the Lane Space Pod. We’re back in the chroma studio with uh, chroma, CEO, Jeff Hoover. Welcome returning guest now guest host.
Aaron Levie: It’s a pleasure. Wow. How’d you get upgraded to, uh, to that?
swyx: Because he’s like the perfect guy to be guest those for you.
Aaron Levie: That makes sense actually, for We love context. We, we both really love context le we really do.
We really do.
swyx: Uh, and we’re here with, uh, Aaron Levy. Welcome.
Aaron Levie: Thank you. Good to, uh, good to be [00:01:00] here.
swyx: Uh, yeah. So we’ve all met offline and like chatted a little bit, but like, it’s always nice to get these things in person and conversation. Yeah. You just started off with so much energy. You’re, you’re super excited about agents.
I love
Aaron Levie: agents.
swyx: Yeah. Open claw. Just got by, got bought by OpenAI. No, not bought, but you know, you know what I mean?
Aaron Levie: Some, some, you know, acquihire. Executive
swyx: hire.
Aaron Levie: Executive hire. Okay. Executive hire. Say,
swyx: hey, that’s my term. Okay. Um, what are you pounding the table on on agents? You have so many insightful tweets.
Why Every Agent Needs a Box
Aaron Levie: Well, the thing that, that we get super excited by that I think is probably, you know, should be relatively obvious is we’ve, we’ve built a platform to help enterprises manage their files and their, their corporate files and the permissions of who has access to those files and the sharing collaboration of those files.
All of those files contain really, really important information for the enterprise. It might have your contracts, it might have your research materials, it might have marketing information, it might have your memos. All that data obviously has, you know, predominantly been used by humans. [00:02:00] But there’s been one really interesting problem, which is that, you know, humans only really work with their files during an active engagement with them, and they kind of go away and you don’t really see them for a long time.
And all of a sudden, uh, with the power of AI and AI agents, all of that data becomes extremely relevant as this ongoing source of, of answers to new questions of data that will transform into, into something else that, that produces value in your organization. It, it contains the answer to the new employee that’s onboarding, that needs to ramp up on a project.
Um, it contains the answer to the right thing to sell a customer when you’re having a conversation to them, with them contains the roadmap information that’s gonna produce the next feature. So all that data. That previously we’ve been just sort of storing and, and you know, occasionally forgetting about, ‘cause we’re only working on the new active stuff.
All of that information becomes valuable to the enterprise and it’s gonna become extremely valuable to end users because now they can have agents go find what they’re looking for and produce new, new [00:03:00] value and new data on that information. And it’s gonna become incredibly valuable to agents because agents can roam around and do a bunch of work and they’re gonna need access to that data as well.
And um, and you know, sometimes that will be an agent that is sort of working on behalf of, of, of you and, and effectively as you as and, and they are kind of accessing all of the same information that you have access to and, and operating as you in the system. And then sometimes there’s gonna be agents that are just.
Effectively autonomous and kind of run on their own and, and you’re gonna collaborate and work with them kind of like you did another person. Open Claw being the most recent and maybe first real sort of, you know, kind of, you know, up updating everybody’s, you know, views of this landscape version of, of what that could look like, which is, okay, I have an agent.
It’s on its own system, it’s on its own computer, it has access to its own tools. I probably don’t give it access to my entire life. I probably communicate with it like I would an assistant or a colleague and then it, it sort of has this sandbox environment. So all of that has massive implications for a platform that manage that [00:04:00] enterprise data.
We think it’s gonna just transform how we work with all of the enterprise content that we work with, and we just have to make sure we’re building the right platform to support that.
swyx: The sort of shorthand I put it is as people build agents, everybody’s just realizing that every agent needs a box. Yes.
And it’s nice to be called box and just give everyone a box.
Aaron Levie: Hey, I if I, you know, if we can make that go viral, uh, like I, I think that that terminology, I, that’s the
swyx: tagline. Every agent
Aaron Levie: needs a box. Every agent needs a box. If we can make that the headline of this, I’m fine with this. And that’s the billboard I wanna like Yeah, exactly.
Every agent needs a box. Um, I like it. Can we ship this? Like,
swyx: okay, let’s do it. Yeah.
Aaron Levie: Uh, my work here is done and I got the value I needed outta this podcast Drinks.
swyx: Yeah.
Agent Governance and Identity
Aaron Levie: But, but, um, but, but, you know, so the thing that we, we kind of think about is, um, is, you know, whether you think the number 10 x or a hundred x or whatever the number is, we’re gonna have some order of magnitude more agents than people.
That’s inevitable. It has to happen. So then the question is, what is the infrastructure that’s needed to make all those agents effective in the enterprise? Make sure that they are well governed. Make sure they’re only doing [00:05:00] safe things on your information. Make sure that they’re not getting exposed. The data that they shouldn’t have access to.
There’s gonna be just incredibly spectacularly crazy security incidents that will happen with agents because you’ll prompt, inject an agent and sort of find your way through the CRM system and pull out data that you shouldn’t have access to. Oh, we
Jeff Huber: have God,
Aaron Levie: right? I mean, that’s just gonna happen all over the place, right?
So, so then the thing is, is how do you make sure you have the right security, the permissions, the access controls, the data governance. Um, we actually don’t yet exactly know in many cases how we’re gonna regulate some of these agents, right? If you think about an agent in financial services, does it have the exact same financial sort of, uh, requirements that a human did?
Or is it, is the risk fully on the human that was interacting or created the agent? All open questions, but no matter what, there’s gonna need to be a layer that manages the, the data they have access to, the workflows that they’re involved in, pulling up data from multiple systems. This is the new infrastructure opportunity in the era of agents.
swyx: You have a piece on agent identities, [00:06:00] which I think was today, um, which I think a lot of breaking news, the security, security people are talking about, right? Like you basically, I, I always think of this as like, well you need the human you and then there you need the agent. You
Aaron Levie: Yes.
swyx: And uh, well, I don’t know if it’s that simple, but is box going to have an opinion on that or you’re just gonna be like, well we’re just the sort of the, the source layer.
Yeah. Let’s Okta of zero handle that.
Aaron Levie: I think we’re gonna have an opinion and we will work with generally wherever the contours of the market end up. Um, and the reason that we’re gonna have an opinion more than other topics probably is because one of the biggest use cases for why your agent might need it, an identity is for file system access.
So thus we have to kind of think about this pretty deeply. And I think, uh, unless you’re like in our world thinking about this particular problem all day long, it might be, you know, like, why is this such a big deal? And the reason why it’s a really big deal is because sometimes sort of say, well just give the agent an, an account on the system and it just treats, treat it like every other type of user on the system.
The [00:07:00] problem is, is that I as Aaron don’t really have any responsibility over anybody else’s box account in our organization. I can’t see the box account of any other employee that I work with. I am not liable for anything that they do. And they have, I have, I have, you know, strict privacy requirements on everything that they’re able to, you know, that, that, that they work on.
Agents don’t have that, you know, don’t have those properties. The person who creates the agent probably is gonna, for the foreseeable future, take on a lot of the liability of what that agent does. That agent doesn’t deserve any privacy because, because it’s, you know, it can’t fully be autonomously operated and it doesn’t have any legal, you know, kind of, you know, responsibility.
So thus you can’t just be like, oh, well I’ll just create a bunch of accounts and then I’ll, I’ll kind of work with that agent and I’ll talk to it occasionally. Like you need oversight of that. And so then the question is, how do you have a world where the agent, sometimes you have oversight of, but what if that agent goes and works with other people?
That person over there is collaborating with the agent on something you shouldn’t have [00:08:00] access to what they’re doing. So we have all of these new boundaries that we’re gonna have to figure out of, of, you know, it’s really, really easy. So far we’ve been in, in easy mode. We’ve hit the easy button with ai, which is the agent just is you.
And when you’re in quad code and you’re in cursor, and you’re in Codex, you’re just, the agent is you. You’re offing into your services. It can do everything you can do. That’s the easy mode. The hard mode is agents are kind of running on their own. People check in with them occasionally, they’re doing things autonomously.
How do you give them access to resources in the enterprise and not dramatically increased the security risk and the risk that you might expose the wrong thing to somebody. These are all the new problems that we have to get solved. I like the identity layer and, and identity vendors as being a solution to that, but we’ll, we’ll need some opinions as well because so many of the use cases are these collaborative file system use cases, which is how do I give it an agent, a subset of my data?
Give it its own workspace as well. ‘cause it’s gonna need to store off its own information that would be relevant for it. And how do I have the right oversight into that? [00:09:00]
Jeff Huber: One thing, which, um, I think is kind interesting, think about is that you know, how humans work, right? Like I may not also just like give you access to the whole file.
I might like sit next to you and like scroll to this like one part of the file and just show you that like one part and like, you know,
swyx: partial file access.
Jeff Huber: I’m just saying I think like our, like RA does seem to be dead, right? Like you wanna say something is dead uhhuh probably RA is dead. And uh, like the auth story to me seems like incredibly unsolved and unaddressed by like the existing state of like AI vendors.
But
Aaron Levie: yeah, I think, um, we’re, I mean you’re taking obviously really to level limit that we probably need to solve for. Yeah. And we built an access control system that was, was kind of like, you know, its own little world for, for a long time. And um, and the idea was this, it’s a many to many collaboration system where I can give you any part of the file system.
And it’s a waterfall model. So if I give you higher up in the, in the, in the system, you get everything below. And that, that kind of created immense flexibility because I can kind of point you to any layer in the, in the tree, but then you’re gonna get access to everything kind of below it. And that [00:10:00] mostly is, is working in this, in this world.
But you do have to manage this issue, which is how do I create an agent that has access to some of my stuff and somebody else’s stuff as well. Mm-hmm. And which parts do I get to look at as the creator of the agent? And, and these are just brand new problems? Yeah. Crazy. And humans, when there was a human there that was really easy to do.
Like, like if the three of us were all sharing, there’d be a Venn diagram where we’d have an overlapping set of things we’ve shared, but then we’d have our own ways that we shared with each other. In an agent world, somebody needs to take responsibility for what that agent has access to and what they’re working on.
These are like the, some of the most probably, you know, boring problems for 98% of people on, on the internet, but they will be the problems that are the difference between can you actually have autonomous agents in an enterprise context
swyx: Yeah.
Aaron Levie: That are not leaking your data constantly.
swyx: No. Like, I mean, you know, I run a very, very small company for my conference and like we already have data sensitivity issues.
Yes. And some of my team members cannot see Yes. Uh, the others and like, I can’t imagine what it’s like to run a Fortune 500 and like, you have to [00:11:00] worry about this. I’m just kinda curious, like you, you talked to a lot like, like 70, 80% of your cus uh, of the Fortune 500, your customers.
Aaron Levie: Yep. 67%. Just so we’re being very
SE
swyx: precise.
So Yeah. I’m not
Aaron Levie: Okay. Okay.
swyx: Something I’m rounding up. Yes. Round up. I’m projecting to, for
Aaron Levie: the government.
swyx: I’m projecting to the end of the year.
Aaron Levie: Okay.
swyx: There you go.
Aaron Levie: You do make it sound like, like we, we, well we’ve gotta be on this. Like we’re, we’re taking way too long to get to 80%. Well,
swyx: no, I mean, so like. How are they approaching it?
Right? Because you’re, you don’t have a, you don’t have a final answer yet.
Why Coding Agents Took Off First
Aaron Levie: Well, okay, so, so this is actually, this is the stark reality that like, unfortunately is the kinda like pouring the water on the party a little bit.
swyx: Yes.
Aaron Levie: We all in Silicon Valley are like, have the absolute best conditions possible for AI ever.
And I think we all saw the dke, you know, kind of Dario podcast and this idea of AI coding. Why is that taken off? And, and we’re not yet fully seeing it everywhere else. Well, look, if you just like enumerated the list of properties that AI coding has and then compared it to other [00:12:00] knowledge work, let’s just, let’s just go through a few of them.
Generally speaking, you bring on a new engineer, they have access to a large swath of the code base. Like, there’s like very, like you, just, like new engineer comes on, they can just go and find the, the, the stuff that they, they need to work with. It’s a fully text in text out. Medium. It’s only, it’s just gonna be text at the end of the day.
So it’s like really great from a, from just a, uh, you know, kinda what the agent can work with. Obviously the models are super trained on that dataset. The labs themselves have a really strong, kind of self-reinforcing positive flywheel of why they need to do, you know, agent coding deeply. So then you get just better tooling, better services.
The actual developers of the AI are daily users of the, of the thing that they’re we’re working on versus like the, you know, probably there’s only like seven Claude Cowork legal plugin users at Anthropic any given day, but there’s like a couple thousand Claude code and you know, users every single day.
So just like, think about which one are they getting more feedback on. All day long. So you just go through this list. You have a, you know, everybody who’s a [00:13:00] developer by definition is technical so they can go install the latest thing. We’re all generally online, or at least, you know, kinda the weird ones are, and we’re all talking to each other, sharing best practices, like that’s like already eight differences.
Versus the rest of the economy. Every other part of the economy has like, like six to seven headwinds relative to that list. You go into a company, you’re a banker in financial services, you have access to like a, a tiny little subset of the total data that’s gonna be relevant to do your job. And you’re have to start to go and talk to a bunch of people to get the right data to do your job because Sally didn’t add you to that deal room, you know, folder.
And that that, you know, the information is actually in a completely different organization that you now have to go in and, and sort of run into. And it’s like you have this endless list of access controls and security. As, as you talked about, you have a medium, which is not, it’s not just text, right? You have, you have a zoom call that, that you’re getting all of the requirements from the customer.
You have a lot of in-person conversations and you’re doing in-person sales and like how do you ever [00:14:00] digitize all of that information? Um, you know, I think a lot of people got upset with this idea that the code base has all the context, um, that I don’t know if you follow, you know, did you follow some of that conversation that that went viral?
Is like, you know, it’s not that simple that, that the code base doesn’t have all the knowledge, but like it’s a lot, you’re a lot better off than you are with other areas of knowledge work. Like you, we like, we like have documentation practices, you write specifications. Those things don’t exist for like 80% of work that happens in the enterprise.
That’s the divide that we have, which is, which is AI coding has, has just fully, you know, where we’ve reached escape velocity of how powerful this stuff is, and then we’re gonna have to find a way to bring that same energy and momentum, but to all these other areas of knowledge work. Where the tools aren’t there, the data’s not set up to be there.
The access controls don’t make it that easy. The context engineering is an incredibly hard problem because again, you have access control challenges, you have different data formats. You have end users that are gonna need to kind of be kind of trained through this as opposed to their adopting [00:15:00] these tools in their free time.
That’s where the Fortune 500 is. And so we, I think, you know, have to be prepared as an industry where we are gonna be on a multi-year march to, to be able to bring agents to the enterprise for these workflows. And I think probably the, the thing that we’ve learned most in coding that, that the rest of the world is not yet, I think ready for, I mean, we’re, they’ll, they’ll have to be ready for it because it’s just gonna inevitably happen is I think in coding.
What, what’s interesting is if you think about the practice of coding today versus two years ago. It’s probably the most changed workflow in maybe the history of time from the amount of time it’s changed, right? Yeah. Like, like has any, has any workflow in the entire economy changed that quickly in terms of the amount of change?
I just, you know, at least in any knowledge worker workflow, there’s like very rarely been an event where one piece of technology and work practice has so fundamentally, you know, changed, changed what you do. Like you don’t write code, you talk to an agent and it goes and [00:16:00] does it for you, and you may be at best review it.
And even that’s even probably like, like largely not even what you’re doing. What’s happening is we are changing our work to make the agents effective. In that model, the agent didn’t really adapt to how we work. We basically adapted to how the agent works. Mm-hmm. All of the economy has to go through that exact same evolution.
The rest of the economy is gonna have to update its workflows to make agents effective. And to give agents the context that they need and to actually figure out what kind of prompting works and to figure out how do you ensure that the agent has the right access to information to be able to execute on its work.
I, you know, this is not the panacea that people were hoping for, of the agent drops in, just automates your life. Like you have to basically re-engineer your workflow to get the most out of agents and, uh, and that, that’s just gonna take, you know, multiple years across the economy. Right now it’s a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this.
‘cause [00:17:00] you’ll see compounding returns, but that’s just gonna take a while for most companies to actually go and get this deployed.
swyx: I love, I love pushing back. I think that. That is what a lot of technology consultants love to hear this sort of thing, right? Yeah, yeah, yeah. First to, to embrace the ai. Yes. To get to the promised land, you must pay me so much money to a hundred percent to adopt the prescribed way of, uh, conforming to the agents.
Yes. And I worry that you will be eclipsed by someone else who says, no, come as you are.
Aaron Levie: Yeah.
swyx: And we’ll meet you where you are.
Aaron Levie: And, and, and and what was the thing that went viral a week ago? OpenAI probably, uh, is hiring F Dees. Yeah. Uh, to go into the enterprise. Yeah. Yeah. And then philanthropic is embedded at Goldman Sachs.
Yeah. So if the labs are having to do this, if, if the labs have decided that they need to hire FDE and professional services, then I think that’s a pretty clear indication that this, there’s no easy mode of workflow transformation. Yeah. Yeah. So, so to your point, I think actually this is a market opportunity for, you know, new professional services and consulting [00:18:00] firms that are like Agent Build and they, and they kind of, you know, go into organizations and they figure out how to re-engineer your workflows to make them more agent ready and get your data into the right format and, you know, reconstruct your business process.
So you’re, you’re not doing most of the work. You’re telling agents how to do the work and then you’re reviewing it. But I haven’t seen the thing that can just drop in and, and kinda let you not go through those changes.
swyx: I don’t know how that kind of sales pitch goes over. Yeah. You know, you’re, you’re saying things like, well, in my sort of nice beautiful walled garden, here’s, there’s, uh, because here’s this, here’s this beautiful box account that has everything.
Yes. And I’m like, well, most, most real life is extremely messy. Sure. And like, poorly named and there duplicate this outdated s**t
Aaron Levie: a hundred percent. And so No, no, a hundred percent. And so this is actually No. So, so this is, I mean, we agree that, that getting to the beautiful garden is gonna be tough.
swyx: Yeah.
Aaron Levie: There’s also the other end of the spectrum where I, I just like, it’s a technical impossibility to solve. The agent is, is truly cannot get enough context to make the right decision in, in the, in the incredibly messy land. Like there’s [00:19:00] no a GI that will solve that. So, so we’re gonna have to kind of land in somewhere in between, which is like we all collectively get better at.
Documentation practices and, and having authoritative relatively up-to-date information and putting it in the right place like agents will, will certainly cause us to be much better organized around how we work with our information, simply because the severity of the agent pulling the wrong data will be too high and the productivity gain of that you’ll miss out on by not doing this will be too high as well, that you, that your competition will just do it and they’ll just have higher velocity.
So, uh, and, and we, we see this a lot firsthand. So we, we build a series of agents internally that they can kind of have access to your full box account and go off and you give it a task and it can go find whatever information you’re looking for and work with. And, you know, thank God for the model progress, but like, if, if you gave that task to an agent.
Nine months ago, you’re just gonna get lots of bogus answers because it’s gonna, it’s gonna say, Hey, here’s, here are fi [00:20:00] five, you know, documents that all kind of smell like the right thing. And I’m gonna, but I, but you’re, you’re putting me on the clock. ‘cause my assistant prompt says like, you know, be pretty smart, but also try and respond to the user and it’s gonna respond.
And it’s like, ah, it got the wrong document. And then you do that once or twice as a knowledge worker and you’re just never
swyx: again,
Aaron Levie: never again. You’re just like done with the system.
swyx: Yeah. It doesn’t work.
Aaron Levie: It doesn’t work. And so, you know, Opus four six and Gemini three one Pro and you know, whatever the latest five 3G BT will be, like, those things are getting better and better and it’s using better judgment.
And this sort of like the, all of these updates to the agentic tool and search systems are, are, we’re seeing, we’re seeing very real progress where the agent. Kind of can, can almost smell some things a little bit fishy when it’s getting, you know, we, we have this process where we, we have it go fan out, do a bunch of searches, pull up a bunch of data, and then it has to sort of do its own ranking of, you know, what are the right documents that, that it should be working with.
And again, like, you know, the intelligence level of a model six months ago, [00:21:00] it’d be just throwing a dart at like, I’m just, I’m gonna grab these seven files and I, I pray, I hope that that’s the right answer. And something like an opus first four five, and now four six is like, oh, it’s like, no, that one doesn’t seem right relative to this question because I’m seeing some signal that is making that, you know, that’s contradicting the document where it would normally be in the tree and who should have access.
Like it’s doing all of that kind of work for you. But like, it still doesn’t work if you just have a total wasteland of data. Like, it’s just not, it’s just not possible. Partly ‘cause a human wouldn’t even be able to do it. So basically if a, if a really, really smart human. Could not do that task in five or 10 minutes for a search retrieval type task.
Look, you know, your agent’s not gonna be able to do it any better. You see this all day long. So
Context Engineering and Search Limits
swyx: this touches on a thing that just passionate about it was just context engineering. I, I’m just gonna let you ramble or riff on, on context engineering. If, if, if there’s anything like he, he did really good work on context fraud, which has really taken over as like the term that people use and the reference
Aaron Levie: a hundred percent.
We, we all we think about is, is the context rob problem. [00:22:00]
Jeff Huber: Yeah, there’s certainly a lot of like ranking considerations. Gentech surgery think is incredibly promising. Um, yeah, I was trying to generate a question though. I think I have a question right now. Swyx.
Aaron Levie: Yeah, no, but like, like I think there was this moment, um, you know, like, I don’t know, two years ago before, before we knew like where the, the gotchas were gonna be in ai and I think someone was like, was like, well, infinite context windows will just solve all of these problems and ‘cause you’ll just, you’ll just give the context window like all the data and.
It’s just like, okay, I mean, maybe in 2035, like this is a viable solution. First of all, it, it would just, it would just simply cost too much. Like we just can’t give the model like the 5,000 documents that might be relevant and it’s gonna read them all. And I’ve seen enough to, to start believing in crazy stuff.
So like, I’m willing to just say, sure. Like in, in 10 years from now,
swyx: never say, never, never.
Aaron Levie: In, in 10 years from now, we’ll have infinite context windows at, at a thousandth of the price of today. Like, let’s just like believe that that’s possible, but Right. We’re in reality today. So today we have a context engineering [00:23:00] problem, which is, I got, I got, you know, 200,000 tokens that I can work with, or prob, I don’t even know what the latest graph is before, like massive degradation.
16. Okay. I have 60,000 tokens that I get to work with where I’m gonna get accurate information. That’s not a lot of tokens for a corpus of 10 million documents that a knowledge worker might have across all of the teams and all the projects and all the people they work with. I have, I have 10 million documents.
Which, you know, maybe is times five pages per document or something like that. I’m at 50 million pages of information and I have 60,000 tokens. Like, holy s**t. Yeah. This is like, how do I bridge the 50 million pages of information with, you know, the couple hundred that I get to work with in that, in that token window.
Yeah. This is like, this is like such an interesting problem and that’s why actually so much work is actually like, just like search systems and the databases and that layer has to just get so locked in, but models getting better and importantly [00:24:00] knowing when they’ve done a search, they found the wrong thing, they go back, they check their work, they, they find a way to balance sort of appeasing the user versus double checking.
We have this one, we have this one test case where we ask the agent to go find. 10 pieces of information.
swyx: Is this the complex work eval?
Aaron Levie: Uh, this is actually not in the eval. This is, this is sort of just like we have a bunch of different, we have a bunch of internal benchmark kind of scenarios. Every time we, we update our agent, we have one, which is, I ask it to find all of our office addresses, and I give it the list of 10 offices that we have.
And there’s not one document that has this, maybe there should be, that would be a great example of the kind of thing that like maybe over time companies start to, you know, have these sort of like, what are the canonical, you know, kind of key areas of knowledge that we need to have. We don’t seem to have this one document that says, here are all of our offices.
We have a bunch of documents that have like, here’s the New York office and whatever. So you task this agent and you, you get, you say, I need the addresses for these 10 offices. Okay. And by the way, if you do this on any, you know, [00:25:00] public chat model, the same outcome is gonna happen. But for a different kind of query, you give it, you say, I need these 10 addresses.
How many times should the agent go and do its search before it decides whether or not, there’s just no answer to this question. Often, and especially the, the, let’s say lower tier models, it’ll come back and it’ll give you six of the 10 addresses. And it’ll, and I’ll just say I couldn’t find the other
swyx: four.
It, it doesn’t know what It doesn’t know. It
Aaron Levie: doesn’t know what It doesn’t know. Yeah. So the model is just like, like when should it stop? When should it stop doing? Like should it, should it do that task for literally an hour and just keep cranking through? Maybe I actually made up an office location and it doesn’t know that I made it up and I didn’t even know that I made it up.
Like, should it just keep, re should it read every single file in your entire box account until it, until it should exhaust every single piece of information.
swyx: Expensive.
Aaron Levie: These are the new problems that we have. So, you know, something like, let’s say a new opus model is sort of like, okay, I’m gonna try these types of queries.
I didn’t get exactly what I wanted. I’m gonna try again. I’m gonna, at [00:26:00] some point I’m gonna stop searching. ‘cause I’ve determined that that no amount of searching is gonna solve this problem. I’m just not able to do it. And that judgment is like a really new thing that the model needs to be able to have.
It’s like, when should it give up on a task? ‘cause, ‘cause you just don’t, it’s a can’t find the thing. That’s the real world of knowledge, work problems. And this is the stuff that the coding agents don’t have to deal with. Because they, it just doesn’t like, like you’re not usually asking it about, you’re, you’re always creating net new information coming right outta the model for the most part.
Obviously it has to know about your code base and your specs and your documentation, but, but when you deploy an agent on all of your data that now you have all of these new problems that you’re dealing with
Jeff Huber: our, uh, follow follow-up research to context ride is actually on a genetic search. Ah. Um, and we’ve like right, sort of stress tested like frontier models and their ability to search.
Um, and they’re not actually that good at searching. Right. Uh, so you’re sort of highlighting this like explore, exploit.
swyx: You’re just say, Debbie, Donna say everything doesn’t work. Like,
Aaron Levie: well,
Jeff Huber: somebody has to be,
Aaron Levie: um, can I just throw out one more thing? Yeah. That is different from coding and, and the rest [00:27:00] of the knowledge work that I, I failed to mention.
So one other kind of key point is, is that, you know, at the end of the day. Whether you believe we’re in a slop apocalypse or, or whatever. At the end of the day, if you, if you build a working product at the end of, if you, if you’ve built a working solution that is ultimately what the customer is paying for, like whether I have a lot of slop, a little slop or whatever, I’m sure there’s lots of code bases we could go into in enterprise software companies where it’s like just crazy slop that humans did over a 20 year period, but the end customer just gets this little interface.
They can, they can type into it, it does its thing. Knowledge work, uh, doesn’t have that property. If I have an AI model, go generate a contract and I generate a contract 20 times and, you know, all 20 times it’s just 3% different and like that I, that, that kind of lop introduces all new kinds of risk for my organization that the code version of that LOP didn’t, didn’t introduce.
These are, and so like, so how do you constrain these models to just the part that you want [00:28:00] them to work on and just do the thing that you want them to do? And, and, you know, in engineering, we don’t, you can’t be disbarred as an engineer, but you could be disbarred as a lawyer. Like you can do the wrong medical thing In healthcare, you, there’s no, there’s no equivalent to that of engineering.
Like, do
swyx: you want there to be, because I’ve considered software
Jeff Huber: engineer. What’s that? Civil engineering there is, right? Not
Aaron Levie: software civil engineer. Sure. Oh yeah, for sure. But like in any of our companies, you like, you know, you’ll be forgiven if you took down the site and, and we, we will do a rollback and you’ll, you’ll be in a meeting, but you have not been disbarred as an engineer.
We don’t, we don’t change your, you know, your computer science, uh, blame
Jeff Huber: degree, this postmortem.
Aaron Levie: Yeah, exactly. Exactly. So, so, uh, now maybe we collectively as an industry need to figure out like, what are you liable for? Not legally, but like in a, in a management sense, uh, of these agents. All sorts of interesting problems that, that, that, uh, that have to come out.
But in knowledge work, that’s the real hostile environments that we’re operating in. Hmm.
swyx: I do think like, uh, a lot of the last year’s, 2025 story was the rise of coding agents and I think [00:29:00] 2026 story is definitely knowledge work agents. Yes. A hundred
Aaron Levie: percent.
swyx: Right. Like that would, and I think open claw core work are just the beginning.
Yes. Like it’s, the next one’s gonna just gonna be absolute craziness.
Aaron Levie: It it is. And, and, uh, and it’s gonna be, I mean, again, like this is gonna be this, this wave where we, we are gonna try and bring as many of the practices from coding because that, that will clearly be the forefront, which is tell an agent to go do something and has an access to a set of resources.
You need to be responsible for reviewing it at the end of the process. That to me is the, is the kind of template that I just think goes across knowledge, work and odd. Cowork is a great example. Open Closet’s a great example. You can kind of, sort of see what Codex could become over time. These are some, some really interesting kind of platforms that are emerging.
swyx: Okay. Um, I wanted to, we touched on evals a little bit. You had, you had the report that you’re gonna go bring up and then I was gonna go into like, uh, boxes, evals, but uh, go ahead. Talk about your genetic search thing.
Jeff Huber: Yeah. Mostly I think kinda a few of the insights. It’s like number one frontier model is not good at search.
Humans have this [00:30:00] natural explore, exploit trade off where we kinda understand like when to stop doing something. Also, humans are pretty good at like forgetting actually, and like pruning their own context, whereas agents are not, and actually an agent in their kind of context history, if they knew something was bad and they even, you could see in the trace the reason you trace, Hey, that probably wasn’t a good idea.
If it’s still in the trace, still in the context, they’ll still do it again. Uhhuh. Uh, and so like, I think pruning is also gonna be like, really, it’s already becoming a thing, right? But like, letting self prune the con windows
swyx: be a big deal. Yeah. So, so don’t leave the mistake. Don’t leave the mistake in there.
Cut out the mistake but tell it that you made a mistake in the past and so it doesn’t repeat it.
Jeff Huber: Yeah. But like cut it out so it doesn’t get like distracted by it again. ‘cause really, you know, what is so, so it will repeat its mistake just because it’s been, it’s in
swyx: the
Jeff Huber: context. It’s
Aaron Levie: in the context so much.
That’s a few shot example. Even if it, yeah.
Jeff Huber: It’s like oh this
Aaron Levie: is a great thing to go try even if
Jeff Huber: it didn’t work.
Aaron Levie: Yeah,
Jeff Huber: exactly.
Aaron Levie: So
Jeff Huber: there’s like a bunch of stuff there. Just
Aaron Levie: Groundhogs Day inside these models. Yeah. I’m gonna go keep doing the same wrong
Jeff Huber: thing. Covering sense. I feel like, you know, some creator analogy you’re trying like fit a manifold in latent space, which kind is doing break program synthesis, which is kinda one we think about we’re doing right.
Like, you know, certain [00:31:00] facts might be like sort of overly pitting it. There are certain, you know, sec sectors of latent space and so like plug clean space. Yeah. And, uh, and
swyx: so we have a bell, our editor as a bell every time you say that. So
Jeff Huber: you have, you have to like remove those, like
swyx: you shoulda a gong like TPN or something.
If
Jeff Huber: we gong, you either remove those links to like kinda give it the freedom, kind of do what you need to do. So, but yeah. We’ll, we’ll release more soon. That’s
Aaron Levie: awesome.
Jeff Huber: That’ll, that’ll be cool.
swyx: We’re a cerebral podcast that people listen to us and, and sort of think really deep. So yeah, we try to keep it subtle.
Okay. We try to keep it.
Aaron Levie: Okay, fine.
Inside Agent Evals
swyx: Um, you, you guys do, you guys do have EVs, you talked about your, your office thing, but, uh, you’ve been also promoting APEX agents and complex work. Uh, yeah, whatever you, wherever you wanna take this just Yeah. How you
Aaron Levie: Apex is, is obviously me, core’s, uh, uh, kind of, um, agent eval.
We, we supported that by sort of. Opening up some data for them around how we kind of see these, um, data workspaces in, in the, you know, kind of regular economy. So how do lawyers have a workspace? How do investment bankers have a workspace? What kind of data goes into those? And so we, [00:32:00] we partner with them on their, their apex eval.
Our own, um, eval is, it’s actually relatively straightforward. We have a, a set of, of documents in a, in a range of industries. We give the agent previously did this as a one shot test of just purely the model. And then we just realized we, we need to, based on where everything’s going, it’s just gotta be more agentic.
So now it’s a bit more of a test of both our harness and the model. And we have a rubric of a set of things that has to get right and we score it. Um, and you’re just seeing, you know, these incredible jumps in almost every single model in its own family of, you know, opus four, um, you know, sonnet four six versus sonnet four five.
swyx: Yeah. We have this up on screen.
Aaron Levie: Okay, cool. So some, you’re seeing it somewhere like. I, I forget the to, it was like 15 point jump, I think on the main, on the overall,
swyx: yes.
Aaron Levie: And it’s just like, you know, these incredible leaps that, that are starting to happen. Um,
swyx: and OP doesn’t know any, like any, it’s completely held out from op.
Aaron Levie: This is not in any, there’s no public data which has, you know, Ben benefits and this is just a private eval that we [00:33:00] do, and then we just happen to show it to, to the world. Hmm. So you can’t, you can’t train against it. And I think it’s just as representative of. It’s obviously reasoning capabilities, what it’s doing at, at, you know, kind of test time, compute capabilities, thinking levels, all like the context rot issues.
So many interesting, you know, kind of, uh, uh, capabilities that are, that are now improving
swyx: one sector that you have. That’s interesting.
Industries and Datasets
swyx: Uh, people are roughly familiar with healthcare and legal, but you have public sector in there.
Aaron Levie: Yeah.
swyx: Uh, what’s that? Like, what, what, what is that?
Aaron Levie: Yeah, and, and we actually test against, I dunno, maybe 10 industries.
We, we end up usually just cutting a few that we think have interesting gains. All extras, won a lot of like government type documents. Um,
swyx: what is that? What is it? Government type documents?
Aaron Levie: Government filings. Like a tax
swyx: return, like
Aaron Levie: a probably not tax returns. It would be more of what would go the government be using, uh, as data.
So, okay. Um, so think about research that, that type of, of, of data sets. And then we have financial services for things like data rooms and what would be in an investment prospectus. Uhhuh,
swyx: that one you can dog food.
Aaron Levie: Yeah, exactly. Exactly. Yes. Yes. [00:34:00] So, uh, so we, we run the models, um, in now, you know, more of an agent mode, but, but still with, with kinda limited capacity and just try and see like on a, like, for like basis, what are the improvements?
And, and again, we just continue to be blown away by. How, how good these models are getting.
swyx: Yeah, I mean, I think every serious AI company needs something like that where like, well, this is the work we do. Here’s our company eval. Yeah. And if you don’t have it, well, you’re not a serious AI company.
Aaron Levie: There’s two dimensions, right?
So there’s, there’s like, how are the models improving? And so which models should you either recommend a customer use, which one should you adopt? But then every single day, we’re making changes to our agents. And you need to know
swyx: if you regressed,
Aaron Levie: if you know. Yeah. You know, I’ve been fully convinced that the whole agent observability and eval space is gonna be a massive space.
Um, super excited for what Braintrust is doing, excited for, you know, Lang Smith, all the things. And I think what you’re going to, I mean, this is like every enter like literally every enterprise right now. It’s like the AI companies are the customers of these tools. Every enterprise will have this. Yeah, you’ll just [00:35:00] have to have an eval.
Of all of your work and like, we’ll, you’ll have an eval of your RFP generation, you’ll have an eval of your sales material creation. You’ll have an eval of your, uh, invoice processing. And, and as you, you know, buy or use new agentic systems, you are gonna need to know like, what’s the quality of your, of your pipeline.
swyx: Yeah.
Aaron Levie: Um, so huge, huge market with agent evals.
swyx: Yeah.
Building the Agent Team
swyx: And, and you know, I’m gonna shout out your, your team a bit, uh, your CTO, Ben, uh, did a great talk with us last year. Awesome. And he’s gonna come back again. Oh, cool. For World’s Fair.
Aaron Levie: Yep.
swyx: Just talk about your team, like brag a little bit. I think I, I think people take these eval numbers in pretty charts for granted, but No, there, I mean, there’s, there’s lots of really smart people at work during all this.
Aaron Levie: Biggest shout out, uh, is we have a, we have a couple folks at Dya, uh, Sidarth, uh, that, that kind of run this. They’re like a, you know, kind of tag tag team duo on our evals, Ben, our CTO, heavily involved Yasha, head of ai, uh, you know, a bunch of folks. And, um, evals is one part of the story. And then just like the full, you know, kind of AI.
An agent team [00:36:00] is, uh, is a, is a pretty, you know, is core to this whole effort. So there’s probably, I don’t know, like maybe a few dozen people that are like the epicenter. And then you just have like layers and layers of, of kind of concentric circles of okay, then there’s a search team that supports them and an infrastructure team that supports them.
And it’s starting to ripple through the entire company. But there’s that kind of core agent team, um, that’s a pretty, pretty close, uh, close knit group.
swyx: The search team is separate from the infra team.
Aaron Levie: I mean, we have like every, every layer of the stack we have to kind of do, except for just pure public cloud.
Um, but um, you know, we, we store, I don’t even know what our public numbers are in, you know, but like, you can just think about it as like a lot of data is, is stored in box. And so we have, and you have every layer of the, of the stack of, you know, how do you manage the data, the file system, the metadata system, the search system, just all of those components.
And then they all are having to understand that now you’ve got this new customer. Which is the agent, and they’ve been building for two types of customers in the past. They’ve been building for users and they’ve been building for like applications. [00:37:00] And now you’ve got this new agent user, and it comes in with a difference of it, of property sometimes, like, hey, maybe sometimes we should do embeddings, an embedding based, you know, kind of search versus, you know, your, your typical semantic search.
Like, it’s just like you have to build the, the capabilities to support all of this. And we’re testing stuff, throwing things away, something doesn’t work and, and not relevant. It’s like just, you know, total chaos. But all of those teams are supporting the agent team that is kind of coming up with its requirements of what, what do we need?
swyx: Yeah. No, uh, we just came from, uh, fireside chat where you did, and you, you talked about how you’re doing this. It’s, it’s kind of like an internal startup. Yeah. Within the broader company. The broader company’s like 3000 people. Yeah. But you know, there’s, there’s a, this is a core team of like, well, here’s the innovation center.
Aaron Levie: Yeah.
swyx: And like that every company kind of is run this way.
Aaron Levie: Yeah. I wanna be sensitive. I don’t call it the innovation center. Yeah. Only because I think everybody has to do innovation. Um, there, there’s a part of the, the, the company that is, is sort of do or die for the agent wave.
swyx: Yeah.
Aaron Levie: And it only happens to be more of my focus simply because it’s existential that [00:38:00] we get it right.
swyx: Yeah.
Aaron Levie: All of the supporting systems are necessary. All of the surrounding adjacent capabilities are necessary. Like the only reason we get to be a platform where you’d run an agent is because we have a security feature or a compliance feature, or a governance feature that, that some team is working on.
But that’s not gonna be the make or break of, of whether we get agents right. Like that already exists and we need to keep innovating there. I don’t know what the right, exact precise number is, but it’s not a thousand people and it’s not 10 people. There’s a number of people that are like the, the kind of like, you know, startup within the company that are the make or break on everything related to AI agents, you know, leveraging our platform and letting you work with your data.
And that’s where I spend a lot of my time, and Ben and Yosh and Diego and Teri, you know, these are just, you know, people that, that, you know, kind of across the team. Are working.
swyx: Yeah. Amazing.
Read Write Agent Workflows
Jeff Huber: How do you, how do you think about, I mean, you talked a lot about like kinda read workflows over your box data. Yep.
Right. You know, gen search questions, queries, et cetera. But like, what about like, write or like authoring workflows?
Aaron Levie: Yes. I’ve [00:39:00] already probably revealed too much actually now that I think about it. So, um, I’ve talked about whatever,
Jeff Huber: whatever you can.
Aaron Levie: Okay. It’s just us. It’s just us. Yeah. Okay. Of course, of course.
So I, I guess I would just, uh, I’ll make it a little bit conceptual, uh, because again, I’ve already, I’ve already said things that are not even ga but, but we’ve, we’ve kinda like danced around it publicly, so I, yeah, yeah. Okay. Just like, hopefully nobody watches this, um, episode. No.
swyx: It’s tidbits for the Heidi engaged to go figure out like what exactly, um, you know, is, is your sort of line of thinking.
Sure. They can connect the dots.
Aaron Levie: Yeah. So, so I would say that, that, uh, we, you know, as a, as a place where you have your enterprise content, there’s a use case where I want to, you know, have an agent read that data and answer questions for me. And then there’s a use case where I want the agent to create something.
And use the file system to create something or store off data that it’s working on, or be able to have, you know, various files that it’s writing to about the work it’s doing. So we do see it as a total read write. The harder problem has so far been the read only because, because again, you have that kind of like 10 [00:40:00] million to one ratio problem, whereas rights are a lot of, that’s just gonna come from the model and, and we just like, we’ll just put it in the file system and kinda use it.
So it’s a little bit of a technically easier problem, but the only part that’s like, not necessarily technically hard, it is just like it’s not yet perfected in the state of the ecosystem is, you know, building a beautiful PowerPoint presentation. It’s still a hard problem for these models. Like, like we still, you know, like, like these formats are just, we’re not built for.
They’re
swyx: working on it.
Aaron Levie: They’re, they’re working on it. Everybody’s working on it.
swyx: Every launch is like, well, we do PowerPoint now.
Aaron Levie: We’re getting, yeah, getting a lot, getting a lot of better each time. But then you’ll do this thing where you’ll ask the update one slide and all of a sudden, like the fonts will be just like a little bit different, you know, on two of the slides, or it moved, you know, some shape over to the left a little bit.
And again, these are the kind of things that, like in code, obviously you could really care about if you really care about, you know, how beautiful is the code, but at the end, user doesn’t notice all those problems and file creation, the end user instantly sees it. You’re [00:41:00] like, ah, like paragraph three, like, you literally just changed the font on me.
Like it’s a totally different font and like midway through the document. Mm-hmm. Those are the kind of things that you run into a lot of in the, in the content creation side. So, mm-hmm. We are gonna have native agents. That do all of those things, they’ll be powered by the leading kind of models and labs.
But the thing that I think is, is probably gonna be a much bigger idea over time is any agent on any system, again, using Box as a file system for its work, and in that kind of scenario, we don’t necessarily care what it’s putting in the file system. It could put its memory files, it could put its, you know, specification, you know, documents.
It could put, you know, whatever its markdown files are, or it could, you know, generate PDFs. It’s just like, it’s a workspace that is, is sort of sandboxed off for its work. People can collaborate into it, it can share with other people. And, and so we, we were thinking a lot about what’s the right, you know, kind of way to, to deliver that at scale.
Docs Graphs and Founder Mode
swyx: I wanted to come into sort of the sort of AI transformation or AI sort of, uh, operations things. [00:42:00] Um, one of the tweets that you, that you wanted to talk about, this is just me going through your tweets, by the way. Oh, okay. I mean, like, this is, you read
Aaron Levie: one by one,
swyx: you’re the, you’re the easiest guest to prep for because you, you already have like, this is the, this is what I’m interested in.
I’m like, okay, well, are
Aaron Levie: we gonna get to like, like February, January or something? Where are we in the, in the timelines? How far back are we going?
swyx: Can you, can you describe boxes? A set of skills? Right? Like that, that’s like, that’s like one of the extremes of like, well if you, you just turn everything into a markdown file.
Yeah. Then your agent can run your company. Uh, like you just have to write, find the right sequence of words to
Aaron Levie: Yes.
swyx: To do it.
Aaron Levie: Sorry, is
that
swyx: the question? So I think the question is like, what if we documented everything? Yes. The way that you exactly said like,
Aaron Levie: yes.
swyx: Um, let’s get all the Fortune five hundreds, uh, prepared for agents.
Yes. And like, you know, everything’s in golden and, and nicely filed away and everything. Yes. What’s missing? Like, what’s left, right? Like
Aaron Levie: Yeah.
swyx: You’ve, you’ve run your company for a decade. Like
Aaron Levie: Yeah. I think the challenge is that, that that information changes a week later. And because something happened in the market for that [00:43:00] customer, or us as a company that now has to go get updated, and so these systems are living and breathing and they have to experience reality and updates to reality, which right now is probably gonna be humans, you know, kinda giving those, giving them the updates.
And, you know, there is this piece about context graphs as as, uh, that kinda went very viral. Yeah. And I, I, I was like a, i, I, I thought it was super provocative. I agreed with many parts of it. I disagree with a few parts around. You know, it’s not gonna be as easy as as just if we just had the agent traces, then we can finally do that work because there’s just like, there’s so much more other stuff that that’s happening that, that we haven’t been able to capture and digitize.
And I think they actually represented that in the piece to be clear. But like there’s just a lot of work, you know, that that has to, you just can’t have only skills files, you know, for your company because it’s just gonna be like, there’s gonna be a lot of other stuff that happens. Yeah. Change over time.
Yeah. Most companies are practically apprenticeships.
swyx: Most companies are practically apprenticeships. Like
Jeff Huber: every new employee who joins the team, [00:44:00] like you span one to three months. Like ramping them up.
Aaron Levie: Yes. All
Jeff Huber: that tat knowledge
Aaron Levie: is
Jeff Huber: not written down.
Aaron Levie: Yes.
Jeff Huber: But like, it would have to be if you wanted to like give it to an Asian.
Right. And so like that seems to me like to be
Aaron Levie: one is I think you’re gonna see again a premium on companies that can document this. Mm-hmm. Much. There’ll be a huge premium on that because, because you know, can you shorten that three month ramp cycle to a two week ramp cycle? That’s an instant productivity gain.
Can you re dramatically reduce rework in the organization because you’ve documented where all the stuff is and where the answers are. Can you make your average employee as good as your 90th percentile employee because you’ve captured the knowledge that’s sort of in the heads of, of those top employees and make that available.
So like you can see some very clear productivity benefits. Mm-hmm. If you had a company culture of making sure you know your information was captured, digitized, put in a format that was agent ready and then made available to agents to work with, and then you just, again, have this reality of like add a 10,000 person [00:45:00] company.
Mapping that to the, you know, access structure of the company is just a hard problem. Is like, is like, yeah, well, you just, not every piece of information that’s digitized can be shared to everybody. And so now you have to organize that in a way that actually works. There was a pretty good piece, um, this, this, uh, this piece called your company as a file is a file system.
I, did you see that one?
swyx: Nope.
Aaron Levie: Uh, yes. You saw it. Yeah. And, and, uh, I actually be curious your thoughts on it. Um, like, like an interesting kind of like, we, we agree with it because, because that’s how we see the world and, uh,
swyx: okay. We, we have it up on screen. Oh,
Aaron Levie: okay. Yeah. But, but it’s all about basically like, you know, we’ve already, we, we, we already organized in this kind of like, you know, permission structure way.
Uh, and, and these are the kind of, you know, natural ways that, that agents can now work with data. So it’s kind of like this, this, you know, kind of interesting metaphor, but I do think companies will have to start to think about how they start to digitize more, more of that data. What was your take?
Jeff Huber: Yeah, I mean, like the company’s probably like an acid compliant file system.
Aaron Levie: Uh,
Jeff Huber: yeah. Which I’m guessing boxes, right? So, yeah. Yes.
swyx: Yeah. [00:46:00]
Jeff Huber: Which you have a great piece on, but,
swyx: uh, yeah. Well, uh, I, I, my, my, my direction is a little bit like, I wanna rewind a little bit to the graph word you said that there, that’s a magic trigger word for us. I always ask what’s your take on knowledge graphs?
Yeah. Uh, ‘cause every, especially at every data database person, I just wanna see what they think. There’s been knowledge graphs, hype cycles, and you’ve seen it all. So.
Aaron Levie: Hmm. I actually am not the expert in knowledge graphs, so, so that you might need to
swyx: research, you don’t need to be an expert. Yeah. I think it’s just like, well, how, how seriously do people take it?
Yeah. Like, is is, is there a lot of potential in the, in the HOVI?
Aaron Levie: Uh, well, can I, can I, uh, understand first if it’s, um, is this a loaded question in the sense of are you super pro, super con, super anti medium? I
swyx: see pro, I see pros and cons. Okay. Uh, but I, I think your opinion should be independent of mine.
Aaron Levie: Yeah. No, no, totally. Yeah. I just want to see what I’m stepping into.
swyx: No, I know. It’s a, and it’s a huge trigger word for a lot of people out Yeah. In our audience. And they’re, they’re trying to figure out why is that? Because why
Aaron Levie: is this such a
swyx: hot item for them? Because a lot of people get graph religion.
And they’re like, everything’s a graph. Of course you have to represent it as a graph. Well, [00:47:00] how do you solve your knowledge? Um, changing over time? Well, it’s a graph.
Aaron Levie: Yeah.
swyx: And, and I think there, there’s that line of work and then there’s, there’s a lot of people who are like, well, you don’t need it. And both are right.
Aaron Levie: Yeah. And what do the people who say you don’t need it, what are they
swyx: arguing for Mark down files. Oh, sure, sure. Simplicity.
Aaron Levie: Yeah.
swyx: Versus it’s, it’s structure versus less structure. Right. That’s, that’s all what it is. I do.
Aaron Levie: I think the tricky thing is, um, is, is again, when this gets met with real humans, they’re just going to their computer.
They’re just working with some people on Slack or teams. They’re just sharing some data through a collaborative file system and Google Docs or Box or whatever. I certainly like the vision of most, most knowledge graph, you know, kind of futuristic kind of ways of thinking about it. Uh, it’s just like, you know, it’s 2026.
We haven’t seen it yet. Kind of play out as as, I mean, I remember. Do you remember the, um, in like, actually I don’t, I don’t even know how old you guys are, but I’ll for, for to show my age. I remember 17 years ago, everybody thought enterprises would just run on [00:48:00] Wikis. Yeah. And, uh, confluence and, and not even, I mean, confluence actually took off for engineering for sure.
Like unquestionably. But like, this was like everything would be in the w. And I think based on our, uh, our, uh, general style of, of, of what we were building, like we were just like, I don’t know, people just like wanna workspace. They’re gonna collaborate with other people.
swyx: Exactly. Yeah. So you were, you were anti-knowledge graph.
Aaron Levie: Not anti, not anti. So
swyx: not non
Aaron Levie: I’m not, I’m not anti. ‘cause I think, I think your search system, I just think these are two systems that probably, but like, I’m, I’m not in any religious war. I don’t want to be in anybody’s YouTube comments on this. There’s not a fight for me.
swyx: We, we love YouTube comments. We’re, we’re, we’re get into comments.
Aaron Levie: Okay. Uh, but like, but I, I, it’s mostly just a virtue of what we built. Yeah. And we just continued down that path. Yeah.
swyx: Yeah.
Aaron Levie: And, um, and that, that was what we pursued. But I’m not, this is not a, you know, kind of, this is not a, uh, it’s
swyx: not existential for you. Great.
Aaron Levie: We’re happy to plug into somebody else’s graph.
We’re happy to feed data into it. We’re happy for [00:49:00] agents to, to talk to multiple systems. Not, not our fight.
swyx: Yeah.
Aaron Levie: But I need your answer. Yeah. Graphs or nerd Snipes is very effective nerd.
swyx: See this is, this is one, one opinion and then I’ve,
Jeff Huber: and I think that the actual graph structure is emergent in the mind of the agent.
Ah, in the same way it is in the mind of the human. And that’s a more powerful graph ‘cause it actually involved over time.
swyx: So don’t tell me how to graph. I’ll, I’ll figure it out myself. Exactly. Okay. All right. And
Jeff Huber: what’s yours?
swyx: I like the, the Wiki approach. Uh, my, I’m actually like, uh, you know, obviously I spent some my time at cognition, which, uh, you, you know very well.
Yep. And they’ve had a lot of success with Deep Wiki. Yeah. It powers a lot of Devrel and brain
Aaron Levie: super powerful.
swyx: And it’s super, it’s useful for humans, but it’s, oh my God, it’s useful for agents.
Aaron Levie: Yes. Tell me if you think I’m, I’m wrong on this, but, but not much of an access control structure issue?
swyx: No.
Aaron Levie: There’s like the whole, you get the whole code base and everybody gets to,
swyx: well, before, before I speak too much, there may be some enterprise controls on Sure.
The enterprise Deb offering that I’m not familiar with. Yeah. But yeah, I don’t, I don’t have any, anything on the public side. But, you know, I, I think like, almost like every agent should have its [00:50:00] own wiki that it’s updating and that’s. Persistent memory and yeah, that is a very weak knowledge graph.
Jeff Huber: Yeah.
swyx: And you, you could strengthen it if you want more structure, but you may not need it.
Jeff Huber: Markdown files, having links and wiki style. Right. Yep. Very effective. Right, Lindy?
Aaron Levie: Yep.
swyx: I like that. As a, as a just general pattern. Um, okay. So, uh, last couple questions. Sure. But feel free to jump on in or, or if you want any rants.
Um, I see you as a very interesting and, and unusual founder where, like, you’ve been in a business and you are, you’re both like, you’re off like of two worlds, like you’re of Silicon Valley, but you’re also of the Fortune five hundreds. And like, I feel like your kind of founder mode is very different from the Brian Chesky founder mode.
And I’m just kinda curious if you have like ref reflections on like how you operate as a founder,
Aaron Levie: what would his founder mode be?
swyx: Don’t delegate.
Aaron Levie: Ah, right. And what, how would you put me,
swyx: you do delegate. Ah,
Aaron Levie: okay. I, I, I, I see the, um, I think that I, I don’t know that Brian and I would be that far removed from each other when you get to the specifics.
swyx: Okay.
Aaron Levie: So there’s a whole bunch that I delegate, [00:51:00] 90%. Of the work that happens at Box is fully, you know, fully delegated. We’ve got great leaders running, running, all that stuff. It’s just too much for my brain to handle. And probably 70% of the work, I’m gonna make up all the numbers here, probably 70% of the work at Box or 70, 80% of the work at Box.
I only need to really look at about 5% of that for like, some high leverage decisions to be involved in, you know, what’s the marketing message that we think is gonna resonate with, with customers. So that’s a little bit of high leverage thing that, that, that we do in marketing. But most of marketing activities I don’t get involved in.
What’s our sales pitch? Maybe I’ll be involved in that a little bit. Or like what’s roughly the investments or push we’re gonna do in certain verticals. You know, that’s about 5% of like the total bandwidth of, you know, this, the, the key areas of sales or go to market. Okay. So like. 70, 80% of the company, I can just do about 5%.[00:52:00]
And then, and then just like operationally, we’ve got great leaders and they’re gonna execute on that, and we collaborate on the 5% anyway. It’s not like I’m just like making up a decision and, and saying to go and do it. Then there’s this part that is like the existential part of the business, which is if we don’t do this right, we’re out of business.
And, uh, by virtue of just being a founder, you get kind of sucked into that part of the work because you can feel it. Like, this is like, like you can just see how the AI tsunami could wipe you out if you make just 2, 3, 4, 5 wrong decisions in this space. Like couple wrong architecture decisions, couple wrong AI feature decisions, couple wrong API platform decisions, and, and you might be out of the game in a year from now and like, you just feel it in your bones.
You, you know, this, uh, like, it’s just like, like, like we feel this all day long in this space given what’s happening. Hmm. And so that, in that area. It’s, you can’t kind of delegate in a classic sense. You still need to make sure you’ve got great leaders and strong hires and people that, that are have high agency.
‘cause [00:53:00] they wanna be able to the own part of the, the strategy and the roadmap or else you can’t hire good people. But, but you know, there’s gonna be a lot of little micro forks in the road that they will compound to determine whether you’ve succeed or fail. And so your kind of founder energy just like automatically draws you into, into those because, because they are the determining decisions of, of your company’s future.
And that’s kind of where I spend my time and I, and you have to kind of, you know, do it in a collaborative way again, because if you are only dictatorial and just, you know, you just won’t, won’t eventually be able to hire the best people. ‘cause they won’t wanna work on that environment. But you also just can’t like.
Abdicate all the responsibility because the risks are, are just simply too high. Like, and so you have to somehow, obviously, add some value. And so the value I add is I’ve seen 20 years of this business, so I, I think I can kind of piece together what I expect the value propositions are gonna be and how customers will react to certain things.
So that’s what I can bring to the table. And then you have this kind of existential fear of, if I get it wrong, it’s all on me anyway. [00:54:00] I don’t get to blame, you know, you know, the engineer that was working on that project, like, it’s all, it’s, it’s, it’s my fault, right? Like at the end of the day, it’ll be my fault if it doesn’t work.
So by virtue of of that liability, uh, responsibility, you just get pulled into needing to make sure like it’s all going a according to, to kind of how you think it needs to end up. I don’t, I don’t know how Brian would answer that, I guess, but like I, I, yeah,
swyx: it’s a long essay. It’s an interesting essay.
People should go and compare and contrast your answer versus his, uh, I do think that, um, systems have a way of letting entropy get to them. Yep. And you, you, if you step away for too long, you need to have a way to like check in and go like, well, do I need to come back in? Or are we good? And people are gonna tell you things are good, but they’re not good.
Yes,
Aaron Levie: yes. A hundred percent.
swyx: Yeah.
Aaron Levie: And that’s actually, I’m, um, I’m a fan of actually process for the, that 70 to 80%.
swyx: Yeah.
Aaron Levie: So that 70 to 80% the process is you’re gonna do a, you know, a quarterly business review and you’re gonna have a brand check-in, and you’re gonna do [00:55:00] those, like, you’re gonna make sure that, that you’re seeing all the, the right episodes of, of what’s changing and, and how, and how it’s kind of, you know, evolving and, and make sure it’s kind of going the right direction.
And then there’s some areas which is like, no, it’s 24 7. Like, like I guarantee after this podcast at 11:00 PM I’ll be doing a Zoom with Ben, uh, and probably some other people. ‘cause we’re gonna be talking about agents and, and new platform features and like, that’s amazing. That’s your just in the cauldron, you know, kind of grinding on, on, on that side.
swyx: Yeah. Yeah. That’s, uh, that’s extremely, um, realistic. Yeah. What is, what it’s like, and I just want to have people hear your perspective on what,
Token FOMO Culture
Aaron Levie: and this is what you like, and this is the, this is this like, um, you read the post about, you know, everybody having agents running on the weekend and, um, and it’s like, uh, you know, you, you just.
I mean, first of all, anybody crazy enough to come to Silicon Valley? Like we don’t bring good news about the sort of like healthiness of our environment right now. Like, like, like you have to,
swyx: and
Aaron Levie: [00:56:00] you have to know what you’re signing up for. But like, like, you know, there, there’s a real issue, which is like, shoot, do I have enough agents running?
And, and
swyx: oh yeah, I made a meme that was like semi viral for me about this. Exactly, yes. That was incredible. That’s,
Aaron Levie: and, and, and that, that
swyx: was, you can’t even enjoy a party these days. Becausecause, you’re working with your tokens.
Aaron Levie: No. You just compute out there that you’re not utilizing,
swyx: what the hell? Like,
so
Aaron Levie: like there’s
swyx: ad I paid for the $200, I’m gonna spend the $200.
Aaron Levie: Yeah.
swyx: Uh, I’m gonna spend $6,000 out of 200 bucks. Yeah, exactly.
Jeff Huber: Exactly.
Aaron Levie: We
Jeff Huber: need to make anthropic very unprofitable. So,
swyx: yeah. Yeah. We’re not doing a good enough job. Cool.
Production Function Secrets
swyx: I have a closing question. If you, unless you,
Jeff Huber: I have a question. I’ve asked this question in private before, but I ask it again, which is, uh, it’s a question that Tyler Cowen asks his guests on his podcast, which is, uh, what is the Aaron Levy production function?
And, uh, uh
swyx: Oh, I love
Jeff Huber: that. I love this question because there’s so a few people that I think are good at both executing. Also like distilling and like, just putting good ideas into the ether. Mm-hmm. You put a lot of good ideas into the ether. And so like what is the air levee production function that allows you you to do that versus others?[00:57:00]
Aaron Levie: How do I get that information? Or
swyx: I, I can give you a, a, a variant. Yeah. Which is what goes into air and levee.
Aaron Levie: Yeah.
swyx: And what goes out and how does it turn inside? Yeah.
Aaron Levie: I’m just trying to think of, ‘cause I mean, you know, there’s some very, I, I just read a lot of Twitter, uh, as well. And so like, I just, and you’ve, you
swyx: spent a lot of effort
Aaron Levie: too.
Jeff Huber: Contrast, you don’t see like, great. Many essays from Brian Chesky every day.
Aaron Levie: Uh,
Jeff Huber: but you
Aaron Levie: do
Jeff Huber: from you.
Aaron Levie: Oh, yeah. And you’re
Jeff Huber: kind of weird in that way, so
Aaron Levie: why? Maybe he’s, he, maybe he’s healthier than me. Actually. We should just like, we should just text him to see if, you know, he’s got a more I think he does
swyx: work out.
Aaron Levie: Yeah. He got bigger
swyx: muscles.
Aaron Levie: That’s the thing. I, I work out less than him and I tweet more than him. So, so that’s the, that’s how we’re balancing things out. I am, um, I mostly, the way I just think about it is, uh, is just, um, you know, there’s, there’s lots of work that’s happening in the business. I am getting to see the, all the problems that we are running into constantly.
And I am trying to, uh, be a little bit of a, create a flywheel between what we’re doing [00:58:00] internally, what, what, what. Then we talk about, uh, getting a feedback loop on that and seeing other people’s, you know, experiences of what they’re doing. Bring that back into the business. And, and so I just see, uh, like my job is as, you know, hopefully being able to kind of connect the dots.
Of, of what’s going on in the world with what’s going on in box. And then I just happened to tweet about that along the way.
swyx: Yeah.
Aaron Levie: Um, because
swyx: it’s all you, there’s no like,
Aaron Levie: yeah.
swyx: Editor,
Aaron Levie: there’s no,
swyx: yeah.
Aaron Levie: Yeah.
swyx: Wow.
Aaron Levie: The, uh, I got, um, there was a funny, uh, uh, my, I, I tried to get an internship in, um, between freshman and sophomore year of this company, and it was a, it was a film, uh, kind of production company in New York.
And, uh, I got the internship and then I emailed my liaison kind of guy who sponsored me for the internship and I said, Hey, I’d like to do a blog of my summer internship. Hmm. Where I blog about, you know, the, the being an intern at a production company in New York and. About like a, I dunno, half a day, a day later, [00:59:00] uh, they emailed me back saying they’ve rescinded the internship.
swyx: No.
Aaron Levie: Um, uh, yeah, because, because I showed a lack of judgment on, you know, professionalism, you know, or whatever. Like, like just even the, the idea that I would ask that question, red flags went up of like, who the f**k is this guy? So anyway, I, I only say that to say that like, like to me, just like, you know, building in public is just like a natural, is a natural thing.
And so I, so I just, you know, go through the day. We, we deal with interesting problems. I tweet about them. I get information back in the process. I, I see your work. I see your work. You know, I see a bunch of folks and, and try and, you know, kind of incorporate that back in the box. My job is to try and connect all these things together and, uh, and make, make it useful.
swyx: And you’re, I mean, you’re the number one spokesperson, right? So you do have to be out there.
Aaron Levie: Yeah, I, but I, I kind of would be doing it whether or not, like it’s, I don’t really think of it as a job requirement as much as like, I just like, I like social media.
Jeff Huber: You’re so good at it.
Aaron Levie: Yeah.
Jeff Huber: It’s so hard to believe.
So like,
Aaron Levie: okay, sorry.
Jeff Huber: Do you get up at 5:00 AM [01:00:00] with coffee? Is that your secret? It’s like, how do you work or do you actually just like, in the back of Waymo’s, like, is, do you do it that way? Like how do you do this?
Aaron Levie: It’s, it’s, no, it’s, it’s, it’s mostly that though. It’s mostly, uh, there’s a, you know, I, I, I have a commute home each night.
I try and see, you know, my kids’ most, most weekdays before I have to hop back online. So there’s like a 20 minute window there.
Jeff Huber: Okay.
Aaron Levie: Where I can kinda like distill the information that’s happened and nice. And be like, ah, is there anything I learned today that would be interesting to throw out there? Or anything that I saw.
And then probably somewhere between like seven 30 and 9:00 PM I finally get a chance to like look through the feed. Mm. And see like, did anything crazy happen in ai? And, um, uh, and then that’s, that will also kind of catalyze, you know, something Yep. As like, that’s the best I can kind of,
swyx: you
Aaron Levie: know, respect.
Yeah. Okay. Thanks.
swyx: Uh, and now I know you, you cut off his 8:00 PM I will try to get AI news out before 8:00 PM so I can help him.
Aaron Levie: Yeah.
swyx: Do, do his thing.
Aaron Levie: Ba basically, if, if I [01:01:00] don’t see it before eight to eight 30, I’m not gonna
swyx: Yeah. It’s, I’m gonna
Aaron Levie: be able to like court tweet or something.
swyx: Yeah,
yeah.
Aaron Levie: Uh, because, uh, because then I’m back on Zoom after that,
Film Roots to Box
swyx: so I wasn’t gonna plan on asking this, but you’ve mentioned, uh, you mentioned the film stuff.
Aaron Levie: Yeah.
swyx: And I know from one of my favorite parts of doing your research on you was that, uh, you got the idea for Box from like, the, the Paramount lot. Yeah. Uh, pushing paper. Uh, are you film guy? You, you’re a big,
Aaron Levie: uh, I, I I, I, I would say I used to be more of a film guy.
swyx: Yeah. What, what’s your, what what, what are your favorites?
If you have, you wanna list off any
Aaron Levie: kind of the classic, uh, wannabe film student classics are, are you
swyx: talking Scorsese?
Aaron Levie: Yeah. Panino, pop Fiction, Magnolia. Requiem for a dream, basically. Like if there was an art house film in the nineties, uh, to early two thousands, that was my genre. Yeah. That got me into like, wow, wouldn’t it be cool to do, you know, you know, film.
And then I, I thought maybe I could connect digital into it. Like, could you, could you do film online? That just seemed too [01:02:00] hard from a licensing standpoint. And then obviously Netflix, you know, kind of existed. Um, so I, I never quite was able to fully connect the dots on these things. But the internship at Paramount, um, was one kind of catalyst for starting box because we were using just traditional enterprise software.
And I was like, wow. It’s like really hard to share data, you know, just like files going back and forth. Um, but the same thing was happening in school as well, and so that all led to, led the box basically.
swyx: Um, well, a 24 is, uh, you know, kind of giving back the sort of resurgence of the independent film, I guess a
Aaron Levie: hundred percent.
swyx: Um, uh, in, in, in, in the face of all the Marvel slop.
Aaron Levie: Uh, you know, I was thinking about this the other day, and a 24 is, you know, uh, certainly the best, uh, EE example I’m sure of, of this today. But, um, you know, they just don’t, you know, you, it’s hard to make a film, uh, like, you know, no country for old men or, um, there will be blood like, like what is that movie today?
swyx: Yeah.
Aaron Levie: Like what is a brand new movie that is just like original? [01:03:00] You just watch it and you’re like, what, what did I just watch? So
swyx: my, my, you know, sixes movie bench is, uh, Forrest Gump.
Aaron Levie: Okay.
swyx: Which iconic in its time.
Aaron Levie: Yep. A hundred percent.
swyx: Never again.
Aaron Levie: Yeah. Yeah. We, we did not make, we don’t know how to make Fors Gump anymore.
Um, they will try it with the sequel
Jeff Huber: though, at some point.
Aaron Levie: For sure. I, I honestly fors
swyx: Gump two in 30
Aaron Levie: years. I’ll be fine with it. No, that Fors Gump has a kid. Like he’s still right. Yeah, he’s still right. Exactly. Um, I think for Gump has a grandkid would be like a good movie. Like what is the grandkid of Forres Gump doing in, uh, in 2026
swyx: goes tropical.
Aaron Levie: Yeah. But, um, yeah, I definitely, let’s, I wanna see good, I wanna see more movies out there.
AI Future of Movies
Aaron Levie: You know, I’m a little bit conflicted on AI and film because,
swyx: oh, that, let’s see that.
Aaron Levie: Well, because I, uh, the world does not need more slop on, on AI entertainment, but I’m kind of like in a mode where I think that AI is, is, is gonna be, you know, generally a pure positive.
Because if I’m a, [01:04:00] if I was me 25 years ago in high school, for sure, I would be making a full production film. That had explosions and car chases and, but then there’d be like people that would show up there. So like I think that ability to, to just, you get to be Spielberg, you know, is, is, you know, completely amazing and, and democratizing.
That is incredible. And I, you know, I’m, I’m concerned about like, how do you make sure that we still get PT Anderson. Along the way and, and can we make sure that those, those guys exist? And then interestingly, I never, and I never saw it, but Darren Aronofsky, I, I believe, has either put out or gonna put out a, an AI film, you know, even some of the best artists are, are, you know, starting to adopt this.
But, um, uh, but yeah, I, I definitely don’t want to, what I don’t wanna do is just be like in this like TikTok feed of just films and it’s just like, oh, this film about the car chase that does this thing. And it says like, we don’t need that. Like, like, [01:05:00] like this should be a form of entertainment and art and let’s use AI to accelerate the production process.
Do the really hard CG work that, that you just, you had to spend way too much money on previously to do the, you know, kind of like, let’s, let’s use it to test out all new kind of plot ideas. Uh, yeah. Previs.
Jeff Huber: Yeah, exactly. Like
Aaron Levie: backgrounds and that’s incredible. Like whatever. Yeah. And all those things are super incredible.
I still like the, it’s very nostalgic, but I still like the idea of like. This is a camera and a person and a person that says, you know, action. Uh, and then, and let’s hopefully like surround AI around that. Yeah. We’ll, but we’ll, we’ll see how that plays out.
swyx: Yeah. I think, you know, so one of the things that stability ai, uh, made an impression on me was like, well, you know, and at least now we can remake Game of Throne Season eight, and I can, you know, uh, like, like it was meant to be not, uh, not rushed.
Yeah.
Aaron Levie: And then you watch, um, well I have a six and a half year old and I, you know, you see a lot of these kid movies and you’re like, yeah, that probably will be ai. I don’t totally know the job math ‘cause I don’t know how many animators there are today. [01:06:00] But I actually think, weirdly, I think we could be producing more high quality, maybe even slightly educational kids entertainment.
And so it’s maybe that’s a positive is like we could just have like more, like you could just have a Pixar for like, you know, things where kids learn stuff. And it used to be these like very, you know, lo-fi uh, you know, kinda lesson things.
swyx: I mean, we had tellies, you know, that so slow.
Aaron Levie: So, so we, we could have way more of that.
And, and maybe every animator that today is making a Pixar film is now, you know, we’re like, we fragment that out and uh, but now they’re responsible for more content and they’ve got AI agents running. So like, so, so I think there’s some optimistic scenarios on the entertainment side is like, there’s a lot of great use cases for being able to do, you know, generative media.
swyx: Yeah. Yeah. Edu edutainment as well.
Media DevRel and Engineering
swyx: I guess one question I is, it’s kind of like a self-serving one and almost like an advice, uh, side of the, the, the, the question, one of the things I just, uh, really enjoyed, uh, researching you was that, uh, Michael Arrington had some influence in the [01:07:00] box journey because he went to his house party.
Aaron Levie: Yes.
swyx: And, and that’s how you got funding.
Aaron Levie: Yes.
swyx: One of latent spaces. That’s a deep cut, right?
Aaron Levie: Yeah. Very deep cut. That’s a oh six deep cut.
swyx: Yeah. Uh, do, I mean, do you want to tell that story? I don’t know if you’ve told it very
Aaron Levie: much. It’s not very much of the story. Yeah. Uh, because I probably just,
swyx: it’s like a random intro, right?
Like,
Aaron Levie: um, well, it was just he used to have house parties. Yeah. Uh, TechCrunch had had these house parties and, and it was, um, probably no different than somebody’s doing a house party in sf Uh, you know, just go, yeah. And you just go and you meet the VCs and founders and like, I’m gonna make up examples, so I don’t want to like, you know, there’d be like Chad Hurley over there pitching his, you know, YouTube to people.
And like, like that’s just like how it worked. And it was just like, wow. Like that was this era where all these new companies were, were emerging. And I met, uh, our first investor, uh, in Silicon Valley at one of these house parties, Emily Melton, who then brought us into D-D-D-F-J-D, that, that became our Series A.
So that was all because of Arrington’s, uh, backyard Party.
swyx: One of my inspirations for late space is to be as helpful, influential, whatever as TechCrunch was. That’s [01:08:00] awesome. In the day.
Aaron Levie: That’s Yeah.
swyx: What would a new TechCrunch today look like? You know, what, what, what, what should I, what should I do? I think there used to be TechCrunch Disrupt.
Yeah. You know, I could do that with my conference, but I haven’t done it yet.
Aaron Levie: Well, I mean, I think,
swyx: um, useful. I don’t know.
Aaron Levie: Uh, well, you know, actually interestingly, I would, I would argue Disrupt came after the period that was the, was that Deep cut period. Okay. So, so I think Di Disrupt, you know, ended up being, you know, you know, catalyzing.
I don’t even, I think Cloud Flare launched It disrupted, yes. Is that the story? Right.
swyx: They were runners up.
Aaron Levie: Okay. Okay. So like, so like, I think anytime. Anytime you can be in a, a launchpad is, is just great because it draws in people that are, that’s what I’m trying to do in that creative moment. And whether it needs to be a contest or, or just like everybody gets like five minutes and you’re fundraising.
I mean, who knows? But, but I mean, for what it’s worth, like, I don’t know, have that much advice. ‘cause I think you, you’re, you’re already doing it effectively. Like I, I just like watched the YouTube videos late at night. Um, uh, from the events. I haven’t [01:09:00] been to one of your events, but like from the, from the camera angles, it looks like everybody’s there trying,
Jeff Huber: trying.
So
Aaron Levie: what’s great is that people are gonna be in the audience as like two random people and they’ll be like, you know, the next, the next big AI company will come from, you know, people coming to a meetup. ‘cause they were like, ah, I came in from Chicago and I’m ah, from, you know. Poland and let’s go do a startup.
Like that’s
swyx: the
Aaron Levie: magic
swyx: of
Aaron Levie: the valley.
swyx: Dix Hy found his co-founder at a IE Oh, and I know of at least one marriage. That’s, that’s, wow,
Aaron Levie: you have marriages
swyx: already. Yeah. Yeah.
Aaron Levie: I
Jeff Huber: don’t,
Aaron Levie: I never heard that about,
swyx: that’s my go, that’s my favorite. KPI.
Aaron Levie: Wow. We have AI marriages at the, at the AI engineer conferences.
These are both
Jeff Huber: humans. To be clear,
swyx: that’s a very good clarification. I like that. You have to check.
Jeff Huber: Yes. That’s a
swyx: very good
Aaron Levie: clarification.
swyx: No, but I, I think you have, you’re, you’re insightful business leader with like, a lot of thoughts on media, so I just figured I would,
Aaron Levie: I mean, media is such an interesting space right now because, because I, you know, with the go direct model, every company is gonna have to be a media company.
You
swyx: are going, you are the og. Go direct.
Aaron Levie: Yeah. But, but, but you know, we [01:10:00] we’re, we’re still like. Like, I think, I think what, what you guys are doing, and I don’t even know all the overlapping relationships, but like I watch your guys’ videos of your events, watch your event videos, but like, it’s clearly like this is the new format, right?
Companies have to become channels to communicate with audiences. Yeah. I think the resurgence, resurgence maybe is a bad word ‘cause it implies it decline, but like, Devrel is hot. Yeah. Like the hottest thing of all time right now. I like if you could produce a fricking factory of Devrel people, like there’s just like unlimited jobs right now on the other end of that.
Yeah.
Jeff Huber: Yeah.
Aaron Levie: Um, ‘cause we’re gonna, everybody needs their services and APIs to be used by agents. And so we have to all find a way to like, like, Hey, look at me. Like, like agent over, oh please come over here agent. And that’s gonna, that’s a content game. Like how do you get the agents to see your stuff
swyx: Yeah.
Aaron Levie: And know your APIs and like, this is like a new world that, that we are in. And uh, it’s gonna be a. It’s, it’s gonna completely be a [01:11:00] digital marketing, you know, kind of world that we’re in.
swyx: Yeah. Uh, for what it’s worth, I’m trying to help by doing little writing bootcamps and basically turn into a Devrel bootcamp.
Um, where, you know, well, it’s a demand and supply problem. There’s, there’s huge demand. Yeah. There’s no supply. Wow. All this increase
Aaron Levie: supply. Why is your no supply?
swyx: The one, the really good ones were for themselves.
Aaron Levie: Uh huh.
swyx: Creator economy screwed, screwed you over.
Aaron Levie: So, so I see so, so Substack and Yes. YouTube payouts.
And that’s, is that
swyx: really making Patreon? Yeah. Like the, the most talented guys are making, you know, millions and just working for themselves while for you,
Aaron Levie: that’s not, we don’t want them to make that much money. Okay.
swyx: We need to be able to hire
Aaron Levie: people.
swyx: I mean, I think, I think like, you know, do do what some companies are doing, you know, I’m not saying it’s my situation exactly, but like give them equity and like Uhhuh it should probably would be worth more, uh, just like sort of helping them out.
Aaron Levie: Well, they are getting Oh, sorry. As full-time employees or not?
swyx: I’m part-time.
Aaron Levie: You need full-time.
swyx: I’m part-time.
Aaron Levie: Yeah. But, but you’re, you’re you n of one, like, we like also people that are full-time.
swyx: Yeah. Yeah. My classic joke or, or like, observation [01:12:00] was like, this was when HubSpot bought, like their, they bought like a newsletter business.
Uh, and then they bought the, my first million, like the, the sort of podcast. Oh, okay. Dharmesh, you must know Dharmesh. Um, so he’s like obsessed with this guy. Okay. So, so my conclusion was like every company must either build or buy a media company. Yes. Right. And until you, unless you realize that. You have to take it that seriously that you are running a media business in your company.
Yes. You will never be good at it.
Aaron Levie: Yes, a hundred percent.
swyx: Yeah.
Aaron Levie: Yeah. No, we’re, we’re very much taking that seriously. But, but still, and yet Devrel, I mean, I gotta do one plug. I don’t all is out. Please, please. We’re hiring a Devrel.
swyx: Yeah.
Like,
Jeff Huber: like please
swyx: no, all engineers here. Like, yeah. Like you’ve made it, like, and I just said every, every agent needs a box.
Like, let’s go, let’s go.
Aaron Levie: Thank you. No, that, that’s the headline. And we are hiring Devrel to make that happen. Uh, but yeah, I think Devrel is like the future job. So we’re all just gonna be doing Devrel in some form.
swyx: Okay. Yeah.
Aaron Levie: I mean, what is FD
swyx: developers are ruling the earth. Yeah.
Jeff Huber: What is FDI don’t know. Um,
Aaron Levie: no, it’s, it’s Devrel.
swyx: Yeah. Okay.
Aaron Levie: No, you just, you’re going to
swyx: a company, isn’t it just like glorify consulting? That’s, that’s the downside.
Aaron Levie: Sure. I mean, I guess nobody can like actually [01:13:00] d you know, fully define this, but, um, uh, but I think it’s, it’s, it’s micro Devrel, like you’re in the company, you’re helping them with the services.
Yeah. You’re doing a little bit extra implementation. Yeah.
swyx: Yeah.
Aaron Levie: Um, but, uh, but yeah, so it’s, uh, I, I think we’re all, you know, the thing that’s gonna happen on the ledger of software is we’re gonna produce far more output of code and thus features per dollar. But on the other end of this, we’re gonna actually end up spending probably just as much on how do you get all of that stuff to the customer, and it’s gonna create a new set of roles that we are all doing, partly because I, either, because there’s so much choice and now you have to kind of fight for attention there, or because this stuff is, is just changing so quickly that you have to technically help your customers.
Along the journey. Yeah, so, so I just think like, I, this is why I, I, I always laugh when, you know, people say you don’t need to be an engineer, don’t do computer science. I actually think like that is like still one of the most protected job categories because [01:14:00] things are only getting more technical. Things are only gonna get harder and anybody in a technical position is in the best position.
Yeah. To get agents deployed, get them built, get them adopted, build the, the, the custom code software to the, for the IT system, all of that.
swyx: So, yeah. Yeah. My, my classic founding story of like why I picked AI engineer as a title and as, as a, as a theme for this podcast as theme for my conference was, um, back in like early 2023, someone al came to me and said like, I’m all in on ai.
What should I do? And I was like, I just looked at her. I was like,
Jeff Huber: God dammit, there’s nothing you can do.
swyx: Like engineers are about to get so much more powerful than you Uhhuh. You don’t even understand.
Aaron Levie: Tell me there’s a good, did she go and then learn?
swyx: No, I didn’t, I didn’t say any of that to her.
Aaron Levie: Oh, oh, I see, I see, I see.
swyx: Okay. Yeah, I’m not, I’m not that honest. Well,
Aaron Levie: I hope, I hope somewhere out there. She, she did, went to some online academy.
swyx: Exactly. Learn to code.
Aaron Levie: Yeah.
swyx: But there, there’s a lot of people, like, there’s a lot of people who believe AI too much, and then they’re like, well, you don’t need to learn to code, so I won’t learn to code.
Yeah. And then there’s, there’s like, there’s a bunch of us who are like, just in that [01:15:00] sweet spot of like, we can code and we can wield AI a thousand times more effectively than you can. Yeah. And like, well, who’s gonna win here? Like
Jeff Huber: I, I think I, this was another, uh, a tweet, but it was like the observation that like, really software engineering for the past 30 years was the primary career track for like technical, high agency people that wanted to have a large outsize impact on the world.
swyx: Yeah.
Jeff Huber: And like, software was a means to, you know, do that Right. Effectively. Um, and so yeah, with ai, is it like that, uh, and, and for AI could eat software engineering or software engineering could eat all their kind of domains of discipline.
Aaron Levie: You, those pr same principles then get applied to every other and then function,
Jeff Huber: right?
Aaron Levie: Yeah, exactly. Yeah. I
Jeff Huber: mean, g team engineering, is that a hundred percent Anything else? Yeah.
Aaron Levie: Well, this is the, you know, uh, anybody who believes that an enterprise, and I’m, I’m, I’m mixed on the, I’m mixed on this is, but if you believe that an enterprise is going to build its own software for all of its problems, then you must be the most long on computer science, you know, as a discipline of all time, because guess what, most of the economy does not have enough engineers to then [01:16:00] maintain all those systems, to update to all those systems, to figure out the, the relationship between the business problem and what the code needs to do to go and actually manage that.
And so, so like that’s, that’s a very pro. Engineering job argument of what the future’s gonna look like. I’m still, again, I go back and forth on like, are you gonna really build all these things versus no prepackaged software, but no matter what, there’s gonna be 10 to a hundred times more code. So I think you can be very long engineering right now as just a, you know, purely on the dimension of, of software’s gonna become increasingly more important once agents are, are, you know, turning everything into software.
swyx: Yeah. All right. Three software guys say software in room. Okay.
Aaron Levie: Not biased at all. Okay.
swyx: But, uh, Aaron, your inspiration. All right. Take you. It’s such a pleasure.
Aaron Levie: All right. Good to be here.


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.latent.space/subscribe

This is a free preview of a paid episode. To hear more, visit www.latent.space

AIE Europe CFP and AIE World’s Fair paper submissions for CAIS peer review are due TODAY - do not delay! Last call ever.
We’re excited to welcome METR for their first LS Pod, hopefully the first of many:
METR are keepers of currently the single most infamous chart in AI:
But every Latent Space reader should be sophisticated enough to know that the details matter and that hype and hyperbole go hand in hand in AI social media, because the millions of impressions that got, by people who don’t understand or care about the nuances, disclaimers, and error bars, far outreaches the 69k views on the corrections by the people who actually made the chart:
There’s a lot of nuance both in making benchmarks (as we discovered with OpenAI on our SWE-Bench Verified podcast) and in extrapolating results from them, especially where exponentials and sigmoids are concerned. METR’s Long Horizons work itself has known biases that the authors have responsibly disclosed, but go far too underappreciated in the pursuit of doomer chart porn.

If you’re interested in a short, sharable TED talk version of this pod, over at AIE CODE we were blessed to feature Joel twice, as a stage talk and with a longer form small workshop with Q&A:
We also make sure cover some of METR’s lesser known work on Threat Evaluation but also Developer Productivity, where 2x friend of the pod and now Zyphra founder Quentin Anthony was the ONLY productive participant!

Finally, if you’re the sort to read these show notes to the end, then you definitely deserve some pictures of Joel shredding the guitar at Love Band Karaoke which we mention at the end:

Full Video Pod

Timestamps
00:00 What METR Means00:39 Podcast Intro With Joel01:39 ME vs TR03:33 Time Horizon Origin Story04:56 Picking Tasks And Biases09:13 Time Horizon Misconceptions11:37 Opus 4.5 And Trendlines14:27 Productivity Studies And Explosions29:50 Compute Slows Progress30:47 Algorithms Need Compute32:45 Industry Spend and Data34:57 Clusters and Shipping Timelines36:44 Prediction Markets for Models38:10 Manifold Alpha Story43:04 Beyond Benchmarks Evals51:39 METR Roadmap and Farewell

Transcript

Swyx joined SAIL! Thank you SAIL Media, Prof. Tom Yeh, 8Lee, Hamid Bagheri, c9n, and many others for tuning into SAIL Live #6 with Nathan Lambert and Sebastian Raschka, PhD. Sharing here for the LS paid subscribers.
We covered:



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.latent.space/subscribe