Back to Podcast Digest
Every7m

Codex Runs My Inbox Now

TL;DR

  • Codex cut his inbox to 30 emails by 2:00 p.m. and kept him at inbox zero for 13 weeks: He says that has never happened before, and credits Codex for handling the scheduling, triage, and reply drafting he used to procrastinate on.

  • The workflow is a custom app he "vibe coded" inside Codex: The app sweeps email a few times a day, turns each message into a card, summarizes it, drafts a reply, and lets him approve or edit actions by talking naturally.

  • Codex has browser access, app access, and calendar context: In examples, it proposes Brooklyn meeting locations, drafts sponsorship replies for Every, and suggests times for Greg Eisenberg because it can see the calendar.

  • He uses the same card-and-queue system beyond email: A separate company feed pulls from Notion meeting transcripts and Slack across a 30-person company, then flags what he should review, what Codex should do, and what is already handled.

  • The system learns from his decisions because everything is stored on the file system: Archive choices, reply patterns, and prompt tweaks are recorded so the app gets better over time at hiding noise and choosing the right next action.

  • He shows the build prompt and says nontechnical users can make this too: His recipe is to ask Codex to build an end-to-end inbox sweep app, run it in auto-review mode on 5.5 with extra high, and let Codex define a detailed goal plus validation steps.

The Breakdown

Inbox zero for 13 straight weeks is the headline, but the real trick is a Codex-native app that turns every email into a card with a drafted next action, then executes the work after a quick human pass. The same setup now filters company meetings, Slack debates, and follow-ups, so Codex acts less like a chatbot and more like an always-on operator inside the browser.

Was This Useful?

Share