Codex frequently responds to the wrong message or drops messages (after compaction?)

What version of Codex CLI is running?

codex-cli 0.116.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4 high fast

What platform is your computer?

Darwin 25.3.0 arm64 arm

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

Ghostty

What issue are you seeing?

This happens to me a lot:

Me: why did you do it this way? Codex: I did it because \<blah blah explanation\> Codex ends turn Me: okay, good. now can you \<blah blah new ask\>? Codex: I'm on it Codex: does some tool calls etc ... Codex: I did it that way because \<repeats explanation\> Codex ends turn Me: yes, we've been over this - why aren't you doing the new ask?

It's not totally clear to me, but this might be happening over compaction boundaries?
Has reproed both in CLI and app.

What steps can reproduce the bug?

Uploaded thread: 019d251e-554f-77b3-aa06-dd7be94e8286

In this thread, Codex reproed the bug and I asked it why it did this, and it clearly had the order wrong and thought I'd ask the question last. I asked it to repeat back the messages it had from me and it completely dropped the question that time. So the harness is clearly not persisting history correctly and is sometimes changing order or dropping messages.

What is the expected behavior?

It should respond to the correct message.

Additional information

This might be involved in the common feeling that Codex is blowing through quota at light speed all of a sudden. Presumably mixing up the message order will invalidate prefix caches.