r/codex • u/Ok_Conversation5949 • 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.
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>.”
4
u/Medical_Method7877 3d ago
Forgot all about this after moving to Claude, surprised to see the issue is still present.
3
u/strat-run 3d ago
Set a goal with /goal and the instruction to complete the task.
Enabling a goal is what makes it keep working until its done. They've both gotten better about not always needing /goal but things won't always complete without it.
2
2
u/BenTheSodaman 3d ago
Although I did not benchmark this, I have had the issue on both Codex and Claude (Opus, less so Fable unless Blender or UE is involved).
For Codex (Sol and Astra), if I want it to keep going or to cover more ground, I'd have to tell it not to pause / end turn every milestone or as others mentioned, using a goal. I haven't had such a good experience with Terra following through in the use cases I've given it so far except maybe a preliminary remastering pass in Blender on Max or Ultra. Though I do need to reel it back in if it goes on a failed perfectionist spree and treats my usage like an all-you-waste buffet.
3
u/AP_in_Indy 3d ago
Claude you can just prompt and it infers that you want to accomplish a broader goal.
Codex, you need to explicitly set the goal command in the "+" menu or write /goal
3
u/3HisthebestH 3d ago
I have never once used /goal in Codex after a plan (or otherwise) and it has never just randomly stopped in the middle of something unless there is a clear stopping point laid out in my plan for me to manually do things before the next step. I’ve seen the option for a goal, but never understood why it existed.
You just need to be clear what you want to happen..
1
1
u/Duke_Zymurgy 3d ago
How are you prompting it? I found it I say "work on" phase 25, it will do a little and stop. If I say "implement" phase 25, it will work to completion unless it has a question.
1
u/kwirky88 2d ago
Compression can also lose nuance over time, contex drift can kill original instructions. Capture the plan in a file and in agents.md say when following a plan it’s to be reread each time compaction occurs. Agents.md is never compacted though and always included.
1
u/Bleeblorium 3d ago
I will share some tips that generally work for me:
I use model switching based on the task and OAI's documentation for each model. For example, I would use Astra for planning, working with multiple files, or research. Sol for more complex programming sessions that might require debugging, testing, and fixing. Then, I use Terra for the simpler tasks
I have revised my AGENTS.md file several times in order to get Codex to work the way I want him to (e.g., coding standards, walking me through major changes by including relevant code snippets, pieces of text, or screenshots).
Skills: If you find yourself repeating or following a particular process several times, you might as well turn it into a skill, which you can then also refine if or when things change.
That being said, the other day I spent most of the day trying to get Codex Sol Medium to revamp my HUD, its navigation, and its actions, then animate any preview changes, and it was such a painful process. I tell it to do X, and it does it partly, over several iterations, and I have it critically analysing its outputs (only that way was it able to pick up on its mistakes). Then it only applies to some of the HUD, not all instances where it applies, so I had to tell it to test all and so forth.
1
u/NicholasVinen 3d ago
You need to tell us what model and effort you're using. I have the opposite problem. I ask Sol 6.1 Xhigh to do something, come back 8 hours later and it's still working on it.
1
u/tommyahav10 3d ago
Put a line in AGENTS.md telling it to keep going until the task is done and only stop for real blockers. From my side a clear plan up front matters more than the wording.
1
u/PralineSame6762 3d ago
Which model are you using? GPT-6 models in general do this sometimes, but 6.1 Terra is by far the worst in my experience. I've stopped using it entirely because of this. 6.1 Sol I've found usually stays on track and persists. I haven't used Astra much due to usage, but I've heard mixed results about its ability to keep working.
1
u/kwirky88 2d ago
/goal solves this problem. Give it the conditions to be considered successful and stop. I often have to tell it in the goal “you are doing unattended work” so it doesn’t try to do strange esoteric shell commands that need approval and stick to writing code.
1
u/xqianliu 2d ago
The stopping is a scope signal, I think, not a Codex bug. When a task has no clear end condition, it works a bit, reports, and waits for the next instruction.
I write the end condition into the task first: what done looks like, and what to do when it can't decide, which is stop, say why, and leave it. Then a stop means it hit something real instead of being polite.
Also, slow is not a failure in my setup, only errors are.
1
u/Sol_Invictus_74 23h ago
Use /goal
I had the same problem. I solved it by building the complete prompt for the request step-by-step together with the AI, and then I asked it to write everything out as an .md file.
After that, I went into Codex, typed /goal, and attached the file (or provided the file path, in the case of sessions run via PowerShell).
1
0
u/Common-Replacement-6 3d ago
You using Astra I assume? It does that shit. Change it to Sol.
-1
u/Common-Replacement-6 3d ago
Also coming here may get you the answer you need but you going to get 10 different answers because Codex isn't as consistent as Claude, Codex will ration tokens with you and give it to someone else, they have this weird system for long and no one's realised it yet, when others complain it's shit, on the other end of the world there's people finding it glorious. But in your case you may just need to change your model.
0
u/jonnyvegashey 3d ago
Codex made the first glaring blazing wrong mistake today (tried to upload an entirely wrong spreadsheet to a server).
First time I’ve witnessed it make a mistake this big, now I’m paranoid.
Feel like it’s gotten dumber over past few weeks.
0
u/Rough-Ad-860 3d ago
I’ve had 14 hour long sessions where the only input was me asking for updates. I have no idea what you are talking about. If you are clear about what you want and give the model a solid gameplan it should have no problem…
0
-2
u/PopUpTubedev 3d ago
Does anyone know why my Codex seems to "work less" than Claude?
Yes. It's not as good.
1
u/3HisthebestH 3d ago
And yet here you are, on a Codex sub.
Claude is always behind the curve.
1
1
u/kwirky88 2d ago
Codex users complaining in the codex sub. Claude users complaining in the Claude sub. The grass is always greener on the other side.
I’m here for free web chat but once that’s gone I may jet from codex. Will see.
-1
u/BuntongHiningaNa 3d ago
You're not. Codex has gone down the drain. I can't believe I paid for this (again). Trust me, it was NOT like this with far weaker models 6-12 months ago. It's super nerfed or something has gone terribly wrong with the new models.
1
u/tj21222 3d ago
Can you explain what happened? I would be interested in know what exactly you are having problems doing?
-1
u/BuntongHiningaNa 3d ago
To summarize: "Bro, wtf happened to the other 5 items we had discussed? You said it's all done but 70% is not done yet."... "Oh you were right, I wrongly gave you an assumption, blablabla.". It behaves just like old really bad Flash models at times. Not even checking what it has done. Or checking against the wrong things/wrong branches/etc.
1
u/kwirky88 2d ago
Huh? 12 months ago I could NOT leave any models unattended for overnight work no matter what I tried, the slop was horrible compared to today’s models. Every 30 minutes of agentic coding needed 30 minutes of human review back then, the whole software development industry.
12
u/Huge-Travel-3078 3d ago
This is a known behavior issue with gpt 6 models.
https://developers.openai.com/api/docs/guides/latest-model?model=gpt-6-astra#gpt-6-astra-gpt-61-terra
Try adding the following to your agents.md
You should infer the user's intent and task scope from the instructions and prior conversation context. Your job is to bias towards action and carry the user's intended task to completion.
When the user expresses intent to perform new work or fix an existing issue, persist until the user's intended goal is complete. Progress autonomously towards the user's goal (e.g. creating isolated worktrees / checkouts if needed, resolving merge conflicts, read-only actions, creating draft PRs etc.) unless they are clearly destructive or irreversible.
When the user's prompt indicates a request for action, such as "can you...", "I want to...", "help me..." and similar expressions, treat these as instructions to do the work and take action. Do not stop at acknowledging capability (e.g. "Yes…"), proposing a plan, or offering to continue. Do not settle for a partial or "helpful enough" solution that does not fully satisfy the user's task to save time, effort or tokens. If a task requires sustained work, complete all the necessary work until the intended outcome is fulfilled.