How I use Codex:
step 1:
- Setup GPT-5.2-XHIGH and tell it to read every files under what directory I want to work in
- Have it produce a map of the code, and a scope that is relevant to the big goal I want to accomplish
- Have it make a directory called /tasks where it makes 1 https://t.co/d9GHgqU4NH file in a sequence
step 2:
- Switch to gpt-5.2-codex-xhigh
- Attach the scope, the rules, and the https://t.co/d9GHgqU4NH
- Push the same message but change the number https://t.co/aqxZlaiq3F
The scope is the big picture. What we are trying to do, what it touches, why we made certain decisions etc..
The rules file is the instructions it has to follow during development:
1. checkout new branch when starting a task
2. complete the task as described, attempt to reduce code not make more for older projects.
3. run type-check, lint, full test suite (not deleting or skipping tests), commit and push
4. update documentation
Each task will take between 15 minutes and 1 hour, you can stack them on top each other so codex only sees 1 per turn.
2-24 hour runs depending on how well you specify
all code is typically functional
improved, cleaner code,
alright, Hamster family
we havenโt chatted in a while
what have you been up to? share in the comments ๐
..and remember: the โwen listingโ reply is getting old ๐
weโre working on it, okay? and youโll be first to know! ๐๐น๐ซถ๐ฝ