Okay, we're here in the studio with Akshay from OpenAI.
Welcome.
Thank you.
And with our trusty co-host Vibhu.
So you recently launched ChatGPT Work.
You lead core product engineering.
You know, it's been a long journey into all this.
I find it very interesting that you started with no code or low code with Walrus and Airtable.
And to some extent, ChatGPT work is kind of like the super app of super apps of, well, here is the ultimate no code.
You just write a prompt.
Yeah.
Yeah.
It's it's it's funny how things come like full circle.
I mean, I think for a long time, my career, I mean, I started my career working consumer fintech.
But then after that, like there's this hypothesis that, you know, the things that we were able to do with code, like as engineers, like if we could bring that to many more people in a more accessible way, then that would be truly magical.
We were working on a startup, it's actually funny, like before LLMs, before Vision LLMs on how to do automated testing with AI.
And it was just kind of jank back then, but, you know, doing what we can.
And then worked at Airtable for a while on, you know, the same thesis that like, if we can bring a database or the primitives behind a database to people, that'd be really awesome.
Useful to them
But once I think LLMs came onto the scene it became clear that like this was like the missing piece like the missing technology required to like bring the magic of code to everyone without them having to know what's going on underneath the hood
And so like I think this launch and you know a lot of the stuff that we've been up to is like the manifestation of that
How was stuff when you joined?
So you joined OpenAI 2023.
Now we've got, you know, so much more stuff.
So ChatGPT, CodexApp, ChatGPT for Work.
Have things changed?
Actually, I think the more interesting thing is how things haven't changed.
Like, I guess, like, one...
I joined, I remember when I joined, it was like 500 people.
One thing I was worried about was like, I was looking for something, you know, more early stage and like, was it going to feel startup enough?
And I joined and I was like, this feels even more startup-y than I could ever imagine.
And like, that really hasn't changed even until now.
I mean, I think the like level of like bottoms up ambition and like
The ability of anyone to like, you know, do anything or have an idea and ship it is really cool.
But on the like sort of mission side, I think what was really compelling to me is this mission of, you know, bringing frontier intelligence to everyone, like building AGI and then bringing it to everyone.
And, um,
I think acknowledging back then that like that vision is going to, you know, not be a linear progression.
Like we're probably going to like try different products and have different things that succeed and don't.
But the vision has stayed the same and the mission has stayed the same.
And we're starting to see the pieces fall together.
And that's really cool.
You worked on Enterprise.
A lot of people never touch ChatGPT for Enterprise, God.
What is something that you learned from there that you're bringing into your work now?
I think how...
There's no, like, one-size-fits-all solution in enterprise.
I remember in the early days of ChatGPT Enterprise, like, we would talk to customers and, like, everyone, that was, like, when, I think it was a year after ChatGPT was released, and everyone was so excited to bring, you know, AI into their enterprise.
And, like, there's all these teams that were being stood up as, like, you know, the AI deployment team, these enormous budgets.
And if you asked anyone, like, what were they excited about?
Like, what were they excited about solving?
Like, at first, you'd get, like, you know, kind of like the baseline answers of, like, we have all these contacts and data and all this stuff.
But if you ask them, like, you know, what was, like, a discrete use case that, like, they want AI to enable in their workplace, you get...
Such a different like variants like explosion of different types of answers.
And it's interesting, like, you know, you using these models and these products, you have this box and you can say anything to it.
Which is the magic.
But on the flip side, it also means that you don't know what to do with it.
And in enterprise, I think a big part of that is actually meeting the users where they are, what use cases are they trying to solve, and then actually teaching them how they can use AI to gain leverage there.
Do you meaningfully differentiate that from forward-deployed engineering?
I think there's, like, the, like, go-to-market side of it, and then there's, like, the product side of it, I think.
You need to see more on the product side, yeah.
And I think, like, however good we get at...
FD motion.
Like I think at the end of the day, if we have a user who's like looking at their computer or looking at their phone, like it's our job in the product to like be enabling them and showing them where to go.
So really excited about that.
Do you think there's been changes, you know, over the past three years of adoption?
So there've been, you know, step function changes, you have reasoning models and whatnot.
Is there still the same problems of enterprise has black box to know what to do with it or how things changed?
I mean, we're seeing now that, like, there's this huge uptake, right?
Everyone's extremely excited about it.
It feels like, you know, millions, hundreds of millions of people are using ChatGPT.
They understand, like, how generally to work with AI.
But then, like, every time, like, a new capability gets unlocked.
So now, like, we're seeing with agents, like...
There is probably a contingent of like early adopters still who, you know, truly get it.
We're like, you know, you can do anything.
You just have to make sure the right context is there.
It's connected to the right tools and then that you're supervising it.
But like anything is possible.
But then there's like this like 10x or 100x bigger market or like they don't
Yet get that or they don't yet see that.
And so I think that's the next stage here.
So I guess to answer your question, I think the adoption is there and growing fast, but I think the opportunity is far, far bigger than that.
That's where we want to play, especially with Chachuiti work.
Yeah.
Well, let's skip ahead to Chachapiti work.
Only like a month ago or so announced.
What was the sort of decision process that led into it?
You know, there was this overall merging of the super app.
Is that what we're officially calling it?
You deprecated the browser as well.
Just, I guess, summarize your last thoughts.
Couple of months of working on this thing.
Yeah, it feels like forever now, but I guess it's only been a few months.
I think maybe the one impetus that is most salient is when we released Codex or even internally added Codex.
Like, it was really surprising to us.
I think we recently put out some stats on this, that there's this like real inflection of like adoption among non-developers at OpenAI.
And I, you know, through this product development process, like would go to like these UXR sessions to talk to people internally.
And the thing that stuck out to me is like, one, like, you know, you go talk to like,
Strategic finance or marketing or whatever, and they're all using Codex for their use cases.
That part's cool, but the thing that really stuck out to me is how proud people were that they were using Codex.
Like, how, like...
It's like, I'm not supposed to be using it, but I am.
It was that.
It was like that they were, you know, early to this, like, new thing.
But it was also this thing of, like, they felt like they had a superpower, right?
And what we recognized then is that, like...
The power of Codex, the power of agents, like, we already have this massive distribution base of people who have, you know, come to know and love ChatGPT.
Like, how do we show that to them?
Like, how do we bring it to them?
Which is like a hard product problem and it's like a tricky thing, right?
There's many ways you can go about it.
And so,
That's what we called the merge and the super app over time and ultimately launched in chat to video workers.
How do we do that?
But it came from that initial realization that like the power was not only for developers, like much, much earlier than probably even we thought, like it can be extended to everyone.
How do you see the products differently?
So like, who is it for, right?
So Codex started out even CLI, then app.
Now there's a merge of ChatGPT, Codex and ChatGPT work.
So is it the opening for the average user, for enterprise, for work?
How do you position it?
I think we want to get to position it for if you're doing work-y related things, for lack of a better word.
I think productivity is, like, it's actually what, like, the pillar that I support.
Like, that's the name of the team.
And the reason for that, the reason we call it productivity and not, like, you know, enterprise or, like, work or something like that is because there's also personal productivity, right?
And, like, I think Chajabiji work is...
I've seen people do things in their personal lives that you wouldn't classify as, like, work technically, but, like, these agents are, you know, super capable for.
Like, one recent example that someone posted about on our Slack is, like, someone has, like, a missed package.
Like, they didn't receive it.
And then they got, like, the picture of it, you know, from Amazon or wherever the courier was.
And they, like, asked how GPD worked to, like, find it.
Find out where that package is.
And, like, the agent, you know, is extremely tenacious and, like, took the image and, like, looked at a bunch of, like, listings around their neighborhood and figured out exactly the apartment complex in which the package was
That gave them some information.
And so, like, I think there's all these things that, like, you, you know,
Worky or productivity related things
I think that's what we want the product to be
You asked about Codex
I think we think Codex is you know a durable brand
But we have a principle that like the user you know we don't want a user to get stuck in a tab or an experience where they don't get the power of the product
And so like basically everything that you can do, you know, in the codex portion of the product on desktop, you can do and chat with your work and vice versa.
But we made some opinionated product decisions on like, you know, how much of
The Git state, if you're in a Git repo, do we want to expose to the end user?
Or how much do we want to make the experience of seeing the agents thinking like diff forward so that you get exposed to the diff side of the box?
And then like on the safety side, like how do we want to think about like sandboxing and making sure that we have the right defaults in one state versus the other?
So there's like some opinions that go behind that, but we do want...
We don't want the user to need to choose which experience they're in.
That is a good goal for AGI, right?
People don't want to choose what version of AGI they want.
They just want the AGI to decide for them.
Can I get an answer?
It's not super clear to me.
Is the Codex harness and the ChatGPT work harness the same?
Is it just UI affordances or are there actually prompt level or even deeper differences?
So the harness is the same.
The harness is shared.
In both of the products, we made improvements to the harness to make it good for knowledge work, especially as it relates to plugins or computer use or artifacts.
You get that power regardless of what your experience you're in.
On the UX side, there's opinionated takes that we have when you're in codex mode, how the UX should behave and some stuff around the sandbox, like I mentioned, but the underlying harness of capabilities should be the same.
I think I'm just kind of curious, maybe we can, is there a query that we can run that would look different in the two modes?
Yeah, I try to create, like, ask it to create, like, a retirement calculator spreadsheet or something in both modes.
And in codex mode, you might have to be in a repo for this, but you'll see, like, the diffs of, like, the sheet that it's creating and stuff like that and the file edits.
But in work, you won't be able to see that.
I think that's super clear.
And then also the other thing I wanted to dive into was the productivity team.
What else is there?
First of all, what are the top level teams other than productivity?
Isn't productivity everything?
So, you know, we have a team focused on ChatGBT, like the core chat experience for consumer, which is like, you know, not, I think,
All productivity, like there's, people are using ChatGPT every day for search to, you know, figure out how to write messages to loved ones, to think about how to like learn a new topic, et cetera.
And so there's so much more inside to create images.
There's so much more in chat that, you know, the hundreds of millions of users are using that,
Obviously, that warrants a very dedicated effort.
And there's teams focused on enterprise and infrastructure and API and stuff like that as well.
I will bring it up.
Yeah, so I have them both running.
This is work.
There's a Codex version here.
I picked 5.6 Sol, so this will take a while.
I think we'll just keep it in the background and, you know, as they finish, we'll look into some of the differences.
Yeah, but immediately, I think if you flip back to the Codex version, you'll see that...
It assumes Git.
Exactly.
Like dynamic island assumes that you're in a Git repo.
And you might miss some stuff because some of it is like in the actual chain of thought with those changes and how we display it up.
Is there an unintuitive, like, is there a thing that you wanted to ship and then you got feedback and you're like, no, let's not do it.
Like, what's the thinking behind that?
I think one direction we could have gone with this is like keeping the experiences like completely separate.
So it's like why...
Different apps.
Exactly.
Like different apps or even in the same app, like different, completely different experiences.
Like why merge it all?
Like what is, you know, Codex obviously people love.
Like why bring these products together?
And I think the intuition here is that like...
All of our jobs are, like, changing dramatically with AI.
Like, every few months, like, I feel like I wake up and I'm, like, doing a completely different thing than I was doing a few months ago.
And my hypothesis here is that... Or I should say our hypothesis is that, like...
Part of what we're building in this technology is giving people leverage, like, you know, the things, maybe it's the more mundane parts of your job or parts that like, if you were able to automate, you'd be able to share more ideas faster or whatever, like you're able to do now.
And because of that, like that might actually blur the lines between someone who's like only writing code or creating strategy docs or, you know,
Planning events or um helping with marketing or doing podcasts or whatever right and so like these things are going to get blurred over time and so like trying to draw a hard boundary based on like the who you are is it's going to be it's going to be tough and like we should enable users to choose but we shouldn't box them in and so
A lot of the work that went in here, like, you know, keeping the primitives the same, like for example, plugins are like unified across this product and ChatGPT in the cloud was because of that.
It's this thesis that like eventually things are going to come together and we don't want to be, like we want to be prescriptive about when to be in either experience, but we don't want to box anyone in.
I wonder if there's users who are very tuned to the old ChatGPT harness that is effectively now replaced by the Codex harness.
I can't imagine what that was, but maybe they're more the more conversational side.
Can you compare and contrast the two harnesses?
Because only you've seen it.
Yeah, I mean, I think ChatGPT, the existing harness, still exists today.
It exists in this app.
The classic, right?
You just start a new chat and you don't go under work, right?
Yeah, if you start a new chat and go to chat, then you're talking to ChatGPT.
Maybe we can technically do another.
I guess, you know, on Instance.
Yeah, so this one's not going to code.
Or it's going to be inline.
It's not in a sandbox.
We try to push you to go to work if you're creating a spreadsheet.
This is a router decision.
Sorry?
It's a router decision.
This is the decision that, you know, the model is making and then like, you know, it sees that you're able to, or you're trying to do something that would be better served in work mode.
But I think your question was like, what are the advantages of like the, the chat,
Like ChatGPT, ChatHarness?
It's more broadly like I want to basically do an oral history of harness engineering.
Right?
You know, the ChatGPT harness lasted us from, let's call it the 01 era until now.
And now it's being replaced by the Codex harness, effectively.
And they're overlapping somewhat.
But I'm curious what changed.
If, you know...
If there is.
My perspective on this is like there's sort of like a constant process of like divergence, convergence, divergence, convergence.
And in chat, like...
Many of the use cases I was talking about before, like, you know, search or learning,
I think we're really optimizing for latency and optimizing for personality and, like, different things that over time, like, the product, the reason people love ChatGPT is because we've been optimizing for those things and working on them for so long.
Codex, what we learned was that, like,
If you give the agent access to this infinitely flexible environment as a computer, you can do really, really powerful things.
And so when we think about, like, okay, well, for knowledge work, like, what is...
Which mode should we choose,
It felt more natural to us to bring that to this computer environment and maybe abstract some of the details of this computer away from users who might not be used to that, but give them that same power.
But ultimately, I think that we want the power in all places, right?
We want to meet people where they are.
So I'm sure there'll be work down the road.
In order to get things to be equivalently capable in all scenarios.
But it's just a question of what we've been focusing on the product on historically and what we're focusing on now.
I think alongside that, outside of just Harness and when to use Codex, ChatGPT or Work, there's also the new models you've released, right?
Any guidance there?
So people love to min-max what to use, like only use Terra on high reasoning versus for this, you know, you want to use Sol here.
There's 32 options.
Yeah, yeah, yeah.
But that being said, you know, for people that are expanding, so productivity, trying stuff for work that don't have the breakdown of what all this is, what's the advice, right?
Well, I mean, I think before the advice, like the first thing is like none of this would be possible without these models.
Like I think you asked earlier, like, you know, what was like the inspiration?
Yeah.
For work.
And early on, I mentioned what we were seeing with Codex, but that was also because the models were getting infinitely more capable.
That's happening again.
I think it's another step function jump now.
And to answer the question on advice, we want this default
To be the best possible, like we want to be opinionated about the default.
And so we've chosen a default that we think is going to be the best for everyone.
And, you know, we have for power users options under the hood.
One could argue that there might be too many right now, and we're working on simplifying it.
But you can extend the reasoning level, and you can change between the different model classes if you need to.
But the default should be the best for most use cases.
So my advice to most people would be to stick to that.
And then if you reach a situation in which you think that you could...
You want to try a different configuration, if you're not seeing either the efficiency on the cost side or the quality on the intelligence side, then you can change the defaults and see if you can get something better.
But we think that the default should be good enough.
I'm just going to run something by you since you have way more experience than me.
I've recently been doing soul light, but with goal.
With the idea that the goal basically augments the reasoning effort, but with more terminations and turns.
Is that a good way to think about it?
As opposed to so ultra or so, you know, extra high.
Yeah.
It's hard to say because it's like an interaction.
Exactly.
It's like there's a preference on, you know, for you as an individual, like how do you like to collaborate with the models?
Like how many of those like terminations, as you call them, do you want where, you know, you can steer or make sure that it's doing the right thing?
I think...
Generally people should try whatever works for them.
I think that using ultra or the multi-agent setups are best for when you have tasks that are either incredibly complicated
Like open expirations or very parallelizable.
I think even for tasks, using goal I think is best for tasks that you know that you'll be able to make consistent progress in a way that's verifiable over time.
But I think for most tasks, they actually don't fall into either of those buckets.
And so like...
At least when they're starting.
And so that's why I think the best first step is like trying it with the default configuration and then seeing like where you want to go from there.
Right.
You guys worked on a slider, which actually is super helpful for reducing the amount of panic.
Yeah.
It's nice on mobile at least.
There's a nice slider.
It's nice here.
I haven't tried it.
So you have the advanced view there, but if you click advanced view, yeah.
Just a simple slider, yeah.
Very pretty, very colorful.
Yeah, the idea was here was to, like, reduce it to, like, one dimension, even though there's multiple dimensions, right?
Try to project it onto a single dimension for the user.
Yeah.
Like, you know, something from, that represents, like, you know, speed and efficiency on one side.
Yeah.
And then, like, sort of, like, quality and thoroughness on the other side.
I am just puzzled that it uses Sol so much.
Like, the lower... No, no, I think the slider, if I'm not mistaken... Terra.
Oh, it is.
So they preset Terra to only be the light one.
But like, I think a lot of people actually, more people should use Terra.
One, because soul keeps running out of capacity.
I'm the reason, you know, here's 10 minutes of our retirement calculator.
Oh, that's the Excel thing.
This is work and then Codex is still cooking.
So we'll get back into it.
I think it'll be interesting to actually see the thought process, the reasoning.
And also, you know, I guess this is eight minutes on work.
Codex is still cooking.
Yeah, and by the way, do you know Gabriel Chua?
He's part of the OpenAI Singapore team.
He showed me this and I was like pretty shocked that this looks like Excel.
It edits Excel files.
You never paid an Excel license, right?
But somehow this is like kind of workable and it's agentic Excel.
Yeah, I mean, one of the big pushes that we made for this launch was artifacts.
Both on the model side, I think if you compare this with 5.5 and 5.4 before that, you'll see that there's been pretty dramatic improvements in the quality of these artifacts.
And then also on the product side.
The UX side is also crazy, like hosted sites and whatnot, no longer needing to host your own little webpage.
Oh, I have a story about that.
I can do a separate thing.
I'll need to take the visuals here, but we'll cut to that later.
Was there co-training, I guess, because you were making this big move and you launched 5.6 on the same day as ChatGipsD work, was there influence between the model training teams and the harness teams or did the launch days just happen to line up on the same day?
I think that, you know, we collaborate heavily with the research teams.
And I mean, I think that's like one of the most magical parts of the job, like the most fun parts of the job.
But yeah, I mean, just using Artifact as an example, like,
You know, a lot of what you're seeing like underneath the hood, there's a lot of work that went into making sure that like, you know, we had the right infra to be able to train the models to get better at this.
And then on the product side, like had the right experience for users to be able to collaborate with the model on an artifact like this.
In fact, like this whole viewer, like the intuition here is that like,
You know, it's not necessarily that you wouldn't need an Excel license.
This is stage one, right?
Like this is probably not what you meant when you're like making a retirement calculator.
You want to iterate.
And like when you're seeing it and if this thing is high fidelity to like what you would actually see or what your coworkers would see if you were to send this to Sean, like that I think makes it so easier and makes you trust the product in terms of iteration.
When you say coworkers would see, do you see a multiplayer, multi-team collaboration with Artifacts?
Any things you guys think about that?
You can already share it, right?
Yeah, it's something that we're actively thinking about.
One thing that we've noticed internally without talking too much about the roadmap is that I...
There's many times when someone will ping me about something and I will ask TragicBD work the question and then I'll ping them back the answer.
And then I'll be thinking like... Like the simplest would be, you know, the three of us are just all on one hosted.
Exactly.
And I'll think about like, you know, like was I...
Required in this loop?
Or maybe it was, you know, rephrase like what they were asking or pulled from certain context or whatever.
But like, you know, when I gave them back the answer, that process was also lossy, right?
Like I gave them just like my interpretation of what
Strategy BG work cooked up but like underneath the hood there's so much context like in the rollout and stuff that that could be interesting
So like the answer was preemptively respond to every inbound request
No, it's just like literally like this is what I do sometimes with my job.
I know you copy paste and then you, you know, you're just a message forwarding service from AI to AI.
I think it's interesting, right?
It helps people understand the capability of what you can ask and delegate that oftentimes people don't realize until they try or someone shows you and then you're like, oh, okay, okay.
I see.
Yeah.
I think there's also like a light security issue where like basically you're the permissions layer.
Like, yes, I could query everything that you query and I could get an automated response, but maybe I'm not supposed to see it.
Yeah.
And there's no way I would know because I'm not supposed to know what I don't know.
Especially as like, you know, which IWB works for asking you to connect your plugins and, you know, it's pulling from your local files and stuff like that.
Like the amount of context that the agent has access to is like deeply personal and like that's something that we need to preserve.
So that'll be definitely a challenge.
There's,
Excel, there's PowerPoint, there's Docs, you know, the grand trio of work.
What other formats of work do you think about?
You know, like obviously you worked on Airtable.
Is there a future where there's like open AI Airtable?
Like, you know, like what does that look like if you ever ended up doing it?
It's a really good question.
I think...
I mean, one that you didn't bring up was sites, and I think that was the core part of this launch.
There's one side of sites that I think people commonly talk about, especially on Twitter and stuff, of this sort of prototyping tool.
And actually, we saw that happen with this launch.
Even the model slider that you guys were referencing earlier, that was developed almost fully in a site.
The collaboration between design and engineering and product on that was on a site where we play with
The affordance and figure out how it feels and all of that.
But the other aspect that I think is a little bit less talked about is like
Sites as like an artifact for knowledge work.
I was actually talking to someone the other day who was on like our corporate finance team and like they're mentioning how like now when they have these reports that they're working on as a team month to month,
Historically those things were in slide decks and in spreadsheets and now they're just in sites and like sites is the mechanism that they collaborate across the team and the reason is because it's like somewhat higher bandwidth like you know
These tools like PowerPoint and Excel are like infinitely flexible but at some point you reach the boundary of like
Either as a human you may not know how to use some feature or something or the product itself doesn't support it
But with a site you can kind of do anything you can ask for anything and you can get that
Once people see that magic I think it's been really valuable
Yeah, let me show you my case study.
This involves all the hot topics, including ChatGPT work, but also 5.6, token billionaires and token maxing and sites and auto research.
I'm a fan of this game called Strata.
It's basically like a little board game that you play with physical blocks.
They come on top of it like that.
So over the weekend, I took like 30 photos and just threw it into ChatGPT.
1.7 billion tokens later, out comes this site with a fully playable thing with 3D block placement and everything because it requires physical blocks and I needed friends to train on it so they can get better so I can play against them.
But also, I could also do things like train an AI on it.
And that gets into auto research.
So you want to train your own AIs and then make sure they self-play against each other.
I need to set both AIs.
So this is AI versus AI, and they're going to self-play.
Obviously, the AI started out bad, and then you want to define a loss function and get good.
I wasn't going to supervise all this.
I was at Daudi San Mateo attending a conference.
What I ended up doing was auto-researching on this and creating benchmarks.
And there was just way too many parameters for me to read.
So I started asking it for a site, and it's created this website.
This lab panel.
Is there a shortcut for a site that is created?
You should be able to go in the sidebar to sites top of the sidebar.
The left sidebar.
This one?
Oh, left?
Yeah, just scroll all the way to the top.
Oh, it says sites.
Oh, there you go.
Yeah.
So it creates the sites.
I don't think this is exactly what I wanted, but let me show you what it popped up.
I think as a research artifact, it is very important to communicate exactly what is being done.
Outputs this thing which I eventually started publishing.
So I moved it off of Sites because I wanted more database and infrastructure than Sites afforded me.
But this is like a research output that you can start to mess with and try to think about
Like what hyperparameters are you tuning for training your AIs?
And like, I was trying to make like scaling laws and everything and doing all sorts of like game optimization stuff.
And the fact that you can just kind of throw this up as a research artifact, like I no longer need to read chat GPT output.
I read site output and,
But then there's also a huge sprawl.
Like, look at how long this thing is.
There's so many numbers.
It is pretty overwhelming.
So then I have to start printing from there.
But it's an interesting transition from Markdown that you're putting out to you're putting out a whole functional site.
I think Markdown just isn't that optimal for people to read, right?
Might as well just write HTML website.
And I don't know, I think you can do a lot with customizing this, right?
You have your skills that explain what you want.
Like I noticed they're quite verbose.
I don't need a lot of this information.
It's very verbose.
And then the nice thing of having a site side by side is, you know, you just iterate on what you want and what you don't, right?
Yeah.
I don't know if that triggers any stories for you of how it's run internally.
Am I doing this right?
Yeah.
I mean, I think that this is like a workflow that we're seeing like all different types of teams use where like,
The canonical artifact that was previously a deck or something is now becoming a site.
And like with a site, because it's just HTML, you can like...
It's infinitely flexible.
And so, you know, if you if you want to give more prominence to a certain thing that like in a slide deck would, you know, feel like it was buried, like you can do that.
You can have it be like the hero image.
Right.
And so I think that like people are starting to see that there's obviously more work to be done to make these things like.
Much more easy to collaborate on.
You mentioned that they're long and verbose, could be broken up.
I'm sure there's something you can do there.
Yeah, but I think we're starting to see that there is this aspect of this is a really interesting format for people to use that's much more flexible than what they ever had before.
I think your job also becomes kind of meta.
You're not designing the products.
You're designing a product to make products.
And I'm curious how you manage that.
I think one thing that we've been...
Like when we look at the UX, like that we've been thinking a lot about is how can we balance like simplicity with capability?
Like if we're designing a product, like you said, that like is made to make up, build other things, right?
You can build so many different things, right?
But we can't put that all in front of you because you'll get overwhelmed.
And so we had similar problems or similar challenges even with ChatGPT, but especially now when there's so much that can be done, I think the balance that we're constantly trying to strike is how can we give the user enough of a UI surface where
They can be expressive, they can tell the agent what they need, they can verify that it's using the right tools, it's pulling from the right sources, etc.
But then it gets out of the way.
And then how can we build the right system such that we can show them instead of telling them what can be done?
Because so much of this is going to be like, how do they discover the next use case and the next one after that if they really want to be super powered by it?
AI.
It's interesting.
I feel like everyone also just has a different way to do it, right?
I made a similar version of this, same game.
I didn't take any pictures of board or rule game.
I threw an at goal, 18 minutes, 53 seconds later, a lot of seconds later, I've got a similar version.
Obviously not with all the auto research and whatnot, but you know, you got to do all the latest trends.
And yeah, I did it with codecs, not work, but it's interesting, right?
Yeah.
And this is obviously GPT image generating the pro avatars.
Very good for game design.
A lot of game designers were really into GPT image.
I will say the broader takeaway probably is the reason that we do this is...
More so just to test the tools, right?
Like this was also a test for 5.6 came out.
I had done the game on 5.5, right?
The ability for me to no longer need it to, I had defeated the rules.
It's a pretty niche game.
It couldn't find how to do this on its own.
Oh, yeah.
5.6.
It is auto distribution.
That's why I'm also very keen on testing the 5.6 capability.
But, you know, this is just as work comes out, as new things come out, these are just our sideways to test things, right?
Yeah.
It's some kind of private evil, I guess.
Yeah.
That is not all this private.
But also valuable because now you can send this to your friends.
I mean, I learned about this game through seeing this.
It's a hard game.
He's very good.
It's good when no one is competing with you.
But yes, it's a classic RL problem of self-play, bootstrapping your game AI.
You see how easily work becomes personal and personal becomes work because the thing I do for personal, it actually directly informs people I work with because I showed it to them.
They were like,
Oh, you can do that with GPT, which I imagine is the growth strategy.
Yeah.
The show not tell is a big piece that, you know, I think we're not still not fully cracked of like, you know, showing people all the things that they can do with the product versus like trying to teach that to them, like, you know, articles or onboarding or whatever.
Yeah.
Meeting them in the moment.
It's a career risk for me because I used to be in developer relations, right?
Where your job is to show.
And then you're like, what do you mean you don't need... Actually, your job is to tell.
But the product people are like, well, we don't need you if our product isn't intuitive enough.
So...
Yeah, I mean, that's the magic of the models.
So you can tailor the telling or the showing to specifically what the user needs, what they care about, what they've done in the past, exactly where they are on the adoption journey.
So I think that's going to be a super big opportunity.
Seems easier and easier now to tailor custom showing, right?
People have different use cases.
As much as you said you don't want to segment different people into different buckets, right?
It's also not that hard to for people that are in different categories.
But the question, I guess, is you said your team is more broadly on, what was the term you used?
Productivity?
Yeah.
Productivity.
Which is now work, basically.
Is it work?
Is there another distribution that we're not hitting?
Is there a group of people that will have something different than chat GPT codecs or work?
Is there more that the mass isn't targeting?
I see it as like a sequencing, like, you know, the vision is like bring useful agents to everyone.
We started with like developers, like developers
Historically are like early adopters that are willing to put up with more friction, set things up, et cetera.
Like that's where, you know, Codex started.
I think the next opportunity is like sort of what we call general knowledge work, you know, all the other functions around developers.
I think when you go from developers to this segment, like there's inherent challenges, obviously, with like, you know, this show not tell thing that we're talking about, making the product more understandable, bringing in new capabilities that matter more for this cohort than matter for developers, things like artifacts, things like computer use, et cetera.
And then I think like,
The same learnings like
Similarly how we took the learnings from developers and brought it to you know general knowledge work
The next stage will be like taking the learnings from general knowledge work and bringing it to everyone no matter what they're doing in their lives and we're already seeing that a little bit like
This game example that you have is you know something that's like on the border of like
Fun and personal life to your professional life.
I use ChatGP teamwork full time at home for everything, like for whatever I'm doing.
I used it the other day to come up with a meal plan.
And like you know save that on um on the like computer environment that it has and something that i can continue going back to like is everyone doing that yet
Probably not because the thing says work on it but eventually you know we want to get people there
Life yeah exactly tragedy cooking
But I think there's a lot of opportunity there.
But I see it as like, you know, we built a foundation in software engineering and we're going to take the same learning.
So we take software engineering to knowledge work, knowledge work to everyone.
Do you have any power user advice?
I feel like there's a group of people that will live it, use it for everything, stay on it 24 seven.
And then there's a bit of a gap between that crew and people that, you know, okay, I use it for work.
I use it occasionally.
Sometimes I pipe questions.
Any advice, any learnings, anything you recommend?
Or just, you know, takeaways that you found that help bridge that gap?
I think a couple things that I've seen is like one, that it really helps to broaden your imagination of what's possible.
And this has been a learning even for me, like, you know, the technology has progressed so fast that, you know, something that like even three months ago, like no way.
No way the malls can do this.
Like now it's like, wow.
It's like, you actually can like, um, you have an example we're going through right now.
There are like,
Review cycle internally.
And people always talked about this as like kind of a thing that the models are good at.
And like, you know, there's a cliche of like, OK, like no one wants to be writing reviews and like we just use AI to do it.
But I mean, it all starts to evaluate it as well.
Yeah, exactly.
In all seriousness, before it was like, just like slot basically.
And like, I think it was helpful, but you know, not super productive.
Now I've found that like,
The model can do a much, much better job than me, especially in this environment of like pulling contacts on like what people are up to, how they've like, the things that they've done to make a difference, highlighting like, you know, wins that they've had that like I may not even have seen, you know, has access to like everything, right?
Like the code, like, you know, things that they've caught, reviews, Slack, everything.
And so,
It's like incredibly powerful in that domain.
And like, just like six months ago, the last time we did this cycle, like I didn't even, I tried using it, but it was not at all helpful.
And this time it's been like incredibly helpful.
And like, so I think continuing to push the frontier of imagination, what's possible, even if you tried something before, I think is maybe my biggest piece of advice.
The other, I guess, thing is, like, the more you put in, especially in this environment where, like, you know, the model has access to everything on your computer or in strategy BD work, like, you can create, you know, artifacts over time and save them in your library and, like,
The model will continue having access to those.
The more information you give it about whatever domain you're in, whether it's your life or your work, the more valuable it becomes.
And it'll become both valuable in ways that might surprise you.
It might pull from context in a way that may be proactive and that you might not even have thought about.
But it needs to have access to those tools or that context first.
One thing I just want to talk about the review stuff, because I still, that's a very sensitive thing.
And you're a founder, you've managed people, you've hired people.
As manager myself, I'm very reticent to put out any LLM generated things, especially when it comes to people, because it feels like you don't care.
Presumably at OpenAI, people are obviously more open to being basically raided by GPT.
But are there any unofficial rules around this?
Like what's the etiquette?
Oh, I mean, I think the etiquette is that I would never write something solely via AI and present it as a review for someone.
What I was talking about is more like gathering context.
That's the place where it's incredibly helpful.
So it's just search.
It's agentic search.
Yeah, exactly.
It's like a genetic search, but, you know, that you can tailor and steer much more capably than you could before.
And because, like, the thing is, it's all...
There's sort of a flywheel happening, right?
Because of Codex...
People are able to do so much more now than ever before.
And if you're able to do so much more, it's easy to miss things as well.
And so I think we need to use these same tools to keep up with all the impact that people are having and understand where it can be helpful.
I think the thing, like, obviously, I run a small company, so easy to search.
But at the scale of OpenAI, with the amount of messages that you guys put in Slack, do you think that it misses things?
Probably, but I think that I also miss things.
Like, it doesn't matter, right?
It needs to be human level.
It's all relative, right?
Yeah.
Sometimes it's nice when it finds things you wouldn't, right?
Like right now, my codec system prompts, they're set up in such a way that every project I have has a separate notes MD.
And it just writes learnings to there.
And then the global one can pull from all these.
So sometimes it'll be like, oh, there's this project you did like four months ago.
Here's a note that we had.
And it randomly pulls it back in the context.
I would never do.
I haven't thought about it.
And I'm like, okay, this is quite superhuman, right?
Like stuff that would, and you know, it'll save like hours on chunking of stuff or find something that's already been done.
And I'm like, as much as it might miss stuff, I would too, but it's very useful when it finds stuff.
And I have like a very, you know,
Non-super-engineered solution to this.
It's just markdown files that get pulled whenever they want.
Yeah, I actually have a funny anecdote about this.
Recently, gearing up to this launch, the team has been really cooking on it for a couple months.
And over that time, there's so much conversation and chatter going on in Slack and Docs and elsewhere.
And one of the members of the team set up this
Scheduled tasks, like automation, to look at everything that's going on and come up with the best memes and then post it in one of our shared channels.
And there are two cool things about this.
The first is, I think the models are...
You know, over time, like actually starting to become like funny.
Or it was like, you know, a year ago, like that was not at all the case.
The second is, it was what you were saying, like they find things that in surprising ways that you may not have
Not have thought of and like create connections that you may not have thought of and that really helps with like the meme generation because then you can see something that you know genuinely surprises you and is funny in that way
So yeah I mean obviously that's like not like the most productive use of this technology but it does
It doesn't cover this like this capability that's emerging which is this like defined information that you otherwise would not
No.
Talking about the launch, I think I have pretty much said this is the most successful launch in a long time.
I think even more successful personally than 5.0.
And you're announcing 10 million users.
Does it feel different?
You've been through a lot of lodges.
I think it feels like a culmination.
Well, I think two things.
One, it feels like a culmination, like I was mentioning earlier, like this vision mission that we've been on for a long time.
Like I said, we saw the magic of Codex internally, and then you're like extremely...
Excited to bring this to many more people and to see it working, to see us reach the distribution goal in numbers that you mentioned.
I think that's huge and super exciting.
The flip side of that is like there's so much more to do too.
Like that's also really exciting.
Like, you know, ChatGPT as a whole, like this product that, you know, everyone almost equates to AI and like loves, you know, has hundreds of millions of users.
And so like 10 million is really cool, but like we need to get this to everyone.
Like we need everyone to feel this magic.
And so that's the next step from here.
But yeah, I think...
Extremely pumped about how it's going so far and the opportunities.
Awesome.
I did want to also, because I've been tracking the number closely, it transitioned at some point from just Codex users to Codex plus ChatGPT work, obviously because it's the same harness.
The whole point is that you can't count them separately.
You have roughly a billion users
ChatGPT users?
Why don't you just jump to 1 billion right away?
Like, isn't that the default on ChatGPT or no?
We don't default you into ChatGPT work if you're on ChatGPT.
If you're free, yeah.
It's also only available to paid users right now.
And I think there's like a process of, you know,
Educating users of what is the value of this product, having them try learning from their feedback and making it better over time.
But, I mean, the goal is to, you know, get as many people who love ChatGPT today to, like, feel the power of ChatGPT work.
But I think it'll be a journey.
Yeah.
Codex will still be alive as a brand for the foreseeable future.
Yeah.
And we'll just toggle between them as needed for UI stuff.
Yeah, I think it's an even stronger point than that.
I think we fully intend to treat developers like developers have been a core market for us for so long.
And there's so much more that we can do to make
Codex Crate specifically for software development and we'll continue to do that.
This doesn't take away from that at all.
If anything,
It should increase the utility of something like CodePix because now you can move seamlessly between writing a diff to creating an artifact or, you know, doing a search over your character.
I do wonder how much this terminology leaks to the non-technical user.
Like, do they have to learn to say artifact if I want artifact?
Or, you know...
It's funny, like we call it Artifacts internally because that's what the team's called.
No one says that.
No one calls it an Artifact.
But I think that people like often like describe things whatever they're used to, right?
So if, you know, Chachapity Work is good at creating slides, they'll say Chachapity Work is good at creating slides.
And that's actually what we want.
One big, another, I mean, it's July of 2026.
One big thing that also happens for OpenAI was OpenClaw.
And that's, I think, a lot of people's first time really maxing an agent for personal stuff, but also crossing over to work in some same way.
As far as I understand, OpenClaw is still independent, but...
Did you go through your own OpenClaw moments?
Were there any lessons that you took from OpenClaw to Codex or back?
Whatever.
I think there's a lot of inspiration.
I did go through my own OpenClaw moment.
Yeah, tell the story.
Me and my wife set up an OpenClaw to try to manage everything in our house.
Not that there's a ton, but it was actually quite useful.
We gave it a calendar and started creating events for us and stuff.
At some point, the laptop they were running on had died and they never got a chance to pick it back up.
But there's a lot of inspiration there.
Like, you know, in chat GBD work in web and mobile, like you get access to those like persistent computer environment where, you know, you can store files and those files stay around forever.
Between sessions.
And the idea is to be able to enable use cases like this.
One of the members of our team actually uses ChachiBD work for what they used OpenClaw for before.
And I feel like it has like completely transitioned, which is like workout planning and like meal tracking, which again,
It's like a worky thing, right?
It's like not work necessarily, but it's like in personal productivity space.
But it has all the same primitives.
It has scheduled tasks.
It has the ability to store files on a file system.
It has the ability to reference those things over time.
And so you start to see the same types of use cases emerge, which has been really cool.
Is there a point that...
ChaiGPC work completely replaces OpenClaw?
Obviously, they're independent, so... Yeah, I mean, I'm not close to it, so I can't speak to the OpenClaw roadmap, but I don't think so.
I think that there's going to be, you know, there's always a need for, like, this, like, incredible, like, open-source technology that...
That team has built.
And I think that we can draw inspiration in the product.
And, you know, ChatGPT, I think many more people have heard about and used ChatGPT than have used OpenClaw.
And if we can take the magic from OpenClaw and bring it to them, I think that'll be a success.
I think that like one thing on the strategy BD work side that we feel strongly about is that like the core experience is that you come to this product and you have a conversation, start a session, whatever you want to call it with this agent.
And the magic of the product is that you can do anything in that moment.
And
We would like to create a product where you don't have to click a button or to go to a different place, whatever.
And you can get whatever functionality exists in your finances app or any other product in this one place.
And so that's the goal.
It's like we want an extensible system with plugins where
You can connect to the tools that you need in order to be able to accomplish like a financial task where you can you know if if you're doing like science work like we have an ability to like extend the system and such that you can like write the tech and it performs well
There will always be like products that we support that are best in class at those things but
We want as much of the magic as possible in that core experience.
Yeah.
Do you think that you can do everything you used to do with Wealthfront in Chachapiti Finance?
I actually tried it.
I mean, like Chachapiti doesn't yet custody cash and assets for me.
So that part, no, not yet.
But I mean, there was like a whole component of like retirement planning there.
And sort of like financial planning and budgeting and stuff that we were looking into when I was there and like,
With the finances plugin, like, that's all possible.
So I feel like at least that component's replaced for me.
I haven't really plugged it in yet.
I'm somewhat scared to look at the answer.
Like, that's honestly, like, the same reason for health and finances.
Like, I don't know.
Know it's really good
I mean it's it's really cool how i mean we were talking about like the agentic search aspect a little bit earlier but like it's really cool how like you know in conventional ux like if the more power you want to give to a user the more like knobs and bells and whistles you need to add like you know for like these finance and budgeting apps like there's always like a bunch of the different filters and like search bars and stuff like that
But like now like with the right
Connectivity to the right data you can have whatever you want you can ask any question you want and into that box and get the answer and I think that's super powerful
I think it's also nice to just have it centralized in one space, right?
You have different health apps.
I have one for a smart scale, a watch, all these different things.
It's just nice to centrally co-locate it.
Which is part of the whole thing of OpenClaw, right?
That you would have a personal OS, which presumably ChatGPT wants to become.
I do think that just relying on just-in-time pulling of data for, let's say, via MCP, CLI, API, whatever you do, still not enough.
I come from a bit of a data engineering background.
You still want a data warehouse or some kind of caching or semantic layer.
Do you feel that or...
Do you already have that?
I can't speak to all the details on how everything works, but I think it depends on the access pattern, right?
If you want an answer immediately, then yes, it's very difficult to do that if you need to pull from all of these sources.
But a lot of the use cases that we want to enable in ChatGP to work
Aren't necessarily something that you need immediately.
It's more like a task that you want the agent to go and do.
And that's going to take a certain amount of time.
And, you know, with things like programmatic tool calling and stuff now, like some of that time and sub-agents and stuff, like some of that is also parallelizable.
And so it's possible, I think it's very possible that there's the ceiling on what can be done, you know, with MCPs and like,
Calling out to these third-party services has been raised substantially.
So we're really excited about that.
You mentioned some agents.
I got a double-click on that.
Ultra is a new mode.
You have special affordances in ChatGPT itself to show off the agents.
Can't really do much with them, to be honest.
Just watch.
What have been your experiences, any design issues that you would call out to other builders building with sub-agents?
I think it sort of goes back to the balance that I was raising earlier about like, you know, showing builders the power of the tool, but also creating enough of an abstraction to not overwhelm them.
I think with subagents, the thing that we wanted to show is that
You can take a task that, you know, has many parallel tracks or, um, is, is complicated in a way that, you know, some agents can handle and this product is for you.
Like the model can, can accomplish those goals or try to accomplish those goals.
Um,
And so, like, that's the point of, like, showing them the product.
And that's where we've gone with the design.
There's another, you know, iteration of this where, like, you can see exactly what they're doing and things like that, which I think is, like, you know, could verge on, like, overwhelming with information.
And so this is, like, the deliberate tradeoff that we've made for now.
I mean, you do display quite a lot of transcripts.
Right, right.
I think it's hidden by default.
You wanted to stay more than that?
No, no.
Some people could want more.
So I'm one of those people that will basically throw a lot of stuff at goal and pretty much every goal I'll tell it to use sub-agents.
Seems redundant, right?
But every time I'm like, okay, use subagents where possible.
And I have a lot of people, a lot of friends that recommend and do the same.
Whereas I'll sometimes talk to people that are like, okay, this is where I want you to use subagents for this subtask.
And I'm sure they would appreciate seeing into how they're being used.
For me, it's primarily like two things, right?
One is net time efficiency.
So span out across sub-agents.
Two is probably cost, right?
Don't use big, expensive model.
Offload to a lot of smaller, cheaper models.
And...
Some people want that level of control.
So if you have repetition in what you're doing, right?
Say I want something built where I want it to consistently do this every day.
I might want to go in and fine tune sub-agents here, sub-agents there.
You can see both, but I think if I'm not mistaken, it's hidden by default.
There's a dropdown that goes a lot where I'm like, okay, I'm just going to keep, you know, you can change the model that they use.
I know I tell them to be steered.
I'll say my,
I know Anthropic offers this in cloud code.
You can tell Fable to use Sonnet or Opus to use Sonnet as sub-agents.
So pretty trivial thing.
You know, you tell it to span out sub-agents with Sonnet, you know, it's cheaper, faster.
I would assume if it's not there, it could be built there.
But I think there's a side of... Too many toggles.
It's not a toggle actually it's just you tell it in chat the way I do it is prompt it right and I think this is something that gets abstracted unless it's something you built for repetition right so
If I'm building something, say that's a podcast prep, right?
Research into people, do a very, very deep, extensive research that I might want to configure to cheaper, faster model just for web search, right?
I can see a world in which you want both.
I think the default is actually pretty good right now where it's hidden, but you can drop down and get some more info into what's done.
I know people talked a lot about it.
On 5.6's launch.
This thing loves to use a lot of sub-agents and causes the ChatGPT app to just crash because it's so processor heavy.
For what it's worth, that's not my experience.
I mean, I haven't had a crash from sub-agents.
I haven't either.
We both have big laptops.
I know people brought it up.
There was a topic of discussion that we didn't see the same, but it is another vibe eval, right?
People are like, okay, the amount of sub-agents Sol is spawning is crazy.
And I'm like, I think this is okay.
I think it's good, but just stuff people bring up.
I think when we launched the product too, it would be...
Weren't as opinionated about, like, who is Ultra for and, like, when should they be using it?
And since then, we've made some changes to, like, you know, require you to turn it on and find it in the advanced setting because that's who it is for.
It's for, like, power users who understand what's going to happen because it also, you know, depending on your use case, can use more of your limits as well.
Yes.
So that's where I think a lot of the feedback was coming from.
It's okay.
Reset the limits.
Always reset the limits.
You know, today we're resetting because of this.
I want to change topics to one last piece of the harness, memory.
A lot of people are commenting on memory recently.
Chad Gipsy's new memory system uses something that's not very good.
And then this guy also basically the same thing.
And Samir, who you presumably work with, talking about memory.
What can you say there?
I think that, you know, Samir and the team have made a ton of, and the research teams have made a ton of updates and improvements over time.
I think when I talk to friends, family members about what they love about ChatGPT, like the fact that it knows them, that they feel like their ChatGPT is their ChatGPT, I think comes up probably
Number one, in ChatGP, you work in the cloud.
By default, all conversations will inherit from your ChatGP memory, so they'll know context about you, and they'll also be able to write back to this memory.
With like a small text write, like you tell me when you're writing, right?
No, it's part of the same like memory V3 system that we launched.
Yeah, Dreaming V3, yeah.
So I think that's been really powerful because, you know, going from ChatGPD to ChatGPD work feels like an extension of what I've already been doing with the product for sometimes many years.
So that's been awesome.
And it's awesome to see that people are recognizing the improvements here.
So it's basically a retrieval problem, right?
Like, are you retrieving the right things?
Are you over-focusing on the wrong things?
Is there like a more false positive or false negative?
You know, if that makes sense, like what's the bigger problem?
So I don't work on memory directly.
So it's hard to say what the bigger problem is with like certainty.
But I think you're right.
I think that like, you know, there's two sides of it.
It's like, you know, making sure it knows things about you, but then also having the EQ to like bring those things up at the right moments.
Proactively or surprising you in ways that are positive, not negative.
So I think it's a very challenging problem, but something that I think we feel is a huge opportunity to get right, which is why we make investments in it.
How do you see the side of, okay, when you're building Chat2BT for work, different than the regular chat app, different than Codex, managing memory across different projects, collaboration and whatnot.
How do you see the side of what's separate from the harness, right?
So if I have four threads on one project, any learnings on how to build memory systems there, you know?
For background as well, I guess, to steer it a bit is when you do chat style applications, I'd say you have a lot of one-offs, right?
When you switch to work, it might be something you're doing for a month, something you do a lot, right?
Now, as I add more sessions, there's a lot more than just single threaded, right?
And there might be memory there.
I mean, I think first I challenge that, like, the depth of the memory or the, like, value of it is, like, fundamentally different across chat and work.
Like, it is true that, like, you know, there are a lot of, like, shorter sessions on chat.
But I think, you know, the ChatGBD, the product has had, like,
A ton of longevity, you know, as long as this technology has been around and people use it for worky, like productivity related things already today.
And so I think we found that there's a lot of value.
I mean, I found this with my personal usage, like
All these one-offs add up over time into something like quite durable and like quite a good representation of who I am.
I know like from time to time something will go viral on X about like, you know, Chachapiti telling you everything he knows about you.
And people are always surprised like how deep that is.
The fun roast me, you know.
Exactly.
So I think that's all to say that I think there's a lot of depth there in the existing Chachi BD product.
And so that's why I think we think it's valuable to bring into the work product.
But the other reason I brought that up is because I think
Like hopefully we can use some of the same fundamental primitives and systems to extend memory here as well.
And I know this is something that the team that focuses on this is like working through right now.
I wanted to bring up one element of memory, which I honestly don't really use much.
And I'm curious if you do, Chronicle.
Which is up on screen right now, it's kind of a super memory or like, what is it?
I think the idea is that it can learn from how you're using your computer and it's another input source into memory.
And I think it's experimental right now and something that isn't default off.
But I'd recommend that you try it.
I think that it's quite interesting how it goes back to a conversation we were having earlier on like, you know,
You were asking, like, does it, can ChatGPD miss things?
Like, does it, you know, on Slack, when it's searching, does it miss things?
Because there's such a volume of stuff, right?
And like, you can ask the same question about like everything that you're doing on your computer.
Like, is it going to know everything that you're doing?
Is it going to capture the intent and stuff like that?
Probably not.
But like, it
Probably will find things that you might not know about and then if it can surface those to you in relevant times in proactive ways like when you're doing tasks and I found at least that it can be quite helpful
So it's worth trying
So mostly for insights and longer term
Yeah, exactly.
Insights in it builds context that can make you more productive on certain tasks, but it's hard to describe without feeling it.
I will say you can feel it pretty well.
Like the idea of what they're saying here, right?
Just check through my memories or check through my logs and add skills.
Yeah.
Pretty underrated.
That's automations.
You can repeat that using a cron job.
Checking through your memories and creating skills.
But I think the creation of the memories from Chronicle itself is like what's different.
It's like you have much deeper memories because you have Chronicle on.
It's there.
I don't use it much, but maybe I just, I need more examples.
I imagine you guys use a lot of it internally, so I'm always fishing for use cases.
Yeah, I would just try turning it on and then like...
It just auto works.
Yeah, and seeing like where it might start helping you, I think you'd be surprised.
Yeah, amazing.
I think that was about it in terms of the overall coverage of ChatGPT work.
I think there's been a lot of good progress and discussion on building and all these things.
There's a lot of ex-founders in the community and in OpenAI as well.
Do you think that...
Things have changed a lot.
I guess your overall reflection of building pre-AI and post-AI?
I mean, I think things have changed a ton.
I think it's like super exciting to see how quickly you can go from idea to something real today.
Whereas even before, I think five, 10 years ago, it was fast if you were scrappy and willing to build the minimal viable thing.
But now the extent of what you can build is much, much broader.
And I think that also...
What we've seen internally building is that gives you an opportunity to validate much more quickly, to talk to users, to talk to internal dog feeders, et cetera, and make sure you're on the right track.
And that loop, I think, has become...
More clothes than ever before.
And that's like a win for product development.
I think it's a win for consumers and users too because ideally that means they're getting much better products out the gate.
Does it mean your teams are smaller?
I think there's much more to do now.
So I think people can accomplish...
More individually or in a small team than they were that would require more people than before.
But there's at the same time, there's also more to do.
So I think the teams are much more ambitious.
You seen any changes in scopes of roles and building teams and how we used to have teams say a few years ago versus what ideal teams look like now?
I think we've seen a blurring in the lines between the typical product development functions, like between EM, VM, engineer, designer, et cetera.
Yeah, I want to bring up this quote.
There will be only four jobs left in tech.
There's AI slop cannon, the people who just like burn a bunch of tokens.
And then there is SRE, people who are more responsible.
There's grownups who sell things.
And then there's hot people.
This is an interesting take.
I think...
My suspicion is that there's everything, everyone will be like T-shaped in a way and that like AI will enable everyone to become a generalist.
Like, you know, things that like I never would be able to like come up with a design before.
And like even now, I don't have maybe like the visual taste required, but I can iterate on something with the help of AI.
But then people will have a specialty and that's like the, I guess the straight line and the T or the upward line and the T. And so like you can have a specialty that you're interested in with the help of AI, you can go deeper and become better at over time, but then you'll also be a generalist.
And so with that foundation, what you can accomplish is like almost limitless.
What are you bottlenecked by in terms of specialties?
Do you need more designers?
Do you need more slob cannons?
Do you need more hot people?
I think the bottlenecks becomes sort of like ideas and taste, I guess.
I think because anyone can build now, I think it really is the era of bottoms-up ambition.
And because there's so much to be built, you're always going to be bottlenecked by...
You know, the amount of ideas and the amount of things that you're doing at any given time.
Do you think models help solve that?
Yeah.
I mean, I have the example of like, I have a front end design skill that's like, they give me four drastically different examples of what this looks like.
Sure, it burns a lot of tokens, but you know, and then I'll mostly just condense down.
Okay, I like this part, I like this part.
Let's draw these together.
And it's like, yeah, I had a vision, but like, I don't know.
I would say that the one automation that I would love to work and it doesn't work is bring me new ideas, right?
Somehow LLMs are just not it.
One interesting part of that idea is like they're not like in a vacuum.
It's like not, they usually come from somewhere.
And like, you know, in product development, like they're coming from talking to users or reacting to, you know, friction that you're seeing or feedback, building on some foundation that you already have planned out before, whatever.
And so I think that's where like...
I think there will always be value in these generalists that we talked about, like, you know, closing that loop and coming up with those ideas that are grounded in that feedback or talking to users or whatever it is.
Cool.
You lead the productivity team.
How do you define productivity?
I think our mission is to make it possible for people to do things that they weren't able to do before.
And right now we're thinking about it from the perspective of knowledge work.
And so when I look at knowledge work, I think about people are no longer siloed by their roles.
They're no longer siloed by maybe
The background or training that they have.
No matter what function you're in, you can suddenly build things.
You can suddenly get access to data that you otherwise might not be able to interpret, etc.
And then I think that extends...
To your personal life where we want to give you leverage at the end of the day.
We want the models and the product to be able to give you leverage so that you can, you know, create time for yourself to do the things that you love.
Does that also translate to a way to measure productivity?
Like what is the measure leverage?
I think we haven't figured this out yet.
Part of the reason is it's so diverse.
Everyone has different goals and really the true measurement is like their ability to achieve that goal.
Did we help you or did we not?
Yeah.
And it's very difficult without knowing what that goal is up front and also tailoring it for every individual.
And the thumbs up and thumbs down from ChatGPT doesn't give you anything, right?
Right.
I mean, you don't know if they're thumbs downing the content of the answer, the vibe of it, whether or not it helped them with their goal.
I think that's difficult.
But it's something that I think we will need to figure out and the industry at large will need to figure out because...
You know, that's how we measure success.
Do you think it's changed productivity and how you measure it?
Basically, you said there's a lot more work that can be done, a lot more scope.
Has it changed?
I think it was always true that what you really wanted to measure is like,
You know, was your team, was the individual, were you personally able to hit the goal or are you closer to hitting whatever your goal is, right?
But I think previously we used proxies for this.
So like, you know, code commits or lines of code or whatever.
Story points.
Yeah, exactly.
Story points.
They're coming back, by the way.
Maybe, but that is part of the change.
I think with AI now, those proxies are starting to fall apart.
The number of tokens you use or the number of pull requests you make are no longer...
Maybe as hyper-correlated that is your team able to hit the goal or are they on track to hit their goals?
So I think we'll need to come up with new measurements.
For the managers listening, give them one thing to try.
I think for me, what's important is at-bats.
Are we as a team building the muscle to have not just quantity of at-bats, but quality?
Are we able to go all the way from generating an idea, building it out, getting the feedback, reacting to that feedback, actually validating or invalidating the hypothesis, going on to the next idea?
Are we able to do that really efficiently?
Like that goes to like, you know, the actual like code that's being written or the designs that are being made or the specs that are being written, whatever, but also the culture of the team.
Like, do we have the humility and are able to like go through that process many, many times and stay motivated and excited throughout that?
So that's the thing that like I think is important now, especially when we're on the frontier of this technology and like,
There's so much to build.
There's so much to do.
That's probably the most important thing that we look at.
Any traps people fall into around measuring productivity, what's your teamwork on?
I feel like there's a lot of, okay, we added a lot of LLMs.
We have dashboards for this and that, but not much has changed, right?
That is the trap, yes.
And, you know, the broader...
Source of the question is for the managers and teams building, you know, how should they approach this?
I think maybe the trap is like conflating motion and progress.
I think motion is much easier now than ever before because of the tooling that we have.
But progress requires you to be very prescriptive and deliberate about what you're actually trying to achieve.
It goes back to our question of measurement, right?
We were talking about, can we, OpenAI, figure out how to measure productivity for our users?
That's a very hard problem because of the diversity.
But as a team, you should have a really
Prescriptive and deliberate view on like what progress looks like for you and for your team.
And if you don't have that, then it's very easy to conflate these two things.
I think at-bats is a really great thing.
I'm really glad.
I like the discussion between motion and progress.
I think that's a quote that we're going to feature on the write-up.
You've been very generous with your time.
Thank you so much and congrats on 10 million.
Yeah, thank you for having me.
Next Monday at 100.
In two months.
Two weeks.
Thank you.
