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.
Codex course · Included in Osum membership
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.

Sound familiar?
“If I need to make iterative progress quickly, I literally can’t use it. It takes ten times longer to use than Claude.”
“Yup, the coding stuff is just unreliable, but the reviews are nice work.”
“Treating all agents as interchangeable caused real issues for me earlier on.”
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
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.
A goal, context, constraints and a done-when line, so Codex builds what you meant and you can judge the PR in minutes.
Your real test commands and do-not rules live in AGENTS.md, so every session starts where it should and nothing gets retyped.
The Test-First Handoff: Codex writes a failing test before it touches the fix, so a green run finally means something.
Sandbox and approval settings that let Codex edit and test on its own, and stop before anything leaves your machine.
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
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.
| Product | Stock | Preorder |
|---|---|---|
| 1. Canvas tote | 12 | No |
| 2. Enamel mug | 0 | No |
| 3. Wool beanie | 0 | Yes |
| 4. Desk lamp | 3 | No |
| 5. Gift card | Not tracked | No |
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?
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.
Look inside








The curriculum
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
Land a first fix, find where a bug lives and write a brief Codex cannot misread.
Module 02
Repo rules in AGENTS.md, safe hands-off settings and a plan before big changes.
Module 03
A failing test first, the smallest right fix and a review that finds what the tests missed.
Module 04
Skills for repeat jobs, parallel tasks with a reviewer and one real pull request you would merge.
Us vs. them
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.
| Feature | Osum course | Official docs | YouTube walkthroughs | Video course |
|---|---|---|---|---|
| A real task from your own repo, not a sample app | ✓ | ✕ | Partly | Sample-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 | ✓ | Partly | Partly | ✕ |
| 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 settings | Links to them | ✓ | Partly | Partly |
| Cost | Membership | Free | Free | Paid course |
One membership
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
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.
Questions
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.
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.
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.
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.
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.
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.
No. Osum is independent and not affiliated with OpenAI, and the certificate is an Osum certificate.
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.
Keep exploring