[Bug] With ~1M context and ~70% usage, asking a new question can make Codex answer the previous question instead of the new one

What version of the Codex App are you using (From “About Codex” dialog)?

26.325.31654

What subscription do you have?

PLUS

What platform is your computer?

Windows

What issue are you seeing?

Summary

When using a very large context window (~1M context), and the usage meter is around 70%, asking a new question may cause Codex to respond to the previous question instead of the newly submitted one.

As a result, the new question appears to be ignored or not visible in the response flow.

Steps to reproduce

1. Start a long Codex session with a very large context (~1M context).
2. Continue using the session until the usage indicator is around 70%.
3. Ask a completely new question.
4. Observe Codex's response.

Expected behavior

Codex should answer the newly submitted question.

Actual behavior

Codex sometimes responds to the previous question instead of the new one.
The new question is effectively not reflected in the response.

Workaround

If I ask the new question again, Codex usually responds correctly on the second try.

Frequency

Intermittent, but reproducible in large-context sessions.

Additional notes

• This seems related to very large context usage.
• It may be a context-selection, message-ordering, or stale-thread-state issue.
• The issue is especially noticeable once usage reaches around 70% in a ~1M context session.

This causes confusion because Codex appears to ignore the latest user message and instead replies to an older one.
Also, is there any planned timeline for Codex support on mobile (iOS/Android)?

What steps can reproduce the bug?

1. Start a long Codex session with a very large context (~1M context).
2. Continue using the session until the usage indicator is around 70%.
3. Ask a completely new question.
4. Observe Codex's response.

What is the expected behavior?

_No response_

Additional information

_No response_