Regression: long resumed conversations fail remote compact with context_length_exceeded on 0.132.0+

Resolved 💬 6 comments Opened May 22, 2026 by zhatlas Closed Jun 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

Observed with:

  • codex-cli 0.132.0
  • codex-cli 0.133.0

Downgrading to codex-cli 0.131.0 works around the problem.

Which model were you using?

GPT-5.5 in Codex.

What platform is your computer?

Linux / WSL environment.

What issue are you seeing?

A very long conversation can no longer continue after upgrading to 0.132.0 or 0.133.0. When the conversation is resumed, Codex appears to put the full conversation history back into the model context instead of successfully compacting it. The remote compact task then fails with context_length_exceeded, and the session cannot continue.

Error shown by Codex:

Error running remote compact task: {
  "error": {
    "message": "Your input exceeds the context window of this model. Please adjust your input and try again.",
    "type": "invalid_request_error",
    "param": "input",
    "code": "context_length_exceeded"
  }
}

This looks like a regression in the resume / remote compaction path. The same long conversation can be continued again after downgrading to 0.131.0.

What steps can reproduce the bug?

  1. Start with a very long Codex conversation.
  2. Use Codex CLI 0.132.0 or 0.133.0.
  3. Resume the long conversation.
  4. Continue the conversation until Codex tries to compact remotely.
  5. Observe that remote compact fails with context_length_exceeded, and the conversation cannot continue.
  6. Downgrade to 0.131.0 and resume the same workflow. The conversation can continue again.

What is the expected behavior?

Resume should not re-add the entire long conversation to the active context in a way that makes compaction impossible. Codex should compact or trim the resumed conversation before sending it to the model, so long conversations remain recoverable.

Additional information

This may be related to #23694, which also reports a remote compact regression after upgrading to 0.132.0, but that issue reports array_above_max_length. This report is specifically for the context_length_exceeded failure mode on resumed long conversations.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #23694
  • #23589
  • #22890

Powered by Codex Action

selaquik · 1 month ago

Same problem. And the app can’t be rolled back to an earlier version either.

zzzjasdawd · 1 month ago

How to downgrade the codex Windows application

cwolff-oai · 1 month ago

We can reproduce this on 0.132.0/0.133.0. The current workaround is to stay on 0.131.0 for the CLI; we are still investigating the resume/remote compact regression.

etraut-openai contributor · 21 days ago

Thanks for reporting this problem. Until recently, Codex used a separate endpoint and server-side logic for compaction. We recently switched to a more robust approach where the compaction logic is moved locally using the same endpoint as normal turns. This eliminates "remote compaction" errors and increases the stability and reliability of compaction operations. If you see further problems with compaction, please use /feedback and open a new bug report.

Showing cached comments. Read the full discussion on GitHub ↗