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
- An MCP server signs every AI agent tool call into a verifiable Merkle chain — Funky_Chicken_22 · 2026-07-22
- Claude Code skill uses 10 Markdown rules to make outputs ADHD-friendly — alex_verem · 2026-07-22
- A Firecracker-based platform says it can host 6,000 AI agents on one 256 GB server — maritime_sh · 2026-07-22
- A better path to agent autonomy is running waves, finding friction, and iterating — JnBrymn · 2026-07-22
- AI agent designers map the visual and tonal cues behind companionship products — Unlikely-Platform-47 · 2026-07-22
- Coding agents are heading toward an AI-writes, AI-reviews, human-approves workflow — aftahi_ai · 2026-07-22