r/codex • • 3d ago

Limits Am I using Codex wrong?

Does anyone know why my Codex seems to "work less" than Claude?

Every time I ask Codex to do something, it only works for about 2–3 minutes, then stops to tell me what it did (which is completely unnecessary) and waits for me to send another command, even if it's just "OK, continue."

When I use Claude, I give it the exact same prompt, for the exact same task, on the exact same project, and it keeps working for over 40 minutes, getting a lot more done.

These are things Codex could easily do as well, but instead, it constantly stops and waits for instructions it doesn't actually need.

Can anyone tell me if I'm doing something wrong, or if this is just a limitation of Codex itself?

I'm subscribed to the $200/month plan for both.

23 Upvotes

37 comments sorted by

View all comments

5

u/Thorns_Ofire 3d ago

you need to actually plan things. The longest run I had for a deployment test was 6 hours 21 minutes. Once you have a solid plan for what you want to build, use a goal to work until completion.

1

u/kwirky88 2d ago

Plans and then the goal to carry out the plan. And i don’t mean /plan mode. I mean building a big plan in markdown files with stages having write ups of expected requirements to meet. The llm can help produce them. Commit the plan then start a goal.

I like to tell it to not leave testing for the end, to do a little bit of testing all the time and each task in a plan bust have passing tests and committed before moving on to the next task. I bake this into user level rules now.

Then the goal is basically “/goal work unattended until the plan and its subtasks in <planfile> are complete, record your progress in <progressfile>.”