Context compression killed Codex
Resolved 💬 13 comments Opened May 23, 2026 by selaquik Closed May 31, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex_26.519.5221.0_x64
What subscription do you have?
Pro x5
What platform is your computer?
Win 10 Pro x64
What issue are you seeing?
Since May 22, context compression has been completely broken. Instead of actually compressing the context, it just keeps happening endlessly. I already tried deleting all chats and reinstalling the app, but it didn’t help. At the same time, I can’t roll back the app version - there’s no older version in the Microsoft Store, and the app packages themselves aren’t published anywhere!
In practice, I haven’t been able to use the subscription for several days now, even though access to x5 Pro for codex was the whole reason I bought it in the first place.
What steps can reproduce the bug?
When the context fills up in the app and context compression starts, it becomes endless.
What is the expected behavior?
_No response_
Additional information
_No response_
13 Comments
I know there are similar threads, but they are mostly about the CLI version, where it’s easy to roll back to a stable version. For the app, there is no such solution.
In practice, this bug breaks the chat after 2-3 messages, and the only thing left to do is delete it.
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Seriously, why deploy to production on a Friday? =\
Same problem
As a temporary workaround, you can use the VS Code extension. I already tested it on “dead” chats, and they started working again.
But it’s significantly worse than the app. And constantly jumping between one and the other is not exactly pleasant either.
Same here
https://github.com/openai/codex/issues/24230#issuecomment-4525934069
fix it
Funny (no) thing is, the temporary hacky fixes that at least helped for a while - today don’t even work anymore.
Several days have already passed, and the issue still hasn’t received any attention. On another PC, the app that hasn’t been updated does not have these problems.
Not giving users any way to roll back to a stable version while also shipping clearly untested software on a Friday is a terrible decision.
I also don’t see any real response to this situation - Codex doesn’t work, and the subscription is running out.
This is an awful decision by the company toward its loyal users who have been with them for years.
omg
@zgl-gits not workin (
I noticed that Codex 134 has already been released, but the app is still receiving version 133 from the Microsoft Store, which seems to be the problematic one.
The issue has been resolved, so this can be considered closed. Thanks for the fix.
<img width="543" height="1207" alt="Image" src="https://github.com/user-attachments/assets/8de91550-66df-48a9-afa7-a3693bef2f5c" />
<img width="242" height="684" alt="Image" src="https://github.com/user-attachments/assets/e27d797b-b872-496e-b411-72f29166d453" />
same problem Here is a screenshot of the behavior from my session. As you can see, almost every single command execution ("Bir komut çalıştırıldı") or minor file edit is immediately followed by a context compaction ("Bağlam otomatik olarak daraltıldı") notice. It triggers constantly on every single minor turn, making the entire session incredibly laggy and fragmented.