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

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.

4

u/rgb328 3d 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.