Grab my Ultimate Guide to Codex and catch up to the 1 in 1,600 people using it every week (mostly no code!))

I’m going to skip the wind-up on this one.

Codex just passed five million weekly active users. That’s OpenAI’s own count, from its June 2 report on knowledge work. Run that against eight billion people and you get six hundredths of one percent, about one in every 1,600 humans alive. Be generous and count only the world’s billion or so knowledge workers, the audience this tool is quietly turning into, and adoption is still about half a percent. Most of those five million are still developers, which only widens the gap I actually care about. And every week I watch what that sliver gets done — pages shipped, pipelines run, whole jobs handed to a computer and handed back finished with receipts — and then I read my inbox, full of smart, capable people describing work that feels heavier every month, and the distance between those two experiences gets to me.

So here’s the closest I will ever come to yelling in this newsletter: use Codex.

Not “consider an agentic workflow.” Not “explore the space when things calm down.” Things are not going to calm down. Use Codex. It is the best daily driver in AI right now, it is absurdly underused, and the gap between the people running it and the people who haven’t touched it is the most fixable gap in your entire working life. It is not a talent gap. It is not a technical gap (most of what’s in this piece requires zero code). It is a setup gap, and a setup gap closes in a weekend.

That’s what this piece is: the catch-up. I just published the complete operating guide to Codex (every habit, every prompt, every skill I actually run), and below I’m going to walk you through all of it, because five million is an embarrassing number and I intend to move it.

Here’s what’s inside:

• The Ultimate Guide to Codex. Go from “I should really learn this” to a working setup in a weekend, with the model wired into your actual files and pages instead of sitting in a chat tab. Every page is a copy-paste prompt, most needing zero code.

• The shift worth making. The unit of work moved from the prompt to the run, and there’s a one-paragraph test for which side you’re working on.

• Why you’re not actually behind. The gap isn’t facts, it’s setup: the difference between a problem that compounds and one you can close on purpose.

• Where to actually start. A first day, first week, and first month, built on one real folder, one small job, and proof you can check.

It’s one honest weekend wide. Below is the whole thing, start to finish. But first, let me make the case for why Codex specifically.