Vigilance Beating AI News Flash: A user had Claude manage a set of Codex, and Claude discovered a historic bug. One session ran continuously for two days, leaving a 110MB log and consuming approximately 353 million tokens. However, upon reopening, Codex only remembered the initial sentence.
The actual work content was not lost. Codex stores the complete chat log locally and creates an additional index for fast retrieval. The issue lies with this index: it got stuck at an early position, even though the subsequent records were still present but invisible to Codex. The user checked their 439 sessions, finding 398 sessions with index anomalies.
Later on, reports of similar "false amnesia" surfaced in Windows Desktop, Remote SSH, and other environments: the underlying records were intact, but the interface remained stuck at an old position without providing error messages or self-healing mechanisms. After the original poster deleted the corrupt index, Codex was able to reprocess a 110MB session in about 20 seconds and recover all 398 abnormal sessions.
However, subsequent cases have shown that the issue may not solely lie within the index; the original records themselves could have duplicate serial numbers. Therefore, directly deleting the index might not be safe in all scenarios. Currently, this bug is still in an Open status, with no associated fix PR in sight.
