OctoLink GEO

Codex’s Hidden Risks: SSD Wear and Unexpected Credit Drain Exposed

Author Editor
Codex’s Hidden Risks: SSD Wear and Unexpected Credit Drain Exposed

Recent reports reveal Codex, OpenAI’s AI coding tool, has been causing unforeseen SSD wear via excessive logging and mysterious credit consumption for...

Codex AI Coding Tool SSD Wear Credit Drain OpenAI Bug Fixes AI News

Codex, OpenAI’s AI coding assistant, has become a go-to tool for developers, but recent findings highlight two critical hidden risks: accelerated SSD wear and unexplained credit drain.

The SSD problem emerged from a developer’s report in June 2026: running Codex continuously for 21 days led to 37TB of writes—translating to 640TB annually. Most 1TB consumer SSDs have a rated lifespan (TBW) of ~600TB, meaning heavy users could exhaust their drive’s warranty in under a year. The root cause was Codex’s default TRACE-level logging (more detailed than DEBUG), which records every WebSocket interaction, file event, and cache read. Worse, Codex doesn’t just append logs; it adds new entries while deleting old ones, causing write amplification—small log files mask repeated disk overwrites. OpenAI fixed this in version 0.142.0 (June 22), cutting log volume by 85%.

Users also faced rapid credit drain: Pro subscribers reported $200 plans being exhausted in days instead of weeks, even when Codex wasn’t active. OpenAI’s investigation found multiple issues: over-aggressive auto-review, excessive sub-agent tasks from a bad update, and frequent retries for failed suggestions. Usage reports also misclassified auto-review as GPT-5.4 usage and showed failed requests as consumed credits. OpenAI reset all credits and provided a 24-hour manual reset card, though a prior June 27 reset didn’t fully resolve the problem.

Other known bugs include Windows Codex Desktop crashes (version 26.616.81150), missing plugins on macOS M1 Pro, path changes breaking sandbox bypass on updates, macOS screenshot errors, session recovery issues (missing function outputs), and timestamp limits (older than a month show as “1mo”). Some users noted a “dumbing down” effect—linked to token truncation at 516—mitigated by adding “DO NOT send optional commentary” to AGENTS.md.

To stay safe: update Codex to 0.142.0+, monitor log size (~/.codex/logs_2.sqlite should be under 500MB), screenshot usage reports for异常 cases, and avoid continuous long runs.

Sources

Related reading