Skip to content

Back to the record

Aug 25, 2026Single source

OpenAI Codex stuck in a 9-hour compaction loop drained an entire weekly usage allowance

AI loose in the worldAvailabilityDERIVED

Approved by person, Oct 11, 2026. How entries are approved

Showing full summaries.

A user asked Codex to make a relatively small change to an existing project. Instead of completing it, the agent entered a continuously repeating loop: it announced the changes it was going to make, ran context compaction, re-explained the same plan, compacted again, and re-started - sometimes pulling previously completed work back into the workflow. The loop ran for roughly 9 hours unattended and took the account's weekly usage from 100% to 0% while the original task remained incomplete. The reporter asked for loop detection, no-progress timeouts, and a warning when a single task consumes an unusual share of usage.

What this means for youIf you pay for an AI tool with a usage limit, an agent can get stuck repeating itself and burn your whole allowance overnight. At work, someone should watch usage and set caps before letting agents run unattended. Check your usage dashboard for alerts or limits, and stop any agent task that runs for hours without finishing.

Sources

Incident records from the AI Agent Incident Database by sipi.bot (https://sipi.bot/incidents/), licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).

Source data license: CC BY 4.0. Attribution to sipi.bot is required.

Covered by snapshot 45

da93f03b406f409940d0a6ef47b526607f82ebf457d98f69299b88aceede576a

This entry is record number 2194. It has not been edited since it was approved; the hash above would not match if it had. How to verify

OpenAI Codex stuck in a 9-hour compaction loop drained an entire weekly usage allowance | Vigilo AI Watch