How to set up Codex
6 steps, about 10 minutes today, then a week of checking. We put the approvals on before anything else.
Pick where to use it
The ChatGPT app is the gentlest start. The CLI and code editor extension suit developers.
Protect your work first
Work in a project tracked in Git, with everything committed, so you can undo any change. Keep its default approval mode, and don't switch to full access or any mode that skips approvals.
Start in a real project
Point it at one repo you know well.
Ask before it changes anything
Start by asking it to explain the codebase.
Read this repo and explain how it's put together. Then suggest the smallest change that would fix this problem. Don't make changes yet.Give it a way to check
Tell it which command proves the work is right.
End in a pull request
Keep a person on every merge.
Our stake: Navigate helps clients set up agents like this one. Claude helps research and draft this site, so a person reviews this page. How we work
Codex is set up.
Now give it one week. This plan keeps it safe and useful.
- Day 1Try your first jobAsk it to explain your codebase, using the prompt below.
- Day 2Fix one small thingPick a small bug, and read every change before you accept it.
- Day 3Check its workRun your tests, and ask which command proves the change works.
- Day 4Let it open a pull requestOne small change, which you review and merge yourself.
- Day 5Write down what it got wrongAdd those lessons to your project rules file.
- Day 6Read what it didLook back over its changes and the commands it ran.
- Day 7DecideKeep it, change how you use it or stop. Then pick job two.
Your first job
Read this repo and explain how it's put together. Then suggest the smallest change that would fix this problem. Don't make changes yet.