Codex ate a hard drive in a resume loop
RexDouglass · x · 2026-07-21
A humorous but detailed post-mortem of Codex unexpectedly filling a disk.
The failure chain was: an orphaned codex resume --last --yolo process kept restarting from an old terminal shell, each resume forked a new rollout that recopied the full session history, and the retries created a death spiral. One loop wrote around 6 GB of history plus logs, nine copies accumulated to roughly 58 GB in four hours, and the issue went unnoticed because the disk guard was disabled and the watchdog monitored transcripts rather than filesystem growth. The author suggests a standalone disk-float watcher and a session-size hygiene rule for Codex profiles.
More from coding & agent
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11