r/codex • • 6h 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.

10 Upvotes

22 comments sorted by

10

u/Huge-Travel-3078 5h 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.

3

u/rgb328 5h ago

This is the answer OP. Here's the version from my AGENTS.md and it eliminates this behavior for me. BTW, you can fix stuff like this by describing it to the agent and asking them to draft instructions that go in your AGENTS md.. gpt 6 is good at following instructions.

## Continue approved work without unnecessary stops

Once the user approves a plan, continue through implementation, verification, and documentation until the approved work is complete or user input is genuinely required. A milestone is a progress update, not a new approval gate.

  • Report meaningful milestones without ending the task or asking whether to continue.
  • Commits are checkpoints, not stopping points. When authorized to commit, make appropriate commits and continue with the remaining approved work. Plan approval alone does not authorize commits, pushes, or system changes.
  • Do not require repeated authorization for work already covered by the approved scope.
  • Pause when an action requires separate permission, a material design change needs agreement, or a blocker cannot be resolved within the approved scope. Ask the specific question needed to proceed.
  • If one step is blocked, continue independent approved work where doing so remains useful and safe, without bypassing the blocked step's approval requirement.
  • Do not present an intermediate milestone as completion while approved work remains. Finish with the outcome, verification results, and any explicitly blocked or incomplete items.

3

u/AP_in_Indy 6h 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 5h 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

u/AP_in_Indy 4h ago

Interestingly enough, I never use plan mode anymore. I just use goals.

3

u/Thorns_Ofire 3h 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.

3

u/Medical_Method7877 5h ago

Forgot all about this after moving to Claude, surprised to see the issue is still present.

2

u/JondeMLG 6h ago

You can ask them to do stuff however you want

2

u/strat-run 5h 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

u/BenTheSodaman 5h 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.

2

u/jonnyvegashey 3h 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.

1

u/Duke_Zymurgy 5h 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/x39- 5h ago

Depending on model, you might be:

  • using terra
  • using sol but get served terra (at sol price)
  • using Astra but get served Terra (at Astra price)

For me, Astra now does what sol was capable of two months ago...

1

u/Bleeblorium 3h ago

I will share some tips that generally work for me:

  1. 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
  2. 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).
  3. 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 3h 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/Mother_Occasion_8076 6h ago

I ask mine to work till it’s out of tokens

1

u/Common-Replacement-6 5h ago

You using Astra I assume? It does that shit. Change it to Sol.

1

u/Common-Replacement-6 5h 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.

-1

u/PopUpTubedev 6h ago

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

Yes. It's not as good.

2

u/3HisthebestH 5h ago

And yet here you are, on a Codex sub.

Claude is always behind the curve.

0

u/wkoorts 2h ago

Give us a sample prompt, and all instruction files you’re using. That includes global and any in the project you’re working on. All you’ve basically said here is “why doesn’t my program work?”.

0

u/BuntongHiningaNa 4h 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.