ABOUT CODEX · INDEPENDENT & UNOFFICIAL
Learn. Build.
Automate with Codex.
Practical guides, reusable resources, and clear reporting for people doing real work with Codex.
New here? Start with your first useful change ↗
AGENTS.md / REPOSITORY BRIEF
# Project briefing
Goal → One useful, reviewable change
Context → Read the project instructions
Scope → Keep the patch focused
Evidence → Run the relevant checks
Handoff → Explain the result & limitsAn example brief. Adapt it to your actual project.
YOUR NEXT USEFUL STEP
Pick a goal. Finish with something you can check.
Three short paths connect the guide, the skill, and a practice project.
Choose a learning path
Beginner · 3 lessons
Your first useful Codex task
Start with a clear brief, make one small change, and check the result.
Suggested practice: 30–45 minutes
Read → practise → verify
Open this path →WordPress · 3 lessons
Improve a WordPress page with evidence
Inspect a real layout, use a focused skill, and compare the result at two widths.
Suggested practice: 45–60 minutes
Read → practise → verify
Open this path →Developer · 3 lessons
Reproduce, fix, and verify a bug
Use a failing reading-list example to practise a complete debugging loop.
Suggested practice: 30–45 minutes
Read → practise → verify
Open this path →THE TOPIC INDEX
Explore more ways to use Codex
Already have a task in mind? Jump directly to a focused guide for planning, building, reviewing, debugging, or automating.
01
PLAN
Plan a project
Turn an unclear request into a brief with scope, constraints, and review evidence.
02
BUILD
Build with WordPress
Move from a page problem to editable blocks, responsive layouts, and accessibility checks.
03
REVIEW
Review code
Trace a change through its risks, CI evidence, release notes, and reviewer handoff.
04
SOLVE
Debug a failure
Reproduce the symptom, find the responsible layer, and verify the correction.
05
AUTOMATE
Automate repeated work
Schedule stable tasks with clear permissions, useful outputs, and meaningful alerts.
THE SKILL SHELF
A useful skill. A clear next step.
Start with a focused procedure. Review its requirements and evidence before using it.
Review a WordPress layout with evidence
Find layout problems across desktop and mobile, then connect each finding to a visible symptom and a focused fix.
Turn a request into a project brief
Define the outcome, constraints, and evidence for a focused change before implementation begins.
Verify a bug fix
Verify that a proposed fix removes the reported failure without creating an obvious regression.
FIELD NOTES / WORDPRESS
Behind the build.
Including the decisions.
Follow the AboutCodex redesign: the original layout, the changes to navigation and reading, and the checks behind the result.
THE NEWS DESK
What changed.
Why it matters.
Release notes, explained through their effect on your work.
- Codex CLI adds an experimental worktree flow
Sep 10, 2026 · What the September 9 CLI release changes, and what to verify before using it in a project.
- CLI plugin updates can refresh available tools and skills
Sep 10, 2026 · A short explanation of the plugin refresh change in CLI 0.154.0.