Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix [Bug] With ~1M context and ~70% usage, asking a new question can make Codex answer the previous question instead of the new one [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18257•Fetched 2026-04-17 08:30:44
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
kkx9578kkx9578
Participants
etraut-openaietraut-openaigithub-actions[bot]github-actions[bot]kkx9578kkx9578
Timeline (top)
labeled ×5commented ×2closed ×1unlabeled ×1

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.

Root Cause

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)?

Fix Action

Workaround

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

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Asking a new question again usually resolves the issue, as it prompts Codex to respond correctly on the second try.

Guidance

  • The problem seems related to large context usage, specifically when the usage meter is around 70% in a ~1M context session, suggesting a potential issue with context selection or message ordering.
  • To mitigate the issue, try asking the new question again, as this usually results in Codex responding correctly on the second attempt.
  • It might be helpful to monitor the usage indicator and context size to see if there's a pattern to when the issue occurs, potentially allowing for more predictable workarounds.
  • Consider breaking down large context sessions into smaller, more manageable parts to reduce the likelihood of encountering this issue.

Example

No specific code snippet is applicable in this scenario, as the issue appears to be related to the Codex App's behavior rather than user-written code.

Notes

The exact cause of the issue (e.g., context-selection, message-ordering, or stale-thread-state) is not specified, and without further technical details, it's challenging to provide a definitive fix. The workaround of asking the question again seems to be the most reliable method to ensure Codex responds to the new question.

Recommendation

Apply the workaround of asking the new question again when the issue occurs, as it has been observed to resolve the problem in most cases. This approach allows for continued use of the Codex App with large context sessions, albeit with an additional step when the issue arises.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Codex should answer the newly submitted question.

#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING