What are the key takeaways from this Latent Space episode?

Key insights include: **Harness unification:** ChatGPT Work and Codex share the same underlying capability harness — the differences are purely UX-level. Codex surfaces git diffs and file edits explicitly; Work abstracts those details away. Users never need to choose between them because the model routes automatically based on task type, such as redirecting spreadsheet creation toward Work mode without manual switching.; **Non-developer adoption signal:** When Codex launched internally at OpenAI, the most telling signal was not developer usage but the pride non-technical staff — strategic finance, marketing — felt using it. That emotional response, feeling like they had a superpower, became the product thesis for ChatGPT Work: agents are ready for general knowledge workers, not just engineers, earlier than anticipated.; **Motion vs. progress trap:** Teams adopting AI tools frequently confuse activity with advancement. Nathan distinguishes motion — easy to generate with current tooling — from progress, which requires deliberate, prescriptive goal-setting upfront. Managers should define what a completed "at bat" looks like: idea generation, build, user feedback, hypothesis validation, and iteration, all completed efficiently in sequence.

What did Akshay Nathan discuss on Latent Space?

Akshay Nathan, OpenAI's core product engineering lead, explains how ChatGPT Work reached 10 million users by merging the Codex and ChatGPT harnesses into a unified productivity platform. The conversation covers the product architecture decisions, sub-agent design tradeoffs, memory systems, artifact evolution, and how OpenAI measures team progress in an AI-accelerated development environment. Key topics include: **Harness unification:** ChatGPT Work and Codex share the same underlying capability harness — the differences are purely UX-level. Codex surfaces git diffs and file edits explicitly; Work abstracts those details away. Users never need to choose between them because the model routes automatically based on task type, such as redirecting spreadsheet creation toward Work mode without manual switching.; **Non-developer adoption signal:** When Codex launched internally at OpenAI, the most telling signal was not developer usage but the pride non-technical staff — strategic finance, marketing — felt using it. That emotional response, feeling like they had a superpower, became the product thesis for ChatGPT Work: agents are ready for general knowledge workers, not just engineers, earlier than anticipated..

How long is this episode of Latent Space?

This episode is 69 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Latent Space

Codex from 0 to 10M Users: Building ChatGPT Work — Akshay Nathan, OpenAI

July 28, 2026

69 min episode · 2 min read

Akshay Nathan

Episode

69 min

Read time

2 min

Topics

Productivity, Fundraising & VC, Leadership

AI-Generated Summary

Published Jul 29, 2026

Key Takeaways

✓Harness unification: ChatGPT Work and Codex share the same underlying capability harness — the differences are purely UX-level. Codex surfaces git diffs and file edits explicitly; Work abstracts those details away. Users never need to choose between them because the model routes automatically based on task type, such as redirecting spreadsheet creation toward Work mode without manual switching.
✓Non-developer adoption signal: When Codex launched internally at OpenAI, the most telling signal was not developer usage but the pride non-technical staff — strategic finance, marketing — felt using it. That emotional response, feeling like they had a superpower, became the product thesis for ChatGPT Work: agents are ready for general knowledge workers, not just engineers, earlier than anticipated.
✓Motion vs. progress trap: Teams adopting AI tools frequently confuse activity with advancement. Nathan distinguishes motion — easy to generate with current tooling — from progress, which requires deliberate, prescriptive goal-setting upfront. Managers should define what a completed "at bat" looks like: idea generation, build, user feedback, hypothesis validation, and iteration, all completed efficiently in sequence.
✓Sub-agent defaults: Ultra mode, which activates multi-agent parallelization, was moved behind an advanced settings toggle after launch feedback showed casual users were hitting usage limits unexpectedly. The practical guidance: use Ultra for tasks that are either highly parallelizable or genuinely open-ended; use default configuration for most tasks and adjust only when quality or cost efficiency falls short.
✓Sites replacing slide decks: OpenAI's internal corporate finance team now produces monthly reports as hosted sites rather than PowerPoint or Excel files. Because sites are HTML-based, they are infinitely flexible — any layout, any data prominence — without requiring the user to know a specific feature. Nathan identifies this format shift as an underreported consequence of the ChatGPT Work launch alongside artifacts.

What It Covers

Akshay Nathan, OpenAI's core product engineering lead, explains how ChatGPT Work reached 10 million users by merging the Codex and ChatGPT harnesses into a unified productivity platform. The conversation covers the product architecture decisions, sub-agent design tradeoffs, memory systems, artifact evolution, and how OpenAI measures team progress in an AI-accelerated development environment.

Key Questions Answered

•Harness unification: ChatGPT Work and Codex share the same underlying capability harness — the differences are purely UX-level. Codex surfaces git diffs and file edits explicitly; Work abstracts those details away. Users never need to choose between them because the model routes automatically based on task type, such as redirecting spreadsheet creation toward Work mode without manual switching.
•Non-developer adoption signal: When Codex launched internally at OpenAI, the most telling signal was not developer usage but the pride non-technical staff — strategic finance, marketing — felt using it. That emotional response, feeling like they had a superpower, became the product thesis for ChatGPT Work: agents are ready for general knowledge workers, not just engineers, earlier than anticipated.
•Motion vs. progress trap: Teams adopting AI tools frequently confuse activity with advancement. Nathan distinguishes motion — easy to generate with current tooling — from progress, which requires deliberate, prescriptive goal-setting upfront. Managers should define what a completed "at bat" looks like: idea generation, build, user feedback, hypothesis validation, and iteration, all completed efficiently in sequence.
•Sub-agent defaults: Ultra mode, which activates multi-agent parallelization, was moved behind an advanced settings toggle after launch feedback showed casual users were hitting usage limits unexpectedly. The practical guidance: use Ultra for tasks that are either highly parallelizable or genuinely open-ended; use default configuration for most tasks and adjust only when quality or cost efficiency falls short.
•Sites replacing slide decks: OpenAI's internal corporate finance team now produces monthly reports as hosted sites rather than PowerPoint or Excel files. Because sites are HTML-based, they are infinitely flexible — any layout, any data prominence — without requiring the user to know a specific feature. Nathan identifies this format shift as an underreported consequence of the ChatGPT Work launch alongside artifacts.
•Memory as retention flywheel: ChatGPT Work inherits the memory v3 system by default, meaning all Work sessions read from and write back to a user's existing ChatGPT memory profile. The practical implication: the longer someone has used ChatGPT conversationally, the richer the contextual foundation Work agents draw from immediately, without any manual setup or re-onboarding when switching to agentic tasks.

Notable Moment

Nathan describes using ChatGPT Work to conduct performance reviews — not by generating the review text with AI, but by deploying it as an agentic search tool across Slack, code repositories, and documents to surface employee contributions he would otherwise miss. He notes this capability was entirely unhelpful just six months prior during the previous review cycle.

Know someone who'd find this useful?

Episode Transcript

Okay. We're here in the studio with Akshay from OpenAI. Welcome. Thank you. And with our trusty co host, Vibhu. We, so you recently launched Chattopity Work. You lead core product engineering. You know, it's been a long journey, into into all this. I find it very interesting that you started with no code or low code, with Walrus and Airtable. And to to some extent, Chat GpT Work is kind of like the super app of super apps of, well, here is the ultimate no code. You just write a 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 I was just kinda jank, back then, but, you know, doing what we can. And then 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 useful to them. But once, I think, LMs 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 twenty twenty three. Now we've got, you know, so much more stuff. So ChatGPT, codecs app, ChatGPT for work. How have things changed? Actually, I think the more interesting thing is how things haven't changed. Like, I guess, like, one, I 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 gonna feel startup enough? And I joined, and I was, like, this feels even more startup y than I could ever imagine. And, like, that that really hasn't changed even till 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 and and ship it is 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 …

Get the full transcript (15,123 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Latent Space transcripts →