GitHub issue #33493 in openai/codex, opened 2026-07-16 by snrui, records a report that a long-running, image-heavy Codex Desktop thread enters a repeated auto-compaction cycle because the compacted replacement_history keeps historical input_image items including their full inline base64/data-URL payloads; in the reported thread the rollout JSONL was approximately 4.16 GB with 224 compaction records and 92 retained images carrying approximately 26.47 million inline image/base64 characters, leaving only about 8,000 tokens of headroom below the auto-compaction threshold; the report was filed against Codex Desktop 26.707.72221 with embedded CLI codex-cli 0.144.2 on macOS 26.3.
Verbatim Excerpts from Cited Records
“A long-running, image-heavy Codex Desktop thread enters a repeated auto-compaction cycle.”
·
openai/codex (issue 33493 opening body, What issue are you seeing section)
·
2026-07-16T04:01:14Z
·GitHub Issue ↗
“The compacted `replacement_history` keeps historical `input_image` items, including their full inline base64/data-URL payloads.”
·
openai/codex (issue 33493 opening body, What issue are you seeing section)
·
2026-07-16T04:01:14Z
·GitHub Issue ↗
“Repeated compactions keep copying the same images into new compacted records.”
·
openai/codex (issue 33493 opening body, What issue are you seeing section)
·
2026-07-16T04:01:14Z
·GitHub Issue ↗
“The post-compaction history therefore has only about 8,000 tokens of headroom.”
·
openai/codex (issue 33493 opening body, Local evidence section)
·
2026-07-16T04:01:14Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 31 comments were read. Multiple users corroborated the behaviour on macOS, Windows and Linux with later builds, including rollouts over 25 GB. ignatremizov (2026-10-27) reported that upstream had addressed the text-only retained-image budget diagnosis via PR #40280, which merged image budgeting, and that compaction_image_budget was stable; Nurozen (2026-09-27) had earlier reported the ratchet still happening with compaction_image_budget enabled on codex-cli 0.157.0, and nathanchillz (2026-10-07) reported a further reproduction on bundled CLI 0.162.0-alpha.2. No retraction of the original report appears in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #33493 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.