Codex started designing without asking for feedback like it normally does

Resolved 💬 2 comments Opened May 3, 2026 by PostTraumaticOS Closed May 3, 2026

What version of Codex CLI is running?

codex-cli 0.128.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.2-codex low

What platform is your computer?

MacOS

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

Codex has been acting weird for me lately, like it completely ignores the interactive back and forth I typically experience (in the sense that it is no longer a call and response interaction, it will just go on wild tangents without asking me for explicit feedback like it normally does) and was super wasteful of tokens over the past 2-3 weeks.

I dont know why this happens, but I use codex in a virtualized codespace environment because that seems to be the most deterministic and predictable over allowing codex to be on my local machine. Not sure why this is happening.

What steps can reproduce the bug?

Uploaded thread: 019dedae-bb57-7731-bf5e-ea78ae6a9568

Just interacting with Codex.

What is the expected behavior?

Call and response, asking permission before executing actions, asking which path I prefer, and overall collaboration vs brute force mistakes.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗