OpenAI Codex, Day-to-Day

OpenAI Codex, Day-to-Day

Why this guide exists

You can use Codex every day and still miss what it added last month. You may never try the features that would help you most. Codex ships fast. This guide keeps you current, a few new techniques a day, so you do not get left behind and you use Codex the way it is meant to be used.

Who it is for

OpenAI Codex, Day-to-Day is a 17-day guide to Codex in the terminal and the ChatGPT desktop app. You need Node.js 22 or later, Git, and a ChatGPT Plus-or-higher account.

How it works

You build one small project, Ticket Triage, across every day. Each day starts where the day before ended and takes 20 to 40 minutes. Start here is a real lesson that ends in a result you can check, such as a passing test. Going deeper holds the explanations and alternatives for when you have more time.

What you will learn

  • Install Codex and make a first safe change (Day 1).
  • Run blocked-write and network probes in the sandbox (Day 4).
  • Put one rule in AGENTS.md and find it in the model input (Day 5).
  • Turn a readiness check into a project skill (Day 9).
  • Trust one hook and watch it protect a file (Day 12).
  • Split work across two worktrees, then hand one task to the cloud (Days 14 and 15).

The 17 days fall into five stages: getting started (Days 1 to 3), rules and boundaries (Days 4 and 5), context and settings (Days 6 to 8), extending Codex (Days 9 to 13), and scaling up (Days 14 to 17).

OpenAI Codex, Day-to-Day roadmap: Getting started, Day 1 Install and first safe change, Day 2 The daily loop, Day 3 Plan before you code. Rules and boundaries, Day 4 Permissions and the sandbox and Day 5 AGENTS.md that loads every time. Context and settings, Day 6 What Codex can see, Day 7 Models and cost, Day 8 Config and profiles. Extending Codex, Day 9 Skills, Day 10 MCP, Day 11 Subagents, Day 12 Hooks, Day 13 Plugins. Scaling up, Day 14 Parallel work, Day 15 Hand it to the cloud, Day 16 Without you, Day 17 Casual, pro, elite.

How it was tested

The Start here steps ran live on Codex CLI 0.169.0 in November 2026 on macOS with a ChatGPT Pro account. Day 15 Cloud results without a command trace are labeled Cloud-reported. A step that was not run for this guide, such as a desktop app step, is labeled Not run.

Get the code

Day 1 builds Ticket Triage by hand. The code is in the ticket-triage-day-by-day repository on the codex branch, with one tag per day, codex/day-00 to codex/day-17. Use a tag to catch up on any day.

Start

Start at Day 1, one part a day.

Also in this series: Claude Code, Day-to-Day, Cursor, Day-to-Day, OpenCode, Day-to-Day, Pi, Day to Day, and GitHub Copilot, Day-to-Day.

The parts

  1. Your First Codex CLI Change Should Be Easy to Check
  2. A Codex CLI Workflow You Can Review and Resume
  3. Revise the Requirement Before Codex Writes the Code
  4. Use a Blocked Command to Understand Codex Permissions
  5. Check That Codex Receives Your AGENTS.md Rules
  6. Check What Survives Codex Compaction
  7. Choose a Codex Model and Check What Usage Shows
  8. Save a Codex Review Profile and Verify It
  9. Build a Codex Skill You Can Inspect Before You Trust It
  10. Connect Codex to Documentation and Verify the Tool Call
  11. Use Codex Subagents for Two Reviews You Can Verify
  12. Test a Codex Hook With an Explicit Denial
  13. Install a Codex Plugin and Verify Which Skill Runs
  14. Keep Two Codex Changes in Separate Worktrees
  15. Hand Codex Work to the Cloud Without Losing the Evidence
  16. Run a Codex Readiness Check From a Script
  17. Build a Codex Routine You Can Repeat Tomorrow