Claude Code autocompacting loop spiked token usage until the budget ran out (flagged ACTIVE INCIDENT)
Claude Code users (GitHub issue 9579) · Oct 15, 2025 · Coding agent
What happened
Windows users reported Claude Code entering an autocompaction loop: the session compacted its own context over and over without ever finishing, spiking token usage on every cycle. The issue was labeled 'ACTIVE INCIDENT, Cost escalation ongoing', and linked reports described the loop running infinitely until the token budget was exhausted.
Causal vector
Autocompaction loop, context compaction retried indefinitely instead of terminating, burning tokens until the budget ran dry
Source
Reported by GitHub issue, anthropics/claude-code 9579. Verified against the primary report.
Self-referential loops like autocompaction can't be reasoned away from inside the session: the stop condition has to live outside the model. A budget-bound firewall halts the process the moment cumulative spend crosses the ceiling, loop or no loop.
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
Stanford Digital Economy Lab: agentic coding tasks consume ~1,000x more tokens than chat, with up to 30x variance on the same task
Stanford Digital Economy Lab · May 5, 2026
Forgotten /loop command checking PRs every 30 minutes ran 46 times over 26 hours and burned ~$6,000 overnight
Individual developer (r/ClaudeAI report) · May 1, 2026
Claude Code entered an infinite loop, re-sending the same requests for hours and burning $500+ in tokens
Claude Code user (GitHub issue 35166) · Mar 17, 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. 67 documented failures, one control.