Runaway inline image duplication during context compaction creates 20+ GB rollout files
What version of Codex CLI is running?
0.146.1
What subscription do you have?
Pro
Which model were you using?
_No response_
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
Codex doctor report
What issue are you seeing?
Corroborating this issue with an independent occurrence on Codex CLI 0.146.1, macOS 26.6, Apple Silicon.
Two dormant rollout files were found:
- 21,047,403,972 bytes with only 6,194 JSONL records
- 37,593 occurrences each of input_image, image_url, data:image, and base64
- 443 context compactions
- 7,697,818,808 bytes with only 2,943 JSONL records
- 12,600 occurrences each of those image markers
- 125 context compactions
Both files are fully allocated rather than sparse and have been dormant since July 23–24, 2026. codex doctor reports 17 OK, 0 warnings, and 0 failures, and the rollout/state-database inventories reconcile cleanly.
This independently confirms the same on-disk image amplification across two threads and shows that it persists in Codex CLI 0.146.1. No rollout files, logs, screenshots, thread IDs, or private conversation data are attached.
A supported repair path that removes duplicated binary payloads while preserving the text transcript would be valuable.
What steps can reproduce the bug?
Uploaded thread: 019fd86f-346c-7f23-88dd-68caa8bdb497
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Related to #34863, which tracks the same compaction/image-amplification mechanism primarily through Desktop and app-server symptoms. This report adds an independent Codex CLI 0.146.1 occurrence involving dormant 21.0 GB and 7.7 GB rollouts. Please consolidate or close as a duplicate if both cases share the same fix.