The Pragmatic Engineer - Building Codex with Tibo Sottiaux

Episode Date: September 9, 2026

Brought to You By:• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.• Entire – Git hosting, rebuilt for the agentic era. Every agent session, prompt  and tool calls: stored in your repo.—Tibo Sottiaux is one of the engineers who created Codex, and today, he heads up the Core Products & Platform org at OpenAI which also includes Codex. He’s also one of the most public faces of Codex due to his frequent – and generous – usage reset announcements, like this one yesterday.In this episode of the Pragmatic Engineer Podcast, Tibo and I discuss how Codex was built and continues to be iterated upon. We explore why the Codex CLI is written in Rust and was released as open source, how the harness and models have evolved, and why Codex supports models from multiple providers.Tibo also shares details about how the OpenAI team uses Codex throughout the software development lifecycle, including code reviews, maintenance, and system rearchitecture. We look into how AI is lowering the cost of changing code – and some interesting side effects of this – the merger of ChatGPT and Codex, and also how Tibo uses the tools in his own work.—Timestamps00:00 Intro07:21 Working at Google12:41 What drew Tibo to OpenAI15:19 The early days of Codex18:20 Why Codex was built in Rust21:15 Why Codex is open source25:50 Codex plays nice with other models: why?32:09 How the harness works36:44 Harness and model improvements41:19 The SDLC behind Codex46:39 Code reviews at Codex52:09 Maintenance and architecture56:43 How AI tools expand what engineers can do1:02:30 The Merge: ChatGPT + Codex1:07:16 How Tibo uses Codex and ChatGPT1:10:44 Advice for engineers who want to work in AI—The Pragmatic Engineer deepdives relevant for this episode:• How Codex is built• How Claude Code is built• How Cursor was built• What is "loop engineering?”• How Uber uses AI for development: inside look• Why Ramp built its own in-house coding agent, Inspect• “I ship code I don’t read”: with Peter Steinberger, the creator of OpenClaw—Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [e-mail]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

Codex is one of the most popular AI coding harnesses today, but how did it all start? Many of you will know today's guest, Tebow, from his generous and pretty frequent Codex usage resets. He was also there when Codex as a product started and has led the broader Codex team since. Today we cover how Codex started and why it was built in rust and made open sorters. How coderies are changing inside the Codex team and Open AI. What it means when maintenance and re-architecting are getting ridiculously cheap, what the merge of Codex into Chan GPT looked like and the many, underappreciated engineering challenges of this project.

If you want to understand how teams inside of Open AI plan, review, and ship software, this episode is for you. This episode is presented by Turbo Buffer, a ridiculously scalable, fast and cheap hybrid search engine built on top of object storage by an engineering team that are really going to like after spending time with them. Turbo Buffer is the tool that companies like Anthropic, Notion, Cognition, and Harvey all used to connect their AI products to massive amounts of unstructured data. When I've talked with engineers who use Turbo Buffer,

the theme that always comes up is reliability and performance at scale. The reasons for this have everything to do with TurboPuffer's architecture. TurboPuffer uses only object storage for state, and MVME SSEs with memory cache for compute. Data and TurboPuffer is organized into namespaces. You can think of a namespace as a database table or a search index or an S3 prefix depending on the world you come from. When a namespace is not being queried, it stays on cheap object storage with no associated compute cost. When a namespace is active, TurboPuffer pulls it up into hot-catching tiers, so queries are very fast.

This design fundamentally makes it effortless to scale to hundreds of millions of namespaces. If you're building a multi-tenant AI product, every user and their agent can have their own dedicated search index without any overhead. And each namespace can hold hundreds of millions of documents without any special configuration. You can scale turbopuffer virtually without limit, and the performance, reliability and operating model all stay the same. If you need to connect AI to lots of data, turbopuffer should be your first choice. Check it out at turbopuffer.com slash pragmatic. Tebow, welcome to the podcast.

So good to have you here. Thank you for having me. It's so good to see you again. It's good to do this last time we did it in person. Now we're doing our video. First, I wanted to ask you, how did you get into tech? When did you first know that you want to work with computers?

It's a good question. It was a long, long time ago. My parents actually decided to move out of Brussels where I was born. And just thought it was great to just buy a small house and refurbish it, but it was in the middle of a village with not much going on. I think there was like roughly 200 people living there. Not many that I felt like I wanted to talk to or couldn't make friends of it. And so I kind of got stuck, this is like very early, like eight years old.

I kind of got stuck as like, you know, computers. And, you know, it's like early days of like the, for me, the internet. And, you know, that was my way to learn about things. And so just the rest that's just like, you know, came from that. Sort of like I owe it to my parents to, you know, have moved into the middle of nowhere. And then, you know, I had no choice but to get interested in computers. Once you, you finished high school, like you went on and went to university, right? it's actually studying it properly.

Yes, I studied mathematics, applied mathematics at university. I went there quite early. And so I graduated earlier as well. I thought for a long time that I would actually not make it and that I would drop out. I had small companies and small consulting business like while I was studying. I was like working for banks. I was working for, I was like, very interested in supply chain and applied mathematics problems.

And I guess sort of like selling that and learning a lot through that. Eventually I ended up in the startup world in Belgium. I did that for a little while and then moved to London. Work initially at Google and then DeepMind and then now moved to be here at OpenEIs. Like this is California. I love the California weather. We can talk about that. It's been very good.

Right after university, you started a, you've founded a startup, right? you had the startup bug in you or the entrepreneur entrepreneur bug? Yeah. So this startup was all about pharmaceutical supply chain, looking at the supply chain for clinical trials and like try to optimize and decide like, hey, you know, should you produce more medicine? Where should you send it? Where should dispatch it?

Like how do you avoid waste? And through that, making clinical trials more efficient. And this was using traditional like non-ML techniques. It's like traditionally more optimization. solving Monte Carlo, simulations, these kinds of things. Stochastic multi-stage optimization problem, really. And we also applied it on steel industry, and we applied it to electrical grid as well in Europe.

It was like anything that sort of had the shape of like an optimization problem we sort of like get interested in. And, you know, to this day, like this company still exists. And I think they do some of the most interesting work still, but it's changing a lot, you know, with modern AI for sure. But it's interesting because you kind of said like, oh yeah, that wasn't ML, it was just a traditional stuff, and then you go into like Monte Carlo

simulation and optimization and this algorithm. I get a sense that you kind of just went deep, right? It was like, okay, like here's a problem space. Like, how can I use mathematics, stuff that I learned, stuff that I didn't learn to just go deeper and deeper. Do I sense that correctly? Yeah, that's why I was obsessed with applied mathematics is just really this idea of you have theoretical mathematics

or you have theoretical science and physics and like there you just, you do it because, there's something to be discovered and something beautiful about it. It's all about patterns and pushing the frontier, but you don't necessarily always know how you're going to apply it. And then there is like the real world, right? It's like, you know, there's all these cool problems that just lie around. And I was like very interested in seeing like, you know,

how can I make the world better? And so like how do I apply like, you know, sophisticated mathematics, you know, to just optimize the world around me? And that was like a lot of the thesis behind that startup. Yeah. And then after a startup, you ended up at Google and first at Google London. It was in 2015, and I remember 2015, Google was a really, really competitive place to get into, like, maybe as competitive as Open AIs today in terms of the industry or terms of prestige. You worked on maps initially, and then you moved over to DeepMind.

Can you talk a little bit what you worked on and then why did you move on from an already really interesting space that you clearly loved, you know, like optimization, logistics and all these things? Yes, I didn't start on Google Maps. I started on a project that was meant to make the web faster and meant to make websites faster, especially on mobile. At the time, you know, Google was saying, so like seeing the transition from desktop to mobile and like more and more traffic going to, like, you know, mobile phones. And so like wanted to get ahead of that.

So funded like a number of, a number of initiatives and projects. I was working on one of them. This was like really, really fun because it was a small, group within actually the ads organization. It was meant to sort of, like, you know, offset the loss for the ad revenue loss because of this shift of traffic to mobile and worked on it for roughly two years. And then it was canceled. And although it was like the most fun I've had on, you know, solving hard technical challenges,

I learned a lot from not having product market fit, not having the right users, not having the right feedback loop, not trusting your product manager when they say the project is going well when in fact it's not going well at all. And then, you know, one day, it's just like this VP flew in from California. And then it was just like, oh, yeah, it's like, you know, we're canceling this project. You know, unfortunately, you only have, you know, hundreds of users. And this is clearly not Google scale. And then it's unbelievable, but people were surprised.

And I think there's a lesson there that I carry with me, of course, is, you know, just always, always question, always go to, like, always, you know, deeply think about the impact that you're having, but also the importance of the overall project that you're contributing. And then I moved into Google Maps. Google Maps was super fun,

worked on reviews. And then after roughly a year, I couldn't ignore, like, deep mind. It was just, it was this special place, headquartered in London. So many great things were happening. This was like really the early days,

you know, with rumblings of things like AlphaGo. And they just seemed to be doing extraordinary things and, you know, just really tackling the very, very hardest problem. that you can tackle. And like, with my background, I was obviously drawn to that. I started there. It's like I worked on a lot of the research infrastructure, research tooling.

This is a theme that I carried on for almost a decade. And it's like, this is very much also the, so like how I approach things is how can I build tooling and products that help make others more efficient and bring a lot of utility to them. Initially, I was doing this for research. And then, like, over time, you know, I got like into thinking about things that I'm much more like more general in general and general way, you know, eventually, like, you know, ending up where I'm now. And a fun story that you recently shared on X as well is how you were part of the team that built this internal Google bot that was, you know, if you want to say similar to chat GPT, but a year before chat GPT.

Can you talk about that? That is a new story. I haven't heard it before. This was part of deep mind. There were like multiple efforts as well. There was like brain as well that was separate at the time. They had their own efforts on large language models. but it was definitely something that was being explored.

It was not the main thrust of deep mind. Mine was very much worried and busy, like thinking about grand challenges and games and, you know, thinking about RL, not in the language sense. And so there was like this group that was pushing on large language models and, you know, thinking about, you know, what if large text corpuses are everything?

What if you just pushed language to its maximum and you just scaled language models. Like, you know, would that be enough to get to general intelligence? That was like a hot debate at the time. And then one group decided to just really push on that. And then it felt really natural, like, you know, as I was building tooling, you know, with others for research,

as like, you know, obviously you're like, what can we do with this model? Like, how do we present it, you know, to the researcher? Like how can they sort of like, you know, debug the inputs, outputs? And eventually you sort of like end up with, you know, like a chat system. So we build that internally. we had a lot of fun. Initially, the models were like, you know, kind of like almost like a little bit absurd, like, you know, not very coherent, not super useful, but it was a lot of fun to sort of like think here with them that caught up like, you know, like wildfires. Like, you know, this application is just sort of like, you know, everyone was kind of like sharing little conversations within deep mind. It felt more than like a research project or like a research, a project for researchers. And so then there was this desire over time to like launch it as an external product. But deep. Deeply. was just like not set up.

You know, there was like the right way to launch products at Google. There was like, you know, the whole machinery of like, you know, how you do that. You know, the whole like, the less production stack. You obviously very, very optimized over the years to do things well,

but also very, very hard as an environment to truly innovate. And then I wanted to ask what made you, you know, look around or maybe you can consider open AI, but I feel you partially answered this question. Just putting myself back into your shoes. Like you're, you know, it's 2024 or 23,

you're inside of Google who are publishing amazing papers, doing really good research. You're doing super fun stuff, right? pushing the limits of what's been done before. It's inside a company where you already moved. For people who are feeling kind of comfortable or good about where they are right now, which I imagine you must have been,

what made you still explore, all right, like what else might be there? Yeah, I was very comfortable. It's a good place. but really I had a desire to meet great people, but also join a mission that I truly believed in and that, you know, I felt like the people were through to the mission and cared deeply about impacting the world in a very,

in a deeply positive way, but also in a direct way, not being like, oh, yeah, it's just like, you know, we just do this work over here. And then it's like, it's the job of someone else to figure out, you know, how to make this useful. It's like, I wanted to join a group where, you know, like, all the parameters were sort of like considered together, where, you know, research and product were, like, really co-designing.

Opening I was just, like, crushing it. At that, Chachabit was, like, you know, taking off. I was like, I met a couple of people from Open AI and then I was like, wait, what, you know, you only have, like, 20 people working on Chachapiti. Like, that is an insanely small number. That must be, like, extremely empowering. Like, you know, how does that work? How do you manage to maintain, you know, a product with that?

level of scale and with that level of autonomy with, you know, only only 20 engineers. And then, you know, I said kind of dug and dug and dug. And it's like, it was just a an amazing group of people, amazing mission, you know, super talented, super driven. And like, it was like, it was like drew me in. And then I joined pre-reasoning efforts immediately like typical opening eye fashions. Like I joined. It was like, oh yeah, you know, like there's this thing going on. Like, you know, we're going to launch reasoning models. Like, you know, it's like some new paradigm. And then, you know, start sprinting on that. And like, you know, like, you know, a month later, like the company launched 01,

011 preview. And that was exhilarating to be part of. I wanted to be part of like a place that moves fast, cares about impact, would be in tune with the world and, you know, just really listen. And sort of like, that's also to me, like, you know, what I've carried with me,

like when building codex, when building products, it's like having a community, listen to the community, just really focus on like a really intense feedback loop. And then building, something that is just like, you know, you just really want to care about it and like, you know, care about the utility of it that it provides to the world.

And then, of course, you start to work pretty quickly on Codex. So you joined in 2024. Can you take us back? What the thinking back there when you joined was about AI or LMs and code. I know there was this ASWE effort back then. We talked about it in the deep dive as well that we did in the Pragmatic Engineer, the Autonomous Software Engineer. A-3.

Yeah, that's what it was pronounced internally. We don't have an ASEB effort anymore. Like, you know, it's codex. But really for me, it was I joined. I started building infrastructure for research. Like a lot of what I did before was large-scale data storage, analysis, and then tools to understand training runs. I did a lot of different things over my years.

But it was always about building four, others and making them faster and just really caring about, you know, fundamentally doing that well. And then through tooling and infrastructure, making new things possible. And so when I joined OpenEI, it was like with the same idea. And then with the re with one preview and like, you know, some of, some of some of the later models, it was very clear that we had to use the models themselves to help us go faster. And so I just really got obsessed with this idea of what were the limitations? How were we going to use those models for research itself. So got together with other folks in research.

We started training models. We started building little agents. Those were truly the precursor to codex. And this was like we were training internal models to be very proficient on the Python code base of Open AI. And then very proficient with, you know, having like good, good taste in architecture, good taste in, you know, like code style.

it was a Python only and then the idea was like we would sort of like use that to build infrastructure very quickly and help researchers code faster as well and then we would move faster and then over time

when you just kind of push that and simplify it to score you're making a lot of you know we found like where you could make a lot of progress very quickly and then learn very quickly and then Greg and Sam are you know people with

immensely supportive and also Greg was very adamant that, you know, we would, we would not just focus on ourselves, but we would also focus on benefiting the world. And so he just sort of encouraged that we would be thinking about this not just as a tool for Open AI itself, but also as something that we would actually make it through a product. And this is when we merged this research effort with this ASEW effort, and we started building one thing. And then that led to a sprint, which was like the initial

cloud codex that we launched, which didn't really have PMF because there was. It was like a little bit too high friction. And then we also launched the Codex CLI, and we continued to push. But it was always this idea of, hey, how do we get models to really help here? You mentioned that first you started to build this model to train on the Python code and actually help build it in for better. But then you made this interesting decision where for Codex, you built it in Rust. And at the time, the model was not on distribution for Rust, right?

It wasn't as good as it was in Python or TypeScript. Why did you make that kind of a decision? Was it kind of like, did you expect that it'll catch up, or you figure that performance is more important? Because it was very counterintuitive. Most of the other harnesses built were actually not built in rust. They were built on distribution on TypeScript or Python or something else. Yes.

From first principles, like very early on, we were thinking about the product interface and the agent as different things. So it was very important. to build the core of the agent in a way that was robust, that was secure as well, that was engineered for efficiency and scale. And having worked through projects over the years that go from, hey, this is a fun thing to like, hey, we need to scale this to the scale of like the largest data center. is the decisions early on are like really turned out to be quite important

as long as you don't sacrifice too much of the velocity. And so it's like it's a tradeoff, but we have very prolific and amazing Rust developers. Our internal models were not bad at Rust. And then you get a lot of validation as well at compile time. It's like, you know, statically verified and all these things. And that is great for agents too. So turns out, you know, it was quite clear that, you know,

Rust as a language would actually be quite good for agents fairly quickly if we decided to put some effort into it. But primarily we were focused on correctness and we were focused on efficiency as well. Interesting. So you're saying it's worth, in your case it was worth thinking ahead of where you want this thing to be. And for example, thing like a language choice, obviously with agents, you can rewrite a bunch of stuff and easier than in the past. But it's still like you can save yourself reworking by putting in the right, I guess, scaffolding or, or, well, the baseline of what you're building on, right? I think we could have been successful if we had written in the TypeScript or, you know, maybe even Python and then it would have fun and then, you know, we would have rewritten

it at some point. But having a very clean separation between the agent itself, which can exist irrespective of the product, it was a very important principle. And if you write everything in the same code base and the same language, just like, inevitably, you're going to be a little bit sloppy and you're going to intertwine things more than you should, and then it's going to prevent further innovation after that. And so that was very important.

And the rest boundary, in a sense, where it's very useful for that. One interesting decision that you made, which is unique across all of the major labs, is having this built-in open source, right? The CLI is open source, the SDK and the apps server are all open source. When and why did you decide that? It's not a given, especially, you know,

there used to be jokes about, open AI having things closed, but this is actually the opposite where like this is open, whereas like some competitors would ship close source harnesses, which again, I think it's very easy to understand why you want something closed source. Why did you want an open source? There was something really cool about the idea of having the code open source because fundamentally what you're billing is you're billing a coding agent. And so we were sort of like thinking about, well, if you have that, you know, you're obviously going to point it at itself and, you know, maybe, you know, you can build a community of, you know, contributors that use it to improve it. And then, you know, you can learn a lot from that. Also, it felt at the time is like, you know, very clear to us that if we were going to be successful, open source itself would change. And the role of code itself would change. And so being part of that community seemed important instead of divorced from it. I think, you know, it's hard to solve problems if you don't sort of like witness. them yourself.

And then the other thing was just, it still feels like early, but it was very early at the time. It felt like we would have some ideas for how to solve things well. And we were co-designing these, you know, with the training and the research. And it's all about expressing, like,

the capabilities of model and like the most flexible and the best way. But also we didn't have all the answers. And sort of being very open about it hey, this is what a good harness looks like. This is how we think about it. We did a couple of very technical, like, deep dives and blockposts, and we talked about it a lot.

And we thought, you know, hey, it's just like, the world is vast out there. Just like, you know, crazy smart people. It's like, you know, we're going to get inspired by other open source project as well. And so let's just make this a level playing field. And so, like, encourage a lot of tinkering and exploration at this stage. Now, this has been now, you know, like a year later, a year and a half later, which is a very long time in right now in this AI timeframe. But looking back or taking the experience, what are the benefits you've seen, the kind of enduring benefits, the enduring teams benefits from being open source?

And just honestly, what are things that are kind of hard about being open source, right? Like, there must be downsides. Like just trying to get an honest take on both sides. Yeah, there are definitely downsides. it comes at a cost, right? The benefits are, it's almost something to build in the open. It's awesome to have a small repo as well. Like whenever we hire someone and they join the Kodix team,

it's like they've seen the repo before. They've looked at PRs. Ombording is done. Yeah, it's done. Yeah, it's like, and onboarding is just like you use Kodex to look at the repo, you know, with you and you ask some questions. But it's like, it's not a secret issue that you can get productive right away. we get a lot of good contributions,

although we get like, you know, a tsunami of like random stuff as well. Obviously, you and everyone else. Right, open source is changing. I think this is one of the examples. That's right. And then to me, and to a lot of the team,

it just brings a lot of energy to just be part of the community and, like, be directly contributing. Not just saying that we care about the community, but actually doing things that, you know, you can see it's costing us effort, right? We don't have to do it. The downsides,

are, you know, it's separate from the rest of our code. So, you know, sometimes we have to draw like artificial boundaries and, you know, work across multiple repos. When we're working on something particularly exciting and, you know, we're building it in the open, then, you know, at times we find that, you know, others copy it, you know, before we have the time to release it. And it's like, it's just a little bit sad.

But also it's like it's part of the game, you know, it's like you're building in the open. And it's like, you know, that's sort like the contract that you signed is like, you know, you can copy it. We have a very permissive license as well. But it does sting a little bit when you're working on something and you're like, you know. And then the third thing is just like everyone else is like, you know, we are overwhelmed with, you know, random contributions and, you know, we have to deal with that additional tax.

But then that pushes us to, you know, also like try and solve for it, right? Which I think is good. And on top of the open source, one thing that surprised me about Codex, and I didn't even know about it until recently, it's not tied. to the OpenAI models. You can use other models with codecs. You know, like putting myself

in a vendor's shoe, it might not be very obvious because, again, all the other vendors I look at when they do a CLI, it's kind of use it with our models. Again, what made you decide to be this permissive

about, you know, using or allowing to use your harness with other models? It felt quite natural. If you are part of this community and building an excellent coding harness is like, why would you couple it to your model? That felt like sort of like quite disappointing to make that decision. So it didn't feel right. And in general, it's like I think, you know, it's like I kind of tried to make decisions that I'm like, yes, you know, it's just like I can just sort of like explain it.

You know, it is correct. It's the same reasoning with, you know, it is open source in the first place. it would have been trivial for anyone to fork it and then add support for another thing, but then you're just encouraging people to just like, you know, go and use that fork and then not suddenly you have overhead. And the only reason you have a fork is because, you know, you wanted to change like 10 lines of code

to add support for like another model provider. That feels very silly. So like, you know, why not just support it in the first place? The other thing is we benefit a lot from like being able to just give optionality. So, you know, it's like, maybe today, you know, you love using opening eye models and, you know, you're super productive with them.

But like tomorrow there's a new model that comes out. You want to try it at. Why force you to go and completely change your setup just to try a new model? And then we benefit from the feedback that we didn't get, which is like, you know, maybe there's something that you liked about that model. Maybe it actually didn't work well. But it's sort of like being nice to our users and to the community. It's like, you know, feels like the right thing to do here.

And then, you know, we also try like other models, right? So, you know, we try them in the same harness and, you know, it's just all good. And then this is also often like this optionality is very important to companies that we work with. Yeah. This is something that, you know, we absolutely lean into. This last point, I think, you know, as any serious company, you want to have optionality and you want to use a tool that gives you that optionality. But I kind of appreciate it because I feel to me like it's kind of honest. Like, look, like, it forces the whole company to beat to compete the best in everywhere.

And the model layer and the harness layer with open source with chooseable models. And it kind of like doesn't allow you to like kick back and say like, all right, we're done. We can hang back for a little bit for now. Yeah, I want us to win users by having, you know, the best models, the most efficient models, the best product. And then, you know, if we do all of these things, it's like, we're going to have a good time. If we sort of like force you to use the product because, you know, this one thing, it's just like, then I don't think. that will attract the very best people to work on this product either. And it's like we're doing our best work here.

We care a lot about the experience. It should feel delightful. It doesn't, irrespective of the model that powers it, it should feel delightful. I love the idea of winning based on merit, not based on knock-in. And this is a perfect time to mention our season sponsor and Tyre who also play by the same rules. Like it or not, Git is becoming a bottleneck for modern agent-heavy software development.

Deves are creating more code with agents. These agents are pushing more code, many devs are running more parallel agents, these are pushing even more code. GitHub is clearly struggling to keep up and has frequent outages. So what's the solution? Entire was founded by GitHub's last CEO Thomas Dumka and he rebuilt Git hosting for the agentic era from scratch. Entire was built to be very fast and to have your repos regionally close to you to reduce latency, allowing for fleets of agents to push in parallel.

Some numbers they published. Entire can handle 418 pushes per second, that's up to 89 times faster than every competitor on the market. When GitHub is down, you can still keep working and you don't even need to migrate from GitHub. You just sign up to Entire and the platform mirrors your repo. And one more neat thing. Have you ever wondered what prompt resulted in this specific code being generated? I find that the prompt and conversation with the agent carries more information than the PR itself, at least for me. Entire captures all the prompt history with your agent right in the their repo easy to check back and has a pretty innovative UI to show all of this.

If you're looking for Git hosting that works even when GitHub is down, head to Entire.I.0-pragmatic, install the CLI and mirror your repo with a click. I've already done it. Oh, and did I mention that it works with any agent and it's open source. I'd also like to mention our season's sponsor Antisys. Tebow talked about how the experience of the software you use should feel delightful. Delightful includes no annoying bugs. But when you're using agents to write your code, how do you avoid shipping bugs? Reviewing every line of code is becoming a challenge with the amount of code that agents generate, which is why antithesis goes well beyond code review.

Anticistuses runs your whole system in a hostile simulation. This simulation includes both targeted testing and fuss testing. By running this simulation, it finds every bug before your users do. And because the simulation is fully deterministic, it doesn't only find bugs, it gives you a perfect reproduction of every issue, which makes it much easier to fix issues. The first thing I thought when I heard about antithesis is that automated bug discovery and fully deterministic testing sounds like science fiction, but it's actually hardcore engineering under the hood. Jane Street, Fly.I.O., and the EtsyD community shape agent-written code

with full confidence because they know it's been verified by Antistesis. To see more case studies and details, head to Antisysys.com slash pragmatic. And with this, let's get back to Tebow and why competition between tools is great. Yeah, and I think as an engineer, like I always see that whenever there's, there's competition as to someone who's using tools. It's always amazing. Like I remember like when Microsoft had with JetBrains, the IDE wars,

and then there's a clouds battling with each other with all the features. And now, of course, we have the harnesses. We have the models. And as a user, it's great because now we have more choice. They just develop faster. I guess our voice gets heard of it better. So it's great to hear.

Speaking of the harness, can you tell me how it works today in the sense of like when I start a co-eastern, task, does it run always on my machine? Does it choose the cloud? Does it use a sandbox? And how do I control this or notice? Or how much should I know about this as an engineer?

Yes. So by default, it runs in, it runs sandboxed. Everything that if there is like a command that should run with additional permissions outside of the sandbox, it will ask. you as a user for permission, but everything, every tool execution happens within the sandbox by default, and it runs entirely on the machine, your local machine. And this has been the case for, you know, more than a year now.

But it is something that is evolving and shifting where, like, you can select to run this in the cloud, which then runs in like a managed VM, where it's the same VM that you get, through chat GPT work. And you can sort of like inspect it, but like it runs in a CADA container. It's like a secure environment. And so if everything runs inside of that VM and it doesn't run on your machine.

And then the only thing that happens in your machine is like your input and then the streaming back of the output. And so that, you know, obviously then is like much nicer on your CPU and your machine and you can scale much, much more. And this is like just a step. It's going to be much more seamless in the future to like, you know, use cloud machines and then, you know, maybe have a combination of like partial execution on your laptop, partial execution on cloud machines. And really the thing that we're thinking about that is very natural is as models just get better and more capable, they can leverage so much more compute and many more resources than.

are available on your local machine. And so it would be a constraint at some point to just limit execution on your local machine. But one thing that is great about it running locally, and I think the reason I love it when it runs locally, of course it's a pain because if I'm doing some work, it's like, you know, I have several agents. It's eating CPU.

If I want to close my laptop, I cannot kind of leave it like hop open, right? When I was in one of the offices of an AI company, I had a lap open and they're like, are you running agents? I'm like, yeah, I have one running because I get it. But the reason I do it because I have my local tools. I have my local Postgres database.

I have my this and that. How are you thinking about the cloud is amazing, but it doesn't have this setup or it's just a pain to set it up? Are you thinking or are you experimenting with making these setups? And I'm kind of reminded of a topic that we talked about pre-A, which is cloud development environments. And like 20, 22, 23, they're hot. And then we talked about AI more. But I think outside of large tech companies, like cloud dev boxes really never took off because there's a very big upfront cost. And then you need to pay like a maintenance cost as well.

And you just, you know, don't benefit from it as like a solo developer or like a small team. With the level of capabilities that we have in agents now is like the setup almost is free. Right. So like this the setup cost and this maintenance cost is like if your agent is capable of doing it, you know, it should just do it for you. So for example, if you're saying like, hey, you know, I have my local SQLite, or I have a local server and MCPs and whatnot. It's like, how hard is it to actually configure exactly the same setup

and keep it in sync on a cloud deckbox? Well, maybe it's not that hard if the model just does it for you. And so I think we're going to see a resurgence of, you know, fully cloud orchestrated machines, which then frees you from your laptop, right? It's like one thing that we've seen a ton of, of success with chat. If you work, it's just available on your mobile.

I start my day just dictating a bunch of tasks into it next to the coffee and it just does it. It has access to my calendar. It has access to my email. It has access to Slack. And it's just so awesome to just be able to walk around and, you know, get stuff done without having to, you know, carry my laptop everywhere. And I think it's the same thing.

Like, you know, we ship like Codex Remote where, you know, execution is like still happening on your laptop. But it would be wonderful if, you know, you didn't have to keep your laptop open. Can you tell me a bit on how, in the past, how did you improve Codex? Because I remember when I first used Codex, this was one of the early versions. You know, like, you could talk to it. It did stuff. But for example, I said, like, all right, make this change.

And it did that change. And I had unit tests and it didn't run it. And then later, a few months later, I don't know exactly when. It just started to run it automatically. Were these things, did you improve the script that run? you know, the instructions, I'm not sure how exactly you call the bootstrapping script or whatever that is. Is it improving the model? As a dev, how can I imagine you making each version better between the harness and then between the model?

And like, what's the connection between the two? Yeah, this is a good question. So the harness, in a sense, is always a little bit ahead of the model. Oh, really? How so? What I mean by that is that you have the model. It's capable of certain things, but then you set it up with like a couple of crutches so that it can actually do the thing to a level of reliability and in a way that is like efficient and also with the behavior that you expect as a user. And sort of like that's the role of the harness. Right.

It's like, you know, provide guardrails like safety, make it more efficient. to make it more like steerable, controllable. And then the harness usually is also responsible for, you know, what we call like the developer message, which is sort of like infected in the context at the start of each turn. And so that affects obviously like the purpose of that is to affect like the behavior of the agent throughout the turn. A lot of what you have is like the result of the harness and the model. initially, like maybe you're like, oh, it doesn't run test.

So, you know, you have to remind it to run tests. And then, you know, we train a battle model that is just, you know, capable of like better reflecting on what is it that you really want when you ask for something. And then, you know, you don't actually have to tell it anymore. So over time, what we see is like the system, the developer message shrinks. And then the harness also shrinks. Inside of the codex team, do you have specific goals? Do you say like, all right, right, right now? the codex as a hardness and model combined is not very good at this, or it's kind of doing silly

mistakes or here, how can I imagine, how as the engineering team, how you're working on the next version of codex? Because the thing that I don't really get as a dev is like, okay, there's a model, which to me is this magical thing, which will get better. Of course, I'm sure you have some feedback channels, but you also have the hardness, which is the tools that you're building. That's probably what the team is responsible for. How do you set even your goals, right? Like in traditional software, you'll be like, we will build this feature and you build that feature because you know how to do it. But it feels a bit more fuzzy to me, this development process. Yeah, it is. And it's why we co-designed, you know, most things. And it's a process where it's a collaboration between research

and the engineering team, like primarily building the core agent harness. It's always a, it's always a question of like, okay, we see today that, you know, we are very good at this, but we're not very good at this and we have a desire to do like another thing because it would be a very cool product feature. And then, you know, we always sort of like look at it. It's like, okay, should this, should this be like a harness change or should this be a model change? And if it's a model change, like how soon can we have it? Can we have it in a month? Can we have it in, you know, three months, six months? And we sort of like work through that. And then depending on, you know, how soon we can just fix it in the model at which level of training, then we might decide to not even do something

in the harness at all and not and just wait for. for the model to solve it. You know, it's agents all the way, right? So we use agents to analyze, like, a lot of the feedback to, like, you know, come up with themes, you know, to just help us have these conversations and decide on priorities. But we analyze it across all of coding. We analyze it across, like, all of, like, you know, the other domains, like finance, comps, marketing, you know, all the things where our users are using these agents nowadays.

And there's, like, you know, subcategories within those. And then we roughly know, like, you know how well we perform. and then we're always pushing the frontier. And there's a thing that is interesting, as we make, you know, as our pre-training model gets better, as we make the overall model better, like the whole thing lifts up. But then there are sometimes things that we pay a little bit more attention to.

You mentioned, you know, we analyzed agents all the way. Can we talk about the software development lifecycle on Codex in the sense of whenever a new engineer joins a team, any team, it's like, okay, how are things done here? And, you know, back pre-AI, it would have been, you join the company like Uber or Google, and they would tell you like, cool, the way it works is we have an idea or the PM has an idea, we make a plan, we get together, we do some estimations, we break up the work, we code the work, we do test, we do code reviews, we release, we do feature

flags, and then, you know, we, we, we're on call. That, you know, that's how it used to be. When someone joins the Codex team, you know, they've clearly been contributing to the open source part, but what do you tell them? How do things get done here? If they're like a total newbie. use them to great people. And then the thing that they hear the most about, like when they have a question is like, have you asked codex? And codex, like,

it's just by default at opening eyes, like plugged into everything. So it has access to Slack. It has access to all the documents, access to all the code. And it still surprises new starters that you can basically ask it anything. And it will very often just like come up with like a really good response. And so the easiest way to understand the state of a project or who's working on something or why decision was made is like critics knows about it all internally.

Wow. And so you just use all of that. We do a lot of work in, you know, for that reason, we do a lot of work in public channels. We open up documents with like, you know, fairly brought permissions. And so that, you know, everyone has access to this information as well. And so that, you know, your agent can go through things and like, you know, reason through things. And then, you know, we have a couple of other things that are just really very helpful for team productivity and team collaboration that we haven't released yet, but are going to come, like, some of it at death day. Although that just sort of like makes you very grounded and in tune with the rest of the team.

And allows you to like, you know, just very, very quickly, like, understand the state of things and produce things yourself. The general recommendation is just like, hey, care about the user, care about the coherence of the product, care about the models and where they're going. If you're doing something and you know, you're building like this 10,000 lines of code crutch to work around the model flaws, that you know, you're probably doing the wrong thing.

So we have a set of principles. But it's just really sort of like a team culture and ethos at this point. And, you know, it's just very much sort of like carries on, you know, when people join, it's just like through the rest of the team, just like, you know,

sort of like teaching the roots. And then when I have an idea, I think it's a good idea. I talk through with Codex. Maybe I talk with it with some of my colleagues. Like here's a cool new feature I'm going to build as my first contribution or first major contribution to Codex. How do I go about that? Obviously, I goaded down with Codex.

I obviously test it and make sure that it works. From there on, what's the process? Do you still have the concept of code review or AI code review of verification, of rolling out, a verifying of stage rolled out? You know, the thing is because Codex itself, it goes out to millions of people. Like I just crossed a big 20 million active user mark. But if it's chat GPT, then it also goes out to even a lot bigger number of people. Yes.

But it's surprisingly like a similar process, whether you ship on Codex or chat GPT, even though chat GPT goes out to like a billion, a billion active users and growing. You can ship a PR, you know, you can make a change and, you know, get a chip like the next day or like even the same day. And it just goes out to a billion users and it's fine. We just really instill a sense of ownership. and care. So people are very empowered to make changes, even large changes.

The general thing that is being asked is like sort of like evidence that it's going to be well received, evidence that is like a worthy addition, evidence that, you know, it's like it is worth maintaining over time, but also like the cost of maintenance is like just really as, you know, gotten done significantly as well.

So we think about these things slightly differently than, you know, say like two years ago or three years ago. The other thing as well is like, you know, we automate as much as possible. So a lot of like the process of like code review and deploys and, you know, catching regressions. It's like, you know, all of that is like pretty much automated. And so like, you know, you get to just focus on just really the idea and, you know, how it's going to help our users. And you care about, you know, the coherence of it all.

And so like the overall power of the agent and making things better. And like we don't, we have a long, long list of things that, you know, we sort of like aspire to do and haven't gotten to yet. And then there's like the sort of like the north star direction. which is a delightful, simple-to-use personal AGI that knows everything about you, like, you know, that it needs to know, has access to the right resources, can take, like, you know, sometimes risky actions on your behalf, but then, you know, you get, like, the push notification and then, you know, you can verify that. And it's like a thing that, you know, you deeply understand as a user.

But also it knows about your schedule. It knows about your goals. It can be proactive. And it should be, like, extremely natural. It should be something that you can control through, like, natural language, your voice, you know, like maybe it should understand, you know, your emotions. Like if it has like a camera feed, it should be the most natural thing on Earth. It's like it should not be like a thing with 10, you know, different buttons and configurations.

It's like AGI should be simple to use. You kind of mentioned just briefly the review, the code review, but I wanted to go back to it. You worked at Google on a product used by, you know, like hundreds of millions, which is Google Maps. And Google is very well known for their culture of very strict code reviews. They have, I think, two layers of code reviews. the language correctness review. And they've taken, I think they've really perfected it across the industry for a long time. And they do believe that it works and they use it.

How do you think that part is changing specifically the human review? Because for a very long time, until maybe a year or two ago, I would have said your code review has all these benefits. Knowledge sharing, the second pair of eyes, removing the bus factor because now someone else understands them when that person is out that they can jump in. Conversations are happening about architecture and not just not just a code. But now there's, you know, there's a lot more code. And what was the value of code review? What in what cases, and so on your team, because you guys are so ahead of this, where do you see humans still being or developers being involved in the review stage of valuable?

And where is it fine? Did you find it fine to hand it off to an agent? Yeah, the role of code review is changing. One of the early projects that I did on Codex was like working with research on developing a code review model that was going to be to a level where it can spot mistakes in logic and reasoning to a degree where it would require humans like, you know, multiple, potentially multiple hours to capture the same level of mistake because it requires like really digging like, you know, three, four levels deep into like the dependencies and like, you know, just. understand that maybe the documentation actually was wrong, and the implementation of like this third-party dependency is different from what you expected. And so therefore, your invariants are not upheld.

And these things, it's just like, you know, unless you're an expert in that library, you wouldn't know. And therefore you have a bug. And so we developed like these code review models and, you know, we release them. And now they're like the same level of like capability and like ability to spot these mistakes by doing like, you know, deep verification or like just part of the mainline models. Like when we benchmark them, it's like they're like super human in code review.

And this is not just true for correctness. This is also true for security, for example, where they're capable of like reasoning across like, you know, very, very complex things. And then, you know, coming up with like, hey, you know, you have a critical security vulnerability here, which is now mandatory across like all of open AI pull requests. Like we block full requests from merging if, you know, we flagged them with like a security issue. And this is like all automatic.

And the role of code review now is like, I think it was always about. correctness. It was always about, you know, ensuring that things worked, but it was also sort of like a little ritual for information exchange and, you know, bringing people on the same page and like, you know, encouraging like a discussion, which ideally would have happened before, but sometimes it just only happens like around the code because once it merged, it just actually runs in production and it's doing stuff. And then you have to maintain it. So there's like this social aspect to it as well. And so I think all of it is changing. Like the correctness, the cybersecurity, the security is like, I think that will be automated. Really what we see and I see,

is there's this sort of really discussion around the intent that takes place around the poll request. It's like, what are you even trying to do? And is that a right thing to attempt to do? I think you can have that discussion outside of the poll request. It doesn't have to be around code. So maybe this helps crystallize the, you know, like where a discussion needs to happen

versus where we did it because maybe we didn't have the type of tool that we have right now. Yeah, I think this is going to change and it was like a forcing function because, you know, you have to have the discussion or like it's good to have that discussion before you merge it and it becomes production code. But I think there are other ways to have these discussions and, you know, design things together and make sure that the intent is good. And then the code doesn't matter as much. And it's interesting because when I think back of all my code reviews, like, of course I have

like memories where like it was great, we, we had a good discussion or I learned something really interesting. But a bunch of times, honestly, it was such a pain in the ass. Like I was trying to get my stuff. You're pinged. Hey. could you remove my code and like, no, right now I'm busy. No, I really need this to unblock me. And then you contact switch. And then I feel it's always been like good and bad, right? So I feel whatever we do, there will be always upsides and downside.

But now they're just moving. So I guess one upside is as an engineer, you might have to not give your attention to just kind of basic stuff that doesn't need your input per se. Yes, it stays time. And progressively, what we're going to see is. also like you have an agreement on, you know, the box and the overall contract of what it's supposed to do. And then, you know, what is inside the box, as long as you have like strict guarantees in terms of resource utilization, data access, security, these kinds of things. It's like, what happens inside the box is, you know, it could be literally anything. It's like,

don't really need to care. And like, really what you need to agree on is like, what does the box actually do and what are the invariants that must be satisfied? And I think that is then worth, you know, having like a really good conversation on, you know, maybe assisted by your favorite agent. But then once you have that and you have that understanding, it's just like changing anything within the box is like, you know, it doesn't require for discussion. And it's like, you know, just really preserves your attention. The cost of maintenance has gone down. You know, maintenance is always such a hot topic whenever we build something inside of all these companies like Google, Uber, even startups like building was the fun part, but then maintenance

was the painful. And that's when we learned like, okay, it was not, we're building it, etc. Inside of Codex and OpenAI, what do you see maintenance becoming cheaper changing in terms of instead of what you're building, what the ambition is, the, I guess, custom tooling, those kind of things.

Maintenance is really like a tax that you pay over time just to keep taking running and it's always been necessary. It will continue to be necessary, but where I think it changes is like a lot of it is just going to be automated. So, you know, it's like, okay, you have this third party dependency

is like you need to upgrade the version. I'm like, oh, it's like, oh, yeah. You can fully automate this, you know. If you have good change log and, you know, and the code is well documented and like, you know, and the model can just like reason through it. It's like, you know, you can just like blast through your code base to it in a couple of hours.

And, you know, previously you would have like sort of punted on it because it's not the most fun thing to do. But it's actually really important for your business. So it's like really important for your project, like, you know, especially for security vulnerabilities. you want to stay up to date, right? You want to apply, you know, all these patches. I think that's just going to be fully automated.

So a large part of like maintenance, it just kind of comes for free, right? And then I think it's awesome to also think about before, like, you know, when you wanted to just completely react, you have to do like a new architecture because you're trying to make space for like a new, you know, different kind of tradeoffs or you have a new understanding of like the workload or you're trying to fit a new feature. and suddenly you realize like your current system is just very limiting

and you need to completely re-architecture it. That was like a really, really costly endeavor, right? So, you know, sometimes like multiple years and I think this is also like super, super accelerated now.

So like the cost of mistakes, you know, I would say like, you know, is going down. But then at the same time, the good old rules, I would say, of software engineer of like, you know, having good abstractions, like really help. Like, you know,

going back to this like having the box with invariance, like, you know, if you sort of like draw the right shape, you're going to be able to change things much more quickly within the box and not affect the rest of the services or the rest of your infrastructure. And I think it's important. It's important to design for very quick iteration and change. I remember when I talk with Peter Steinberger, that was before he joined OpenAI, but about

OpenClaw and how he thinks about it. He told me that he doesn't read the code, but he kept thinking about, I could see that he's holding the architecture in his head and he was telling me how he re-architects a lot and he thinks about how to make it modular, how to, how to make it modular, how to allow 100 contributors to each build their thing without stepping on each other's toes. So I'm hearing what you're saying that this care, this planning, this structuring has become maybe just a lot more important to, which was something back in a day.

It was like the architect or a staff engineer or experienced folks were doing this thing and other engineers around them were kind of building those smaller parts. But it sounds like now all engineers need to be aware of when you're building your software, right, and plan for edge. Yeah, and, and the GPT models are getting better and better at this as well, like, you know, thinking about long-term

maintenance and, like, good architecture, and, like, this is, like, a natural sort of like, next step, right? It's, like, not just about code quality in the sense of, like, oh, is this code clean within this file? But, like, you know, is this, like, is the architecture actually correct to reduce maintenance burden over time and, like, you know, make space for, like, future product

or feature extensions or changes? And just really this act of, like, you know, engineering over time. that's kind of like something that models are starting to become capable of thinking about very well. I think it's just kind of fascinating to understand that the software that we're building is just going through the life cycle much, much faster. Before you had, you know, you were scaling it, you were starting it, you know, maybe as like a small team of, you know, yourself, maybe a couple of engineers. And then you would add engineers like slowly. And then, you know, maybe after a year, you know, it's like if it's very, very successful, you would have 50 engineers on it or like 100 engineers.

on it, you would have time to see it coming. You would have time to see, like, you know, the humans on board. And you said, like, you know, you can think about the documentation, all of that stuff. But now it's just sort of like that explosion of like, you know, suddenly you have like a hundred agents contributing to this thing. It's like, you know, that can happen like, you know, in a weekend. And so, you know, you're just going through it at, you know, major, major speed compared to before.

Okay, but how do you and the folks at Open AI, like, deal with it? Does it not mess with your mind? Like, you know what I mean? in the sense of like, you've been in this business for quite some time now, like decades or well over. And there was a pace that we kind of got used. And obviously, it's now a lot faster. But how do you get your head around the fact that, A, it's faster, B, the stuff that you've

been doing a year ago, right now you're not doing because now the model is good at it? And, you know, like, how do you kind of reconcile that? Because I'm sure there's stuff that you've been really good at related to software that now you can hand off to the agent. Do you not get a little bit of sting? We talk about it stinging for your features to be implemented open source, but it can also sting that I've been really good at, like, I don't know, refactoring or right now it might be architecture,

but maybe the model will be really good at that. And now I'm like, oh, okay, damn. Like, I'm glad, but also like, it would have been nice for me to do that. Yeah, I think there's like a craft aspect to it, which occasionally I still, you know, pull up an editor and, like, write some code. And it's just like, it feels nice. And it's sort of like, I have fond memories of like late nights sitting in, uh, in them and, you know, just like cranking it out, you know, drinking, um, Coke Zero and, uh, yeah, just not

having to think about anything else other than like the problem in front of me. But really, I think it's, um, it's all about being in the flow and solving problems. And what I find is like, you know, folks here and also like, everyone I talk to is just like, adapting very quickly. And I think if you have a mindset where it's all about code is a tool to solve problems, and you can solve so many more problems. It's like before you wanted to benchmark something and you weren't quite sure where you were going to net at, it's like, you can just do it. It's going to take you like no more than 30 seconds, you know, to launch something in the background and, you know, get proper number and be able to do like a better tradeoff. It makes you, it should

make you a better engineer if you just really care about. but the outcome and the system working well. And so what it allows us to do at opening eye, it allows us to run our inference much more efficiently. It allows us to get much more effective compute and deploy that to the world. And so everyone is just very focused on that and solving important problems at the speed

that was not possible before. And I haven't yet encountered someone who's like, oh, that's not good. That's not fun. Do I understand correctly that? It sounds like if you have, ambitious problems, if you have way more problems and what you can solve today or tomorrow or the next week, sounds like this is not really a problem because when you get more efficient somewhere,

you keep going, which is a lot of startups, right? Like startups are always way more ambitious than what they're able to do. We're not out of problems for sure, right? So, and I don't think we'll be for a while. We have a long, long road ahead of us in terms of like mathematical breakthroughs, scientific breakthroughs, you know, making the world a better place, like, just really billing for humans and solving the most important problems that everyone is facing and just doing it in a deeply human way. That's, that's what we're here for. Also, just going back to coding and, like, you know, these late nights, it's like, I think there's like, it's also, like, maybe like a glamorous version of it. It's just like I also had very, a lot of late nights where I was

trying to refactor something. And, you know, it was just like it would be like three hours deep into the refactor and then realize like actually this is a dead end. And I must restart from scratch. And it was like very frustrating. And so it's like there was like there are like these very, very fun times. There's also a time where it's like it doesn't compile and you're just like, why is it's not compiling yet? I'm sure you had the time where you go, you will later.

It's now super late. You need to go to bed because you need to get some sleep. And then you can't really sleep. And you have this thing where like you have some. some task that is halfway and it upsets you. Sometimes I remember dreaming about the code as well. And I guess one thing I don't really have these days when I'm working on my software for my business is I don't really have something that is halfway because I can just tell it, do this and then I can leave it at a state where it's kind of like, you know, done, either finish or it's either working or it's, I have proof that it's failed. But it's interesting because, you know, everything's sped up, right?

Yeah, maybe. Yeah, like I do have, like what a lot of people do and I do myself is like, you know, I have like sometimes like bigger questions that I'm asking myself. Like, and I, you know, from conversations I've had during the day or like I haven't yet, you know, just like had the time to just look into it. And so I, you know, I will send off codex to just like look at it overnight. And then I'm very excited to then wake up and look at the results. And so, you know, it's always like an exciting morning.

Well, I feel there's an arch to doing long running tasks. And of course, you can use the slash goal, which, will go and run. You know, that's also something that was recently out of, like, a few months ago, right? The slash goal command to codex. Yeah. And back to, you know, maybe like the harness is a crutch, right? It's a flash goal was like necessary to allow like, no, to keep the model like on track on like a singular goal for a very long period of time.

And it's like it allows the model to literally run for days or weeks if it's like a really, really hard problem. but with the new generation of models, like what we're seeing is like, you know, you don't need slash goal anymore. You don't need a harness around it. You can just tell the model like, you know, hey, go and work for a week and, you know, it will actually do it.

Speaking of hard problems and the fact that you're not out of them, one of the interesting things that you shipped from the outside, I would say it was, you know, as an engineer, it was moderately interesting, is the what you call the merge, which is codex appeared inside of chat GPT. And the reason I say that as engineers is it kind of moderately interesting

because we've been using codecs. Like, yeah, it's there. You can now open it in the chat GPT app. Great. Like, I just went there and I just immediately went to codex because I don't really use chat GPT in the app per se. But I talk with folks at OpenAI and people in your team. And they were telling me, like,

there was a lot of preparation going on, a lot of engineering challenges. Can you give a sense of how big this project was, what you needed to do? And why was it difficult to pull off? and how did Codex and other tools help you get it done in ways that would have been hard before? Because since you've launched the merge,

the numbers that you keep sharing of how many people use codex, it's going up way faster than before. So I assume there's a big scale problem you've solved here. A lot of things were challenging with the merge is, first of all, completely different stacks. Chatsypt is like fully... managed cloud-based, like, you know, you run everything on our systems. We restore things, like traditional, traditional way of, like, building things,

built for scale, built for efficiency, codex, fully local. And so the merger is just really like, how do you get the same benefits and the same capabilities from this local coding agent and then build a product around it and build it in a way where it can benefit like a much, much broader pool of people, which is just also why all of us joined OpenEI is to benefit this very, very broad population across the world. And so it was like a very exciting journey of like figuring out

like how do we build a cloud version of this that in essence is capable of like very, very much the same things. But it's also built in a way where, you know, we can serve it through like tens and hundreds of millions of, hundreds of millions of users in a way that is still, like, you know, efficient so that we can include it all the way into the plus plan. ChatsypT work is essentially, like, running the full codex harness in a cloud, like, together with, like, a cloud computer.

It's a very powerful machine, actually, like, people have sort of picked up on it and showed, like, you know, what you can do. Like, you know, if you are creative with the prompt that, you know, you can get, you can get, you can get chatyptu to, like, you know, train another model. in there, you know, you're like, wow. There's like pretty wild things.

You know, you can get it to install blender and, you know, do like 3D modeling. It's like very permissive. It has like internet access. It's like a powerful machine. And then Kodix just works on it.

And this is like what we shipped through casually work. So a lot of system challenges. The team did it very quickly. Obviously like Kodick's helped, you know, to make it more efficient, look at and build a lot of the infrastructure.

and then help resolve a lot of the little differences as well that had been occurring between Codex and Chatsubit. Like merging plugins, architecture, you know, merging library. And like really, really working towards a unified system, which is really the goal. It's like you shouldn't feel like, you know, you can do something in codex that you can't do in Chachabit or vice versa. Like what we're trying to build is like one unified product

that gives you access to the same intelligence, but in the way that you want to use it. And so it was very fun as well because Codex throughout the whole journey also acted as a journalist to sort of document all the steps and the debates and the discussions that the teams were having

and it was very animated debate of how we should do it and how we should name the thing and when to introduce it in what way and what to merge into what there were like many different permutations considered and so there's like a very fun journalistic element to it

where we have a full recounting that Codex did over time and yeah, it's just, it's kind of become known as well as like the toggle arc of OpenEI where, you know, we introduced like the work toggle, which there was also a lot of the beta around of like, you know, whether this was like the right thing. And then, you know, it's just like we kind of grew to just really like it. But over time, we're going to merge things further. So it's like we're really headed into this direction of like full unification.

And, you know, we kind of view this as like a temporary state. where, you know, you have, like, you have better and stronger capabilities when you're in work mode. But over time, we're bringing this, you know, all the way through, like, you know, everyone that uses chance to Peech. And how do you personally use codex? Like, what's your, what's your working set up in terms of agents, in terms of tasks, in terms of what you manage with it? And related to this, I asked Peter Stainberger what I should ask about you. And he said, like, you need to ask him, how do you? deal with the fact that you

involve with all these projects. Your calendar is like Tetris, but usually you show up pretty cheerful. My calendar is fine. And it's just, I am capable of doing so many more things nowadays because I have the technology like Kodak's and I actually shifted a lot of my work on mobile

using Tadavit's tree work, where whenever I have something that I want to take note off, I just fire that off. I use dictation a lot. Whenever I have a question, instead of writing it down to look into later or delegating to someone, I just fire it off in charge of your work

and I get a report, it has a whole bunch of custom skills and custom instructions where it's now very, very tailored to produce the kinds of reports and slide decks and code explorations in the style that I can consume effectively. And so every time I'm like between meetings or like, you know,

you'll kind of like see me like, you know, I was just like dictating to my phone. As I said before, it's just like, we do a lot of work in public channels. We have like a lot in Slack. We have a lot in Notion and Google Docs as well. And so there's pretty much like there's no question really that I feel like cannot ask that, you know, codex will be able to sort of like do at least a first path of thinking through. Whether it is like public sentiment on a feature, looking at production logs for, you know, how much usage we have on a certain thing,

making a list of things that we should deprecate because they're not getting traction, understanding what a certain team is up to. It's like any question I have, I can get an answer to, like, you know, within 30 minutes. And so that's how I use it. I use it for everything. It's like my personal agent in like all the ways. And then oftentimes on weekends as well, I do some like code explorations or like I built some prototypes and I have fun, like, sort of like imagining the future of the product in some ways.

And I do that with others on the teams. It's not always the same team. And it's just like in one day I can build things that I sort of like I had it in my system. It's like it's like I woke up one day. I'm just like we should explore what it means to build this. And then I can just sort of express all of that and get like something in front of people in a day so that they can think through it and criticize it and hopefully get inspired by it. It's like by no means, you know, we need to ship it.

But it's more like, okay, I flush it out of my system and then, you know, I go on and like, you know, do other things. So it's just like so, I don't know, it's such a magical time and it's like so empowering. And as closing, what would your advice be for a software engineer slash AI engineer, someone who built software who would want to get the skill set and the experience to have the opportunity to work at a place like the Codex team, like OpenAI or like an AI startup. So, like, you know, just become this really great builder with these tools. Because the question that comes up is often like, should I start with the theory? How important are the basics? Should I just get really good at using the tools? Yeah.

I think there are two things that are important is deep, deep curiosity for how things work and an ability to, like, you know, train yourself to understand things very quickly. And so it's it is the case that things will continue to change, but people that do extraordinarily well at OpenEI are like, you know, people that just sort of like are able to like grok a system quickly and like, you know, also dive into like a new code base and sort of like, you know, make sense of it.

But obviously like all of that is helped with agents nowadays, right? So just like there's so much information that you need to absorb and that, you know, being able to understand and reason through it. And a lot of that is asking good questions, really, about, you know, how do things work and just like going into like the five wise, which I think, you know, you can just kind of keep digging and digging and digging, and you know,

you're learning very, very fast through that. The other thing is being in tune with the community or, you know, the people that you're trying to solve a problem for. It's like, not everything is like solving a direct problem. Sometimes you're solving a problem that will be useful,

you know, to like another group of people in the pursuit of like solving a problem for humans. But just being crisp about the taste or the needs or the requirements and being able to think clearly and like, you know, exercising through this clarity of thought, feels really important to me. Like if you can't explain what you're trying to achieve, if you can't explain your intent,

if you don't have a tie to a community, if you don't have the taste, it's going to be much harder to do great work. Awesome, Tibo. Well, thanks a bunch for this conversation. This was awesome. Thanks for having me. I've always wanted to get together with Tibo,

and I'm glad that we finally made it happen. I appreciated how Tibo talked about not just the upsides of open source, but also the downsides. Most notably, how competitors can copy features you are just working on in the open right now, and then ship it right before release and just how much this stinks. Plus, you get a lot of low-quality contributions

that you still need to somehow deal with. Another interesting one was Tebowl saying how the harness is always a step ahead of the model. From the inside, the codex team see their job as building clutches for the model with the harness, the tools, and the setup instruction. And then the next version of the model will be trained to need fewer of these clutches.

I'll be honest, as a debub, this sounds a little demotivating, that the stuff I build, in the next version of the model, it'll just know and we can get rid of it. Plus, I do suspect that it's not just about building these clutches, but also building tools that models will use, and it's not like the next version of the model will reinvent an MCB protocol or skills or plugins. At least I hope not. I also enjoyed hearing what the merge, merging chat GPS, look like from the inside.

It was merging a previously fully local coding agent, Codex, into a managed cloud-based stack. and doing it efficient enough so that it can be included in Open AI's $20 per month's plan when $20 is not all that much in terms of compute purchase. It was pretty amusing to hear how Kodak itself acted as a journalist

of the whole project as it was present in all the Slack conversations and all the documents and so it could capture all the important debates and decisions. I'm not going to lie, this part felt a little bit of a big brother feel to it where the AI is always watching,

but it could well become the new normal in startups in the future. I have not yet done. decided how I feel about this. And finally, I appreciated Tebow's advice for engineers to succeed, be curious, undersat Simpsons quickly, and be in tune with the group you are building for. It's reassuring to hear from Tebow as well how much the fundamentals still matter. Do check out the show notes below for deep dives on how Codex, ClockCode, and Cursier were built and other related topics. If you like what you heard, please hit a rating on a podcast

player that you're using. It means a lot to me and to the show. Thanks, and I'll see you in the next one.