After a $10,000 loop bill: budget alerts and a cost-audit prompt for vibe-coded projects

Key points

• The author argues that vibe-coded projects pass functional checks while polling, alarms, retries and full-table scans keep running without errors, and that AI-written code does not estimate trigger frequency × unit price × run time.
• He shows the dashboard path for a billing budget alert (Manage Account → Billing → Billable Usage → notifications → Create alert → Billing budget alert) and suggests a threshold of two to three times normal monthly spend, capped by the loss you can bear.
• He notes alerts are based on the previous day’s data, send one email per billing period, need a Super Administrator, Administrator or Billing role, exclude fixed fees such as Workers Paid, and do not pause service or cap spend.
• He lists patterns to check: alarms that reschedule themselves without a stop condition, polling without backoff, cron jobs without cursors or idempotency, D1 queries without indexes or WHERE, Worker/Queue call loops without retry limits or dead-letter queues, per-request KV or Durable Object writes, and AI loops without iteration caps, and gives a read-only audit prompt covering them.
• If a bill has already spiked, he suggests stopping the triggering sources first, exporting usage data and fix records, and filing a billing appeal in Support, and writes that relief is decided case by case.

Original sources

1. 2026-10-08

   Original post

   Read on 𝕏

   铁柱AGI

   @cgnot996 · Original 𝕏 post

   https://t.co/6G2XYCLf2h

   2026-10-08 01:56:48 UTC