Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Repeated automatic context compaction after every prompt/task. [1 comments, 2 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#18827•Fetched 2026-04-22 07:52:01
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
jlekerli-sourcejlekerli-source
Participants
github-actions[bot]github-actions[bot]jlekerli-sourcejlekerli-source
Timeline (top)
labeled ×3commented ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

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

Version 26.417.41555 (1858)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

i am still haveing the contest issue now for over 9 hrs ???? how can this be - after every prompt triggers the autmatic contest window - i lost 16% of my weekly to this

Use this in the feedback box:

Repeated automatic context compaction after every prompt/task.

Codex is repeatedly hitting the context limit after nearly every single prompt or autonomous task. Even with normal usage, it runs for only about 15–20 seconds before it starts automatically compacting context again.

This has been happening continuously for around 9-10 hours in the same session and makes Codex extremely difficult to use. It seems to happen after almost every task, not just occasionally.

Please check whether this is a bug or an issue with my current session/account. I’ve included the current Codex session logs.

Keep Bug selected and leave Include current Codex session logs checked.

codex://threads/019da2e1-6ab2-7830-a27f-5403a9caa33b

019da2e1-6ab2-7830-a27f-5403a9caa33b

/Users/omarat-turkmani/Documents/Ringly

What steps can reproduce the bug?

Uploaded thread: 2bffb833-a020-45af-aeaa-35ab0ac3f752

Codex is repeatedly hitting the context limit after nearly every single prompt or autonomous task. Even with normal usage, it runs for only about 15–20 seconds before it starts automatically compacting context again.

What is the expected behavior?

if starts compacting after 1 task

Additional information

I would like a compensation for this - I lost 16-17% of my weekly usage and 9 hours fof work Kina wasted, thx

extent analysis

TL;DR

The issue can be mitigated by restarting the Codex session or checking the session logs for any anomalies that may be causing the repeated automatic context compaction.

Guidance

  • Review the provided Codex session logs to identify any patterns or errors that may be contributing to the repeated context compaction.
  • Try restarting the Codex session to see if the issue persists, as this may resolve any temporary issues causing the problem.
  • Check the thread 2bffb833-a020-45af-aeaa-35ab0ac3f752 for any specific tasks or prompts that may be triggering the context compaction.
  • Verify that the issue is not specific to the current task or prompt by trying different tasks or prompts to see if the context compaction occurs consistently.

Example

No code snippet is provided as the issue is related to the Codex App's behavior and not a specific code problem.

Notes

The issue may be specific to the user's account or session, and reviewing the session logs and thread information may help identify the root cause. The user has already lost a significant amount of time and usage, so resolving the issue quickly is important.

Recommendation

Apply workaround: Restart the Codex session and review the session logs to identify any patterns or errors that may be causing the repeated context compaction, as this may provide a temporary solution until the root cause is identified and fixed.

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…
#response parsing#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING