codex - 💡(How to fix) Fix Codex entered a documentation loop and became my project manager

What issue are you seeing?

Codex is the most realistic senior engineer simulator I’ve ever used.

You ask it to change one script.

Six hours later you have:

• 4 markdown files
• a migration strategy
• implementation philosophy
• updated handoff notes
• architectural considerations
• future roadmap ideas
• a rewritten TODO list

The script itself remains untouched.

At one point it literally explained, in detail, why modifying the file was the correct next step.

Then it opened another markdown file.

I’m no longer using an AI coding assistant. I’m managing a very talented employee who is deeply committed to documentation culture.

What steps can reproduce the bug?

Environment

• Codex Desktop App on Windows
• Large repo with docs/, scripts/, and markdown workflow files
• Long-running conversation/session

Reproduction Steps

1. Ask Codex to implement changes across a script-based workflow.

2. Codex begins creating and updating markdown files such as:

   • tasks.md
   • handoff.md
   • planning/spec documents

3. Later, explicitly instruct Codex:

   • “Only modify this one file”
   • “Do not write documentation”
   • “Directly edit the script”

4. Codex edits the target file partially, but then repeatedly switches back into:

   • status reports
   • implementation summaries
   • deployment notes
   • planning explanations instead of continuing execution or deployment.

Observed Behavior

Codex appears to enter a persistent planning/documentation loop.

Even after explicit instructions to:

• stop writing markdown
• stop planning
• only edit code

the agent continues generating:

• status summaries
• architectural notes
• rationale text
• “next step” explanations

instead of behaving like an execution-focused coding agent.

In multiple cases, Codex explained that deployment or execution was the correct next step, but still did not perform it.

Expected Behavior

Codex should:

• remain in execution mode after explicit user correction
• prioritize requested code modifications
• avoid repeatedly switching back into planning/documentation mode
• provide a clearer distinction between “planning mode” and “execution mode”

Additional Notes

This behavior seems more likely after:

• long sessions
• multiple markdown/spec files
• PowerShell workflows
• Windows desktop app usage

What is the expected behavior?

No response

Additional information

No response