Codex logging bug may write TBs to local SSDs(github.com)
488 points by vantareed 1 day ago | 267 comments
tl;dr: A Codex bug caused its SQLite feedback log to write at extreme rates—roughly 37 TB over 21 days on one user's machine—due to a global TRACE-level default that persisted noisy dependency logs, raw WebSocket/SSE payloads, and mirrored OpenTelemetry events. Analysis showed ~96% of retained log bytes came from TRACE noise and otel mirror logs, with heavy insert-and-prune write amplification (5.5B row IDs allocated for only 0.5M retained rows). Two merged PRs now filter noisy targets and stop logging every Responses WebSocket event, eliminating about 85% of logs.
HN Discussion:
  • Codex has broader quality issues beyond this bug, like GPU-hogging spinner animations
  • Sharing practical workarounds like SQL triggers and VACUUM to mitigate the bug
  • OpenAI's silence and slow response to a known GitHub issue is baffling
  • Classic trace-level logging blunder reflects sloppy vibe-coded development practices
  • ~Codex being open-source makes it easy to patch yourself, and a fix has already landed