Lenny's PodcastAlexander Embiricos: How Codex grew 20x by moving into IDEs
How Codex left the asynchronous cloud for IDE extensions and terminal sandboxes; reviewing agent-written code is the new bottleneck, not compute.
CHAPTERS
- 0:00 – 5:21
Codex in one minute: the “teammate” vision and early mind-blowing wins
The episode opens with a crisp framing of Codex as OpenAI’s coding agent—and as the earliest version of a full software-engineering teammate. Alex and Lenny tease striking examples of acceleration, from solving notoriously hard bugs to Codex contributing to its own training infrastructure and rapid app launches.
- •Codex is positioned as the start of a true engineering teammate, not just autocomplete
- •Analogy: a brilliant intern that lacks ambient context (Slack/Datadog) unless prompted
- •Anecdote: Codex can solve extremely gnarly bugs given time to run
- •Early glimpse: Codex reviewing code for its own training stack and catching config mistakes
- •Acceleration headline: Sora Android app built in 18 days, public in 28
- 5:21 – 11:34
What’s different about OpenAI: speed, ambition, and bottoms-up execution
Alex explains how OpenAI’s pace and impact expectations reframed his notion of “moving fast,” even relative to startups. The org operates unusually bottoms-up, optimized for rapid empirical learning in a world where capabilities and product-market fit are uncertain.
- •OpenAI’s speed/ambition is ‘dramatically’ beyond prior startup and big-tech experiences
- •Living through Codex’s rapid scaling changes how Alex allocates time and focus
- •Because the future is uncertain, empirical iteration beats perfect planning
- •Bottoms-up execution is real, but depends on exceptionally high talent density
- •Aiming is ‘fuzzy’ long-term; short-term shipping and learning drives product direction
- 11:34 – 15:49
Codex explained: IDE/CLI agent today, full lifecycle teammate tomorrow
Alex defines Codex concretely (VS Code extension and terminal tool) and then broadens to the long-term goal: an agent that participates across ideation, implementation, validation, deployment, and maintenance. The core bet is proactivity—Codex becoming helpful by default rather than requiring constant prompting.
- •Codex works in the ‘thick middle’ of the SDLC: writing and shipping real production code
- •Long-term: agent participates in planning, validation, deployment, and maintenance
- •Teammate framing highlights current gaps: missing passive context and situational awareness
- •Key product goal: proactivity (agent suggesting/doing work without being explicitly asked)
- •Bottleneck today: users must know when to ask—future is ‘helpful by default’
- 15:49 – 21:38
Explosive growth: what changed after the early ‘Codex Cloud’ approach
Codex’s usage surged post–GPT-5 launch, with Alex sharing 10–20x scale growth and massive token volumes. He explains a crucial product lesson: the first “cloud computer you delegate to” vision was powerful but too hard to adopt broadly, so the team shifted to interactive IDE/CLI workflows with tight feedback loops.
- •Growth since GPT-5 launch: over 10x, now ~20x; Codex models serve trillions of tokens weekly
- •Early Codex Cloud enabled parallel delegated tasks but had onboarding friction
- •Main unlock: meet users where they already work (IDE/CLI) and make value immediate
- •Sandbox approach: safe execution with access to dependencies; agent can run commands or ask
- •Internal dogfooding can mislead because OpenAI’s workflows are unusually ‘future-native’
- 21:38 – 24:59
Why Codex is getting so strong: model + API + harness (and long-running agents)
Rather than treating coding performance as purely a model problem, Alex describes an “agent stack” view: model, serving layer, and harness must co-evolve. He highlights compaction—enabling tasks that run overnight or 24 hours by managing context limits—as a capability requiring tight integration across all layers.
- •Codex strength comes from tuning the full stack, not only training a better model
- •GPT-5-based “Codex Max” improves speed and high-reasoning performance on hard tasks
- •Compaction enables long-running work beyond context windows
- •Serving and harness design choices (e.g., shell-first workflows) shape training and capability
- •Opinionated tool environment accelerates iteration versus trying to fit every harness style
- 24:59 – 33:24
How OpenAI ‘wins’: the super-assistant thesis and coding as the core agent skill
Alex argues that as new AI capabilities ship continuously, users need a sticky “super assistant” that just works—without reading guides for every new feature. His core claim: to make agents effective at taking action, the best way to use computers is to write code—so building a coding agent is foundational to building any agent.
- •Winning product is a proactive, sticky assistant that reduces user burden and complexity
- •Chat is a great default interface when users aren’t sure what to ask or do
- •Functional experts (developers) still need deeper GUIs for code-level work
- •Agents are more effective when they can use a computer; coding is the most reliable method
- •Idea: non-technical users may ‘use a coding agent’ without realizing it
- 33:24 – 43:45
Engineering impact: code is easy; review and validation become the bottleneck
The conversation turns to job impact and what changes when code generation becomes abundant. Alex emphasizes designing tools that ‘maximally accelerate’ humans, while Lenny highlights the looming overload of reviewing many AI-generated PRs—pushing focus toward validation, testing, and code review experiences.
- •As code becomes more ubiquitous, demand for people with software competency may rise
- •Product north star: accelerate humans rather than obscure what the human should do
- •New pain: reviewing AI-written code is often less fun than writing code
- •Focus shift: better AI validation and AI-assisted code review to build trust
- •The ‘end of the funnel’ (review/merge confidence) becomes the key constraint
- 43:45 – 46:55
PMs and designers with Codex: compressed roles, throwaway tools, and ‘vibe-coded’ prototypes
Alex shares how Codex changes his PM workflow: faster learning, easier analysis, and prototyping that sometimes beats writing specs. He describes the emergence of “throwaway code” and role compression—designers building working prototypes and even PRs with agent help.
- •Codex makes PMs feel more empowered—answering questions, understanding changes, prototyping
- •“Compressing the talent stack”: fewer handoffs when individuals can do more end-to-end
- •Rise of throwaway code: quick interactive viewers/tools created for one-off analysis
- •Designers build prototypes (even animation tooling) via vibe-coding and ship to repos
- •Internal workflows evolve toward quick jams + executable prototypes instead of heavy docs
- 46:55 – 48:56
Case study: shipping the Sora Android app in 28 days (and what made it possible)
A standout example of agent-driven velocity: a small team shipped a brand-new Android app in 18 days to employees and 10 more days to the public. Alex explains that Codex excels at porting and cross-referencing existing implementations (e.g., iOS) to generate plans and execute quickly.
- •Sora Android: 18 days to employee launch, 28 days to GA, with 2–3 engineers
- •Codex adoption intensity inside OpenAI increased over the year (skill + usage)
- •Porting advantage: leverage existing iOS app as reference for plans and implementation
- •Agent helps compare platform differences and execute step-by-step
- •Illustrates broader theme: massive velocity gains once teams become power users
- 48:56 – 55:14
Case study: building Atlas (the browser) and the road to Windows/PowerShell
Alex recounts how the Atlas browser team used Codex ‘for absolutely everything,’ compressing timelines dramatically on chunks of work. The project also drove improvements for Windows support, including models that understand PowerShell—a key ingredient for agentic development across platforms.
- •Atlas is a hard, systems-heavy project; Codex became central to team execution
- •Reported acceleration: tasks that took 2–3 engineers for 2–3 weeks become 1 engineer in ~1 week
- •Atlas shipped on Mac first; Windows work feeds back into Codex capability needs
- •PowerShell understanding highlighted as a notable milestone for Windows-native agent work
- •Codex benefits spread beyond engineering into research, design, and marketing workflows
- 55:14 – 58:09
Progress metrics: beyond benchmarks—retention, onboarding, and Reddit ‘vibe checks’
When asked how they measure progress, Alex stresses avoiding a trap: over-optimizing for power users. The team watches early retention, repeatedly re-tests the first-time experience, and mines unfiltered feedback—especially on Reddit—for real-world pain points and “broken” behaviors.
- •Risk: building only for power users because advanced agent workflows are seductive
- •Key metric: early retention (e.g., D7) and repeatedly experiencing onboarding from scratch
- •Continuous dogfooding paired with awareness of different market/user behavior
- •Heavy social listening: Reddit for grounded critique; Twitter/X for hype + direct feedback
- •Goal: build a tool that accelerates users rather than making next steps unclear
- 58:09 – 1:02:54
Why build a browser: contextual assistance, mixed-initiative UX, and user control boundaries
Alex explains the strategic rationale for Atlas: a huge amount of work happens in the browser, and owning the rendering context enables richer, safer “contextual actions” than relying on screenshots or accessibility hacks. The broader aim is mixed-initiative help that keeps users in flow—avoiding a future of endless push notifications.
- •A browser provides first-class context: the assistant can understand what you’re doing reliably
- •Avoids brittle approaches like screenshots/accessibility-tree inconsistencies across apps
- •Enables ‘contextual actions’ (video-game style) surfaced at the right moment in workflow
- •Better user control: open something in the AI browser when you want actions taken
- •Mixed-initiative UX reduces interruption versus constant proactive notifications
- 1:02:54 – 1:05:38
Getting started with Codex: give it the hard stuff, plan-driven workflows, and parallel trials
Alex offers practical advice: Codex is built for professional-grade hard tasks, not toy demos. Success comes from treating it like a new teammate—align on understanding, co-write a plan, then execute—and from trying multiple tasks in parallel to quickly build trust and intuition.
- •Best first test: a real, hard bug or complex task (within a single well-scoped request)
- •Language support follows real-world prevalence; most mainstream languages work well
- •Long tasks work better with a plan.md and verifiable steps
- •Tip: try a few things in parallel to build trust and learn prompting patterns
- •Treat Codex like onboarding a teammate: context → approach alignment → incremental delegation
- 1:05:38 – 1:13:30
The AI age: skills to lean into, on-call agents for training, and AGI via productivity hockey-sticks
In the closing stretch, Alex shares career advice (be a doer, strengthen systems thinking, use frontier tools) and describes early experiments with Codex supporting its own training operations (“babysitting” runs). He also offers an AGI-adjacent view: the key bottleneck isn’t compute, but human prompting/validation speed—and agents become transformative as they validate and act autonomously.
- •Career advice: maximize output with modern tools; build real things beyond homework
- •Enduring value: systems engineering judgment and team communication/collaboration
- •Frontier example: Codex writes and reviews infra code; early idea of Codex ‘on call’ for training
- •AGI timeline framing: productivity hockey-sticks start with early adopters, then spread to larger orgs
- •Underappreciated bottleneck: human typing/multitasking and manual validation/review speed
- 1:13:30 – 1:25:12
Hiring, lightning round, and where to send feedback
Alex notes the Codex team is growing and invites builders passionate about the future of agents to apply or reach out. The lightning round covers book and media recommendations, a “kind and candid” motto, and practical ways listeners can help: try Codex and share honest feedback.
- •Hiring filter: candidates should have a concrete opinion about the future of software work with agents
- •Lightning round: The Culture (optimistic AI sci-fi), Jujutsu Kaisen, Tesla UX as mixed-initiative inspiration
- •Motto/value: ‘kind and candid’ (candor as an act of kindness)
- •Where to find Alex: X/Twitter @embirico; feedback often seen via r/codex
- •Call to action: try Codex, share complaints/praise—team closely monitors real user feedback
