Codex Windows app exhausted a weekly usage limit in about 62 hours across many parallel tasks
lty418905-blip (OpenAI Codex user) · Aug 5, 2026 · Coding agent
What happened
A ChatGPT Pro user ran more than ten independent Codex tasks across several projects through the Codex Windows desktop application. The weekly usage cycle started on August 2, 2026 at about 12:00 and the entire weekly limit was exhausted by about August 5 at 02:00 — roughly 62 hours later. The usage interface reported approximately 3.17 billion tokens during that period, which the user described as disproportionately high for an individual developer even with many active long-context tasks. One task entered a repeated context-compaction and file-rereading loop: the context became full, Codex compacted it, the task reread files or reconstructed its working state, the context quickly grew again, another compaction occurred, and the cycle repeated without producing proportional progress. The issue remains open.
Causal vector
Many parallel independent Codex tasks across several projects, repeated context-compaction loops, redundant status reporting, and continuous Windows commit growth
Source
Reported by GitHub issue, openai/codex #37090. Verified against the primary report.
A spend firewall operating at the account or workspace level — not per-task — is what catches the aggregate burn when many agents each look reasonable in isolation but together exhaust a weekly cap in under three days.
The six rule types that contain this class of failure
Per-transaction cap
Any single spend above your ceiling is BLOCKED before it moves.
Daily total
Cumulative spend across all agent calls, bounded per day.
Velocity limit
Stops runaway retry loops — the #1 cause of overnight losses.
Merchant allowlist
Only approved destinations can ever receive funds.
Category rules
Flag high-risk classes (crypto, infra, refunds) for review.
Approval threshold
Above a value, the action waits for a human.
Related incidents
Codex context auto-compaction loop rereads files, loses progress, and burns paid credits
edisonjoao1 (OpenAI Codex user) · Jul 24, 2026
OpenAI confirmed Codex background tasks were silently burning users' usage limits faster than normal
OpenAI (Codex) · Jun 30, 2026
Codex Runtime stuck in a runaway inference loop burned credits with no project loaded
TWembley (OpenAI Codex Runtime user) · Jun 25, 2026
Don't be the next entry
Every incident in this database is the result of trusting a prompt, a provider cap, or a human review cycle. sipi.bot replaces all three with one deterministic call. 80 documented failures, one control.