Replit Agent's effort-based billing hits $50/hour as looping inflates billable actions
Replit Agent users · Jul 16, 2026 · Coding agent
What happened
An r/replit thread from July 16, 2026 reported Replit's AI Agent effectively charging $50/hour under effort-based pricing, with the poster stating the agent 'just reads files over and over to inflate the actions taken and burns through the budget'. Commenters reported being billed $50 every other day; the thread's top advice was to set a hard billing cap immediately. Effort pricing bills attempts, not outcomes, and attempts go unbounded exactly when the agent cannot see what is wrong.
Causal vector
Per-attempt billing plus a file-reading loop: repeated billable actions with no progress test between them
Source
Reported by Reddit r/replit - 'Replit's AI Agent is now charging me $50/hour' (2026-07-16). Verified against the primary report.
Paying per attempt turns a loop into a revenue event for the vendor and a loss event for the user. A velocity limit on consecutive billable actions trips on the Nth failing attempt and ends the run before the usage page does.
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 Codex stuck in a 9-hour compaction loop drained an entire weekly usage allowance
Codex user (OpenAI Developer Community) · Aug 25, 2026
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
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.