OpenAI Codex CLI Massive Logging Issue Discovered by 1996fanrui Causes Permanent SSD Hardware Damage Through Excessive Data Writes
A software developer operating under the username 1996fanrui has uncovered an issue within the OpenAI Codex CLI tool that drastically reduces the operational lifespan of storage drives. The command line utility which is designed for agentic programming tasks writes massive volumes of unnecessary diagnostic logs to a local database by default. This constant storage activity is placing consumer grade hardware under extreme stress and causing premature wear on storage components.
As may be seen in a comprehensive analysis published by the developer the application wrote around 37 TB to a local SQLite database across a trial period of just 21 days. Extrapolated over 1 year this usage would amount to over 640 TB of data written writing which is far beyond the write endurance endurance of typical consumer solid state drives and could render a typical drive useless in under 12 months.
At the root of the issue is the enormous number of individual database writes. Rather than batching the data or ultimately only recording a significant event, the tool is perpetually recording all of the background processes. The programmer admitted that the program produces about 36,000 new lines of log data, every fifteen seconds. This continual fire hosing prevents the hard drive from even entering idle power states, thereby further hastening hardware deterioration.
While the problem has been known and well discussed in the developer circle OpenAI has not yet implemented a fix that limits the amount of logs written. The latest updates from the developer mentioned fixing stability problems associated with the database itself, but not implemented any limit on the amount of diagnostic data saved. ZOOM users should manually track their drives health and limit execution time to avoid permanent hardware damage.
