Hello Everyone,
Codex app constantly Context automatically compacted ( every request ) which lead to waste of credits (financial aspect and limits ) without completing any task. Platform Mac Arm latest version Version 26.616.41845 • Released Jun 19, 2026
Please see attached screenshot .
The question is app should be production ready or it in some earlier stages ?
Also constant crashes like time to time it just quits . I can provide crash reports .3
After limit is expired . I observed more and Context automatically … is conceptually and architecturally is incorrect. I know what I am talking about. Main concern it interrupting agent in middle of modification or thought process. Then only point is not clear how it impact credits and limits
I would not answer this as a simple yes/no. I would split production readiness by workload.
For personal assisted coding, it can be useful today if you keep the loop bounded: small task, clean git state, narrow working directory, explicit verification command, and human review before accepting changes.
For production engineering work, I would not treat any agent session as autonomous unless you have controls around it: a repo checkpoint before the run; a clear task boundary, not “fix everything”; max retry/tool-call limits; tests or a build command that must pass; review of the final diff before merge; and a way to stop when compaction or crashes begin.
The repeated automatic compaction you describe is worth reporting as a bug, especially if it happens every request and interrupts edits mid-run. The most useful report would include the exact app version and macOS version, whether it happens in a fresh thread with a tiny repo, approximate transcript size when compaction starts, whether MCP/tools are enabled, crash reports from Console.app, and a short screen recording if possible.
On credits/limits: compaction can be legitimate when context is large, but if it is triggered every turn in a small task, that is not just a UX issue. It can change cost, continuity, and reliability. I would file it as a reproducible bug rather than only as a general production-readiness question.
Thank you for suggestion , I will open bug report. In our case tool use for prototyping with strict guard rails in place where my question is related to stability and end user comfort use.
Here are example of the crashes
An error has occurred
Codex crashed with the following error:
(code=null, signal=SIGKILL).
Most recent error: {"timestamp":"2026-06-21T15:46:10.052287Z","level":"WARN","fields":{"message":"unknown feature key in config: thread_tools"},"target":"codex_features"}
Some things to try:
Check your config.toml for invalid settings
Try updating your IDE settings
Try updating Codex or installing a different version