Codex replies to earlier messages instead of latest one in conversations

[BobbyWang0120]

What version of Codex is running?

0.77.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.2-xhigh

What platform is your computer?

No response

What issue are you seeing?

In multi-message conversations with Codex, the assistant sometimes responds to an earlier message instead of the most recent one. For example, I had a conversation with six messages. By the sixth message, I had moved on to asking a different question, but Codex's final summary acted as if it was still on the third message. The third message asked about a question A and its solution, while the sixth asked about question B. Even though the topic changed at the sixth message, Codex still responded about question A. This happens frequently and suggests that Codex may be referencing the wrong message in the conversation history.

What steps can reproduce the bug?

1. Start a conversation in Codex and send several messages (e.g., six messages).
2. In an earlier message (e.g., the third message), ask question A and wait for a response.
3. In a later message (e.g., the sixth message), ask a different question B.
4. Observe that Codex's summary or response refers back to question A rather than answering question B.
   This suggests that Codex is using the wrong message as context.

What is the expected behavior?

Codex should respond to the current message, acknowledging the latest context. After a user moves from question A to question B, the assistant should answer question B and not revert to a previous question. The summarization should maintain the correct message pointer in the conversation.

Additional information

the pattern is randomly happening, and it has a higher chance to happen after we compacting the context within the conversation

[g3grau]

I also frequently see this behavior. Codex repeats previous responses (at least 1) although it didn't work on the same topic in the last task. Here, too, it is in the context of a huge project (GPT-5.1-Codex-Max with High effort, Local Agent mode, ~60% context window. I never tried to "compact the context" (didn't even know that this is possible)

[etraut-openai]

Please use the /feedback slash command to upload your session and post the thread ID here.

[MineshK]

I've been seeing this too - only since updating to the latest version of the plugin.

My feedback thread ID: 019b1a35-5b10-7741-93bb-58589661a52c

[sayan-oai]

Thanks for reporting. We are aware of this issue with compacted conversations and are working on a fix.

[STAlfsen]

Reporting the same issue after a session where it was particularly bad. In my experience Codex has been bad at tracking which questions are "new" and which issues it has already responded to even in its early days. It has been quite typical to see conversations of this style as long as I have been using Codex:

User - Fix issue A
Codex - Fixed issue A
User - Fix issue B
Codex - Fixed issue A. Fixed issue B.

I have never seen the same issue with other agent harnesses, although I have not really explored codex models through Cursor for instance. It also now seems to worsen after compaction (I would rarely let conversations run to the point of compaction before, so unsure if recent changes to compact earlier is just making this problem more visible).

Submitted the conversation through /feedback with the following tracking number:
019bdad1-8b88-7c82-bd9e-48a0b4ba835f

[sentialx]

Yeah after summarization, the chat is unusable and the model just loses context or fixes previously fixed bugs

[alc1986]

This issue is getting worse and worse all the time. It's made 5.3 pretty much unusable.

[svendvd]

I’m seeing the same issue since 0.98. It’s burning through my Pro limits, roughly 0.5–1% of the weekly limit per prompt.

Yesterday, a very small change took 23 minutes and modified ~20 files instead of a single line. Most of those edits were redundant (same change repeated with only minor style differences).

Right now, it’s completely unusable with gpt-5.3-codex and barely usable with gpt-5.2-codex.

If this isn’t fixed ASAP, I’ll have to switch to Claude or Gemini. I’m a big fan of Codex, but I need a tool I can actually ship work with.