Replit subscription credits hit 100% on an undeployed prototype; auto-billing invoices $60 beyond the plan
Replit (community forum) · Feb 12, 2026 · Coding agent
What happened
A February 12, 2026 Replit community forum post reported monthly credits completely exhausted (100% used) by agent work on a React + MongoDB prototype that was never deployed publicly. A reply documented the auto-billing mechanic: once the included $25 credits are exhausted, usage continues and generates a new bill invoiced every $60. The user's only intended actions were running the app locally and making small changes.
Causal vector
Auto-renewing pay-as-you-go invoices keep metering an agent whose credit pool is already empty, with no stop condition on the spend
Source
Reported by Replit Community Forum - 'Replit Credits Exhausted' (2026-02-12). Verified against the primary report.
A spend policy must live outside the platform that profits from exceeding it. An external hard cap on agent spend makes the auto-invoice impossible: the agent stops when the budget stops, not when a human notices the charge.
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
OpenAI confirmed Codex background tasks were silently burning users' usage limits faster than normal
OpenAI (Codex) · Jun 30, 2026
Uber burns through its entire 2026 AI coding budget in four months
Uber · Jun 2, 2026
Company hit with a reported $500 million Claude bill after leaving usage limits off
Unnamed enterprise (reported via Axios) · May 28, 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. 75 documented failures, one control.