Skip to content

Codex course · Included in Osum membership

Get PRs you’d merge from Codex.

You handed Codex a task and got back a confident summary, a green test run and a diff you don’t trust. The fix is not a longer prompt. Learn the Test-First Handoff: a brief with a done-when line, a failing test before the fix, and a review of what the tests missed.

  • Lesson 1: a real fix in your own repo, ready to commit in 14 minutes
  • By lesson 12: one real pull request you would merge, with what’s tested written down
  • Practice on a branch. Nothing is pushed, merged or deployed unless you choose to
Get my Codex plan About 2 minutes. Lesson 1 is a fix in your own repo you can check the same day.
Would you merge this PR? Try it first ↓
A developer chooses among local tools, close code inspection, and a separate configured workspace.
Lesson 1: Land your first fix today
12 hands-on lessons36 exercises1 certificate for LinkedIn30 courses in one membership

Sound familiar?

You wanted a teammate. You got pull requests to babysit.

“If I need to make iterative progress quickly, I literally can’t use it. It takes ten times longer to use than Claude.”

Codex user

“Yup, the coding stuff is just unreliable, but the reviews are nice work.”

Codex user

“Treating all agents as interchangeable caused real issues for me earlier on.”

Codex user

A longer prompt rarely fixes it. A handoff with a proof usually does. That’s the Test-First Handoff, and this course teaches it.

What you’ll be able to do

Hand Codex the task. Get back a PR you’d merge.

01

Land a real fix on day one

Pick the surface next to your code, commit a small fix from your own repo in your first session, and read every changed line before it lands.

02

Write a brief it can’t misread

A goal, context, constraints and a done-when line, so Codex builds what you meant and you can judge the PR in minutes.

03

Set your rules once

Your real test commands and do-not rules live in AGENTS.md, so every session starts where it should and nothing gets retyped.

04

Make the bug fail first

The Test-First Handoff: Codex writes a failing test before it touches the fix, so a green run finally means something.

05

Let it run without watching

Sandbox and approval settings that let Codex edit and test on its own, and stop before anything leaves your machine.

06

Review like it’s someone else’s PR

Use /review and your own read of the diff to find what the tests missed. The broken merge stops at your desk.

Try it before you sign in

Would you merge this PR?

You asked Codex to hide sold-out products on your shop page. Here are the products, the rules and the pull request it opened. Take a minute and decide.

The products in your shop

ProductStockPreorder
1. Canvas tote12No
2. Enamel mug0No
3. Wool beanie0Yes
4. Desk lamp3No
5. Gift cardNot trackedNo
  1. Rule 1: Sold-out products (stock 0) are hidden.
  2. Rule 2: Preorder products stay visible, even at stock 0.
  3. Rule 3: Products without stock tracking, like gift cards, always show.

The pull request Codex opened

Hide sold-out products. One-line fix in visibleProducts: the filter changes from stock >= 0 to stock > 0. New test: the enamel mug is hidden and the canvas tote still shows. 48 of 48 tests pass. Ready to merge.

Merge it, send it back, or merge part of it?

See what a checked review finds
  • Send it back. The tests pass, but they only check the two easy products.
  • The wool beanie is a preorder at stock 0. Rule 2 keeps it visible. This change hides it.
  • The gift card has no stock number. The new check hides anything without a number above zero, so gift cards vanish from the shop. Rule 3 says they always show.
  • 48 passing tests prove the 48 things they test. None of them covers a preorder or an untracked product.
  • What you can keep: the fix for the mug. Merge it once the PR also keeps preorders and untracked products visible, with a test for each.

That is the review the course has you practice on your own repo: a brief with a done-when line, a failing test before the fix, and a review that asks what the tests don’t cover. You finish with a real pull request of yours that you would merge.

Get my Codex plan About 2 minutes. Lesson 1 is a fix in your own repo you can check the same day.

Look inside

Every lesson is illustrated. No walls of text.

The curriculum

The Codex course: 12 lessons, one real pull request.

Osum’s Codex course is 12 hands-on lessons, about 3 hours 45 minutes in all. Lesson 1 is a 14-minute fix in your own repo, on a branch, that you can commit the same day. By lesson 12 you ship one real task from your backlog as a pull request you’d merge. You need your own Codex access. You finish with a certificate you can add to LinkedIn.

Module 01

Aim it at real work

Land a first fix, find where a bug lives and write a brief Codex cannot misread.

  1. Land your first fix todayPick the Codex surface that fits the job and get one small, real fix from your own repo ready to commit.
  2. Make Codex show where the bug livesGet a read-only map of one real bug in your repo, with a file and function behind every claim.
  3. Write a brief that gets a mergeable PRWrite a task for Codex with a goal, context, constraints and a done-when line you can check.

Module 02

Set the rules once

Repo rules in AGENTS.md, safe hands-off settings and a plan before big changes.

  1. Set the rules once with AGENTS.mdPut your repo’s real commands and do-not rules in AGENTS.md and confirm Codex loads them.
  2. Let it run without babysittingSet the sandbox and approvals so Codex edits and tests on its own, and stops before anything risky.
  3. Check the plan before a refactorUse plan mode to catch a wrong assumption before Codex rewrites working code.

Module 03

Fix it for real

A failing test first, the smallest right fix and a review that finds what the tests missed.

  1. Make the bug fail on commandGet Codex to write a failing test for a real bug before it touches the fix.
  2. Get the smallest fix that is rightGet a fix that turns your failing test green and changes nothing it did not need to.
  3. Would you merge this PR?Review a Codex change with /review and your own read of the diff, and find what the tests did not cover.

Module 04

Ship it

Skills for repeat jobs, parallel tasks with a reviewer and one real pull request you would merge.

  1. Save repeat jobs as skillsGive Codex the right context for today, and turn a job you repeat into a skill.
  2. Run two tasks at once, merge one resultRun parallel Codex tasks without collisions, use a second session as reviewer, and combine the results safely.
  3. Ship one real PR you would mergeTake one real bug, feature or refactor from your own repo from brief to a reviewed pull request you would merge.
Get my Codex plan About 2 minutes. Lesson 1 is a fix in your own repo you can check the same day.

Us vs. them

Why learn Codex here

The docs tell you what each command does. Video courses build a sample app on screen. This course takes a real task from your own repo from brief to a pull request you’d merge, with an exercise after every lesson.

FeatureOsum courseOfficial docsYouTube walkthroughsVideo course
A real task from your own repo, not a sample app✓✕PartlySample-app builds
Hands-on exercise after every lesson✓✕✕Follow-along videos
A worked example to check each exercise against✓✕✕✕
The failing test and the review, step by step✓PartlyPartly✕
Practice on a branch, nothing pushed or merged✓✕✕Partly
Certificate from a final check, one question per lesson✓✕✕Completion certificate
Every other Osum course included✓✕✕✕
Official, always-current commands and settingsLinks to them✓PartlyPartly
CostMembershipFreeFreePaid course

One membership

Learn Codex. Get every course with it.

The same membership covers Claude Code for a second agent in your repo, Grok Bot for a weekly research brief and Reasoning Skills for judging the numbers behind a change. Each course has its own certificate.

Certificate

Finish it. Prove it.

Show a manager, a client or a hiring team that you can hand Codex real work and merge what comes back. The certificate records a final check you passed, one question per lesson.

  • 12-question final check, one per lesson
  • Miss one? You see which lessons to review, then submit again
  • A public page you control, one click to add it to LinkedIn
  • Earn one for every course in the library

Questions

Before you start

How much does the Codex course cost?

One Osum membership covers the Codex course, its certificate and every other Osum course. It is a subscription. You see the price after your 2-minute plan, before you pay anything.

Do I need Codex to start the course?

You can start Osum’s Codex course right away, and the hands-on exercises need your own Codex access. It comes with ChatGPT plans: Plus is $20 a month, and Free and Go include lighter access in the desktop app (checked 28 September 2026). You also need a repo you can work in on a branch.

How long does the Codex course take?

Osum’s Codex course takes about 3 hours 45 minutes: 12 lessons, starting with a 14-minute fix in your own repo that you can commit the same day.

I’m not a senior engineer. Can I do the Codex course?

Yes, if you can read a small function, use Git branches and run your project’s tests. You don’t need to know Codex already. You do need to read a diff, because the course teaches you to judge one.

I already write detailed prompts for Codex. Why would this course work?

Osum’s Codex course adds what prompts leave out: a done-when line Codex can build to, and a failing test a fix has to turn green. You practice on a real task in every lesson, with a worked example to check against, and finish with one pull request you would merge.

Will the Codex course make Codex faster?

No: no course changes how fast the model answers or your plan’s usage limits. You learn which jobs suit a fast loop, and the Test-First Handoff that cuts the rounds on the jobs you hand over.

Is the Codex course made by OpenAI?

No. Osum is independent and not affiliated with OpenAI, and the certificate is an Osum certificate.

Keep rewriting Codex’s diffs. Or merge work you’d have written yourself.

The Test-First Handoff is four habits: brief it once, make it fail first, keep the fix small, review what the tests missed. You get a real fix in lesson 1 and a pull request you’d merge by lesson 12, with a certificate and every other Osum course. A few quick questions, then your plan.

Get my Codex plan About 2 minutes. Lesson 1 is a fix in your own repo you can check the same day.

Keep exploring

Related learning paths

Learn a useful skill. Put it to work.

Practical courses for AI tools and skills. Course and tool names are the trademarks of their respective owners; Osum is independent and not endorsed by them.