Wow.

And in five months, we, uh, we've seen the, the clear inflection point for Codex, right? Like, uh, we now have more than 5 million people using it every week, and a lot of the energy at the company has gravitated around Codex.

And I think the cool thing that not many people realize is that obviously engineers at OpenAI are using the models and Codex to build, but everyone else at OpenAI is also using Codex.

Ron, um, uh, any last thing that you wanna finish on? Anything from your keynote that, that I think, um, the, the main thesis or anything about this, uh, AI engineer, would love to hear, like, your thoughts on where we are and where we're going.

I think it's a pretty unique moment, as we shared in the keynote.

I think it's like, uh, we can all reinvent the way we build, the way we work.

I think the vibes at the conference are exceptional.

I think, like, it's very cool that we get to build this community.

I think that's mostly been put to bed now, but there must be still these ongoing, uh, ongoing changes to the developer ecosystem.

ecosystem.Yeah, I mean, what is absolutely certain is that what it means to be a developer is changing, right? Like, when we first started to have tools to simply auto-complete, you know, a line of code in an IDE to, like, doing some more like what we call pair programming maybe like a year or two ago, uh, you know, in an IDE that had, like, more AI to, like, write complex functions of files.

Like, we've moved far beyond that point now, where, like, you're able to, like, not just generate, like, you know, features.

You're able to, like, accomplish massive, ambitious goal.

Sometimes it's just, like, one prompt.

So in that new world, I think what's very exciting to me is that, like, you can really take all of the toil away from what it means to be an engineer or a developer, right? Honestly, no developer I know loves migrating code, loves, like, you know, fixing bugs or, or, or loves, like, uh, you know, uh, organizing their, like, standups and things like this.

These are all the things that Codex can actually take off of your plate so you can spend most of your time then to think about, like, "What are my customers, like, excited about? Like, what kind of creative ideas should I be working on? Should I try some experiment? What kind of features should I bring up in the roadmap?" Right? Like, what are the things that are exciting to ship that I could ship actually faster than I thought? This is all very exciting.

How can you best leverage them?

So Responses API, I think the sort of primary concern that people have, and something I think I voiced to you guys when, when I was, uh, talking with you in the, in the planning process, was is chat completions going away? Uh, so I just wanted to let it, uh, let you guys respond to the concerns that people might have.

Chat completion is definitely, like, here to stay.

You know, it's a bare metal API we've had for quite some time.

Uh, lots of tools built, uh, around it, uh, so we wanna make sure that, uh, it's maintained and people can confidently keep on building on it.

At the same time, it was kind of optimized for a different world, right? It was optimized for a pre-multimodality world.

We also optimized for kinda single turn, uh, text-to-prompt, uh, text prompt in, text, uh, response out.

And now with these agentic, um, workflows, we, we notice that, like, developers and companies wanna build, um, longer horizon tasks, you know, like things that require multiple turns to get the task accomplished, and computer use is one of those, for instance.

So just like, you know, adding lots of core features and making it more usable, but still centered around like handoffs as like the main, main concept.