Bonus week just added - 7 extra Codex lessons covering Hooks, MCP, AGENTS.md, context, permissions, diff review, and safety rules.
Jump to Bonus WeekMaster ChatGPT Codex in 21 Days
10-15 minutes a day. One safe task. Real progress. No coding experience needed.
10-15 mins/day
Short enough to fit into any schedule
Built for non-developers
Starts from absolute zero
Safety-first workflows
Review, verify, and recover before you accept changes
28 lessons total
21 main lessons plus 7 bonus power-user lessons
A calm, safe path from first prompt to real project changes.
Each lesson is built for non-developers. Open Codex, ask for a plan, review the diff, and move one step at a time.
Setup and First Safe Wins
Install Codex and run your first safe prompt
Install Codex, sign in using the easiest current path, and run one safe prompt without changing files.
ChatGPT vs Codex - know which tool to use
Using the wrong tool for the wrong job wastes time and causes mistakes. Today you learn the one simple rule, walk through three worked examples, practice classifying real tasks, and run the two-tool workflow from idea to safe Codex prompt.
Plan Mode - make Codex think before it builds
Learn how to ask Codex for a written plan before it touches any file, how to read and evaluate that plan, and how to reduce it if it looks too large.
Open a project without breaking anything
Find the correct project folder, open a terminal inside it, and confirm you are in the right place before Codex touches a single file.
Approval modes - when to use Suggest, Auto Edit, and Full Auto
Learn the current approval modes in Codex, when each one is safe, and how to stop a run immediately if something looks wrong.
Read Codex output without panicking
Learn to read terminal error messages calmly, find the useful line quickly, ask for an explanation before anyone tries to fix anything, and save an error record you can use if the first fix attempt fails.
Week 1 build day - one safe homepage change from start to finish
Today you use everything from Days 1 to 6 together on one real task. You will pick one small visible change, ask Codex to plan it, approve only what you understand, preview it in your browser, check the diff, and save only when it looks right.
Building Confidence
The AGENTS.md file - give Codex permanent project rules
Every Codex session starts fresh with no memory of your project. Today you create one file that fixes this — AGENTS.md. It sits in your project folder and tells Codex exactly how to behave before it touches a single file. You will create it, paste a starter template, and confirm Codex actually reads it.
What to put in AGENTS.md so Codex follows your rules every session
Learn the six essential sections of a strong AGENTS.md, study a complete working example, customise at least one rule for your project, and confirm Codex reads it accurately.
Slash commands - how to find and use shortcuts safely
Codex has a set of slash commands — shortcuts you type starting with "/" that control the session. Today you learn how to find the commands available on your version of Codex, identify which ones are safe for beginners, try two of them, and build a personal cheat sheet. Important: command names can differ between Codex versions, so today you learn how to find your local list rather than memorise a fixed set.
Permissions and approvals - do not let AI run wild
Learn how to read permission prompts, approve only what you understand, point Codex at the right file before it starts, and reject or revise actions that are too broad.
How to review a diff before accepting changes
Learn to read what Codex actually changed, spot unexpected edits before committing, check user-facing text, and handle the case where two sessions may have touched the same file.
When Codex goes wrong - the exact recovery process
Learn what to do the moment something breaks: stop immediately, collect the right information, build a recovery summary, use GitHub Desktop to undo safely, and know exactly when to stop trying to fix and start fresh.
Week 2 build day - add a contact section with no backend email sending
Today you use the full safe Codex workflow to add one real feature: a simple contact section. No email sending. No backend. Just a visible contact section with your details or a basic form that does not submit anywhere yet.
Power User Moves
Codex skills - reusable instructions for repeated work
Build a reusable instruction block for one repeated task, store it somewhere you can find it, and test it on a live example.
Create your first personal Codex workflow
Build one complete reusable workflow from scratch — a pre-session checklist, a standard opening prompt, and a closing report request — then test it on a small real task so you know it works before your next session.
Big-build planning - handle complex multi-file tasks safely
Day 3 taught you how to ask for a plan on a small task. Today you handle something bigger — a feature that touches multiple files across multiple phases. You will learn how a big-build plan looks different from a small one, how to spot when a plan is too large, and how to split it into phases you can approve one at a time.
GitHub safety - branches, commits, and how to undo changes
When Codex changes files, those changes happen directly on your computer. Without GitHub, one wrong Codex session could overwrite weeks of work with no way back. Today you learn to use GitHub Desktop — the safest, most visual way to manage your project — to create branches, commit working changes, review what Codex did, and safely undo changes when something goes wrong.
Use Codex for SEO fixes, UI fixes, and bug fixes
Learn three of the most common Codex job types: improving one SEO element, fixing one visible UI problem, and diagnosing one bug. Each job type needs a different prompt structure — today you build and use all three.
Build your pre-session safety checklist
Create the complete pre-session safety checklist you will use before every Codex session for the rest of your building career. By the end of today, the checklist is saved, tested, and added to AGENTS.md.
Final build day - plan, build, test, and ship one real improvement
This is the last day of the challenge. Today you use every skill from all 21 days together — on one real, small improvement that you will take from an idea all the way to a tested, committed result. You will plan before building, approve only what you understand, preview on desktop and mobile, check the diff, and write a short summary of what you shipped and what safety habit helped you most.
Power user moves
Free bonusSafe automation in Codex - use repeatable commands, not mystery hooks
Current Codex docs emphasize clear rules, reusable skills, MCP, and helper commands - not hidden hook workflows. This bonus lesson teaches the safer automation building blocks a non-developer can actually understand and review.
The context window - why long AI sessions drift and how to reset safely
Learn to spot the warning signs of a drifting Codex session, stop before damage happens, write a handoff note, and restart cleanly.
The AGENTS.md checklist - rules every Codex session should follow
Upgrade your AGENTS.md from a basic starting file to a strong permanent safety contract — covering identity, design quality, validation, and final reporting.
What MCP is and how to connect Codex to one safe tool first
MCP lets Codex connect to external tools and services. That is powerful and risky. This lesson teaches you what MCP is, how to inspect your current setup, and how to start with one official read-only server before you connect anything stronger.
Specialist role prompts - how to give Codex one job at a time
A role prompt turns Codex from a general assistant into a focused specialist for one task. This is prompt structure, not the separate OpenAI Agents product. This lesson teaches you what a role prompt means, shows you three real examples, and gives you a copy-paste template for creating your own specialist prompts.
Permissions and safety rules before you let Codex touch your files
Before Codex edits any file, you should pass four checks: task clarity, file list, risk level, and a final approval decision. This lesson teaches you a visible risk scale, exact approval and rejection prompts, and how to ask for a smaller plan when a task feels too large.
How to read a diff - and why you must before accepting any change
A diff shows you exactly what Codex changed — line by line. Reading it is the most important habit a non-developer can build. This lesson teaches you what the symbols mean, which areas are scary to change, how to spot unwanted edits, and how to ask Codex for a targeted revert.
FAQ
Common questions.
Is Codex good for non-developers?
Yes. It works best when you want AI to make changes inside a real project while you stay in control, review the plan, and check the diff before accepting anything.
Do I need to know coding to use Codex?
No. You need enough confidence to open a project, describe the result you want, and verify the changes. The challenge teaches that from zero.
What is the difference between ChatGPT and Codex?
ChatGPT is the general assistant for thinking, writing, and planning. Codex is the tool focused on working inside your project files, making changes, and showing you what changed.
What is the difference between Codex and Claude Code?
Both can help you work on real projects. The practical difference is workflow and preference: some people like Codex inside ChatGPT, while others prefer Claude Code. This challenge helps you understand when each one fits best.
Can Codex build a website for me?
Yes. It can help create, edit, and fix a website. The safe way to use it is in small steps, with a plan first and a diff review before you accept any change.
Is the 21-Day Codex Challenge free?
Yes. This landing page and course outline are free to read.
Get your access code now
Free. No payment. Sign up and we email you a code that unlocks all 21 days online.
Keep learning