OpenAI Codex CLI excessive SSD writes damage disk lifespan
OpenAI's Codex CLI tool reportedly writes excessive diagnostic logs to disk, causing SSDs to accumulate 37 TB of writes in 21 days. Developers warn this could exhaust typical consumer SSD write budgets within a year, though OpenAI has not yet released a fix.
What happened
A GitHub user discovered Codex CLI continuously writes large amounts of diagnostic logs to a local SQLite database, causing abnormal disk activity.
Over 21 days of operation, the system accumulated approximately 37 TB of write volume. If sustained at the same rate, annual writes would reach approximately 640 TB.
The issue stems from Codex's logging mechanism recording extensive system information including network communications and file access records in detailed debug mode. The logging feature was enabled by default.
Reported impact
A typical consumer SSD with 1 TB capacity has a write endurance budget of approximately 600 TBW (Terabytes Written). At the observed write rate, an SSD could exhaust its rated write lifespan within one year.
The continuous writes and frequent data modifications stress the storage device's endurance, potentially degrading SSD durability even as file sizes may not visibly expand.
Index analysis
The root cause is Codex's default TRACE-level logging, which records granular diagnostic information of limited practical value to typical users. Users cannot disable TRACE logging through the RUST_LOG environment variable, which is ignored by the system.
Some Linux and macOS users have identified a temporary workaround by redirecting logs to temporary memory directories to reduce SSD write load. However, this does not address the underlying logging volume issue.
Governance controls
Similar reports of high write volumes were first reported beginning in April 2026. As of the reporting date, the core issue remained unresolved and the related GitHub Issue remained open.
OpenAI has not released an official fix or patch for the logging defect.
Classification
Sources and evidence
Sources not yet published
This record was researched and written by the Index from original reporting. Its sources are still being verified by an editor, and they are listed here once that check is complete. Until then the record carries no reviewer.